Kybase MCP server

Read from the package source without running it. The installed server may list more.

• append_to_note

  Add text to a note without resending the rest \u2014 prefer it over update_note for journals, logs and running lists. A blank line separates your text from what was there. The note is locked for the read-modify-write, so two sessions appending at the same moment keep both additions instead of the later one overwriting the earlier. Re-embeds in the background like any content change.

• create_folderwrite action

  Create a new folder. Optionally nested under a parent.

• create_notewrite action

  Create a new note. Embedding is generated automatically in the background. The server instructions' wikilink and tag rules apply: search_notes for the topic first and link the related notes it finds, and call list_tags before coining a new tag.

• delete_folderwrite action

  Delete a folder and its full subtree of child folders (cascade). Every note inside \u2014 including notes in nested subfolders \u2014 is soft-deleted into the trash along with it (see delete_note), recoverable via restore_note within the retention window. To preserve organization instead, move notes/subfolders out first.

• delete_notewrite action

  Soft-delete a note by id \u2014 it disappears from list_notes/search/get_note/the graph, but is recoverable with restore_note for … days before being purged for good. Use list_notes with trashed:true to see what's currently in the trash.

• get_backlinks

  Notes that link to this one via [[Title]] wikilinks, by id or title. Each comes back as id/title/folder_path plus a snippet around the link; include_content:true returns their full text instead, which is expensive when many notes link here \u2014 prefer get_note on the ids you actually want. offset and limit count notes, not characters.

• get_graph
• get_neighbors
• get_note
• indexing_status
• list_folders

  List folders with the full path already resolved \u2014 no need to walk parent_id yourself. Pass a folder's own id as parent_id to create_folder/update_folder to nest under it. Sorted by path, so a page is a contiguous slice of the tree read top to bottom; the reply is `{folders, has_more, next_offset?}`.

• list_notes

  List notes newest first, filtered by folder, tag or date. This is the tool for "what is new" and "what changed lately": search_notes ranks by relevance and never by recency. created_* is when a note was made, updated_* when its own text last changed \u2014 a rename elsewhere rewriting a [[link]] inside it does not count as an edit here. Each row carries content_length, so you can tell a long note

• list_tags
• replace_in_note

  Replace exact text in a note without resending the rest. Either find/replace or old_string/new_string \u2014 the same pair, either spelling. For several replacements pass `edits` rather than the singular fields (one lock and one re-embed for the batch, not one per call); the two forms cannot be combined in one call. Edits apply in order, and each `find` is matched against the note as the edits bef

• restore_note

  Undo delete_note: brings a soft-deleted note back. Errors if the note isn't in the trash (never deleted, already restored, or purged past the retention window), or if a live note has since taken the same title (rename one of them first, then retry).

• search_notes
• update_folderwrite action

  Rename a folder and/or move it under a different parent (set parent_id to null for top level). Provide at least one of name/parent_id. The response includes the resolved `path` so a rename or move can be confirmed without a follow-up list_folders call.

• update_notewrite action

  Update note fields. Re-embeds if title or content changed. Updates wikilinks if title changed. The server instructions' wikilink and tag rules apply when substantially rewriting \u2014 in particular, call list_tags before coining a new tag. Pass expected_updated_at (the updated_at you read) to be refused instead of overwriting a change made in between.

• Code scan2 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 5 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

83/100

higher than 70% of 3,470 Web search servers

Tools

18

the typical Web search server has 5

Tools that change things

33%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

6

more than 81% of 1,786 Web search servers

Downloads a week

365

more than 81% of 827 Web search servers with a package

Kybase: common questions

Is Kybase MCP server safe?

Mostly: it is graded B (83/100). Read the Kybase safety report

How do I install Kybase?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Kybase need an API key?

Yes. The registry entry asks for GOOGLE_API_KEY, OPENAI_API_KEY, DATABASE_URL.

Is Kybase maintained?

The last commit was 6 days ago (2026-10-29). The latest release is v0.2.4.

What can I use instead of Kybase?

Servers from other publishers that do the same job: DocsMint MCP server, searxNcrawl MCP server and obsei MCP server. Compare all Kybase alternatives.

How does Kybase compare with other Web search MCP servers?

safety score 83/100 (higher than 70% of 3,470 Web search servers); tools 18 (the typical Web search server has 5); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.