Connect your agent to Knownbase.

The endpoint

Every client below uses the same URL:

https://knownbase.dev/mcp

There are two ways to authenticate against it. Use whichever your client supports.

Option A: sign in with OAuth (recommended)

Claude, ChatGPT, Cursor, and most modern MCP clients can sign a human in interactively instead of asking for a pasted key. Give the client the endpoint URL above and nothing else — it discovers the rest itself and opens a Knownbase login/consent screen where you pick which workspace to grant access to.

• Claude.ai / Claude Desktop — Settings → Connectors → Add custom connector → paste the URL.
• Claude Code (CLI) — claude mcp add --transport http knownbase https://knownbase.dev/mcp. The first tool call opens a browser to finish sign-in automatically.
• ChatGPT — Settings → Connectors → Add connector → paste the URL.
• Cursor — add {"url": "https://knownbase.dev/mcp"} (no headers) to mcp.json; Cursor opens a browser on first use.

You can review and revoke connected apps any time from Settings → Connected apps. If a client shows a raw error or "can't connect" on this URL, it likely doesn't support remote MCP servers yet — use an API key instead.

Option B: paste an API key

Works with every MCP client, including ones that only support static config. Sign up for a free workspace, then open Settings → Workspace & MCP and generate a key (it looks like kb_..., and is shown in full only once).

{
  "mcpServers": {
    "knownbase": {
      "url": "https://knownbase.dev/mcp",
      "headers": {
        "Authorization": "Bearer kb_YOUR_KEY_HERE"
      }
    }
  }
}

A key can optionally be marked read-only (queries only, no writes) or scoped to a single project (every note operation restricted to that one project) — both set when you create it in Settings.

MCP tool reference

Once connected, these are the tools your agent can call. All are workspace-scoped: an agent only ever sees the notes its key or OAuth grant can reach.

• search_notes — full-text (or semantic, on Business) search by project, tag, status, query, or last-modified date. Lean by default; pass includeBody:true for full content inline.
• get_note / get_notes — read one note, or up to 50 by id in one call, full body included with resolved links and backlinks.
• upsert_note — create or update a note. Updates are partial: omit a field to leave it unchanged, so "just fix the tags" can't silently wipe the body.
• delete_note — move a note to trash (soft delete, restorable from the dashboard).
• list_note_revisions / get_note_revision — browse or fetch a note's prior versions.
• list_projects — every project in the workspace with note counts by status.
• rename_project / rename_tag — bulk-rename (or remove) across every note in one call.
• workspace_info / usage_summary — plan, limits, current usage, and this credential's own access.
• backup_project — full content for one project, returned inline for your agent to persist wherever you like.
• backup_now — trigger a configured server-side backup of the whole workspace.

Every tool call is workspace rate-limited at 300 requests/minute. Write tools (upsert_note, delete_note, rename_project, rename_tag, backup_now) are refused for read-only keys with a clear error, not a silent no-op.

REST API

The dashboard itself runs on a JSON REST API under /api/*, authenticated the same way — a browser session, or the same Authorization: Bearer kb_... key you use for MCP. If you'd rather script against notes directly instead of going through an agent, the core note routes are GET/POST /api/notes, GET/DELETE /api/notes/:id, and GET /api/notes/:id/revisions — the same operations as the MCP tools above, one HTTP call each.

MCP is the primary, stable interface for programmatic access (the tool names and shapes are a compatibility contract we don't break); the wider REST surface is what the dashboard uses internally and may evolve alongside it.