MCP Server

MindWiki exposes a single MCP endpoint that compatible AI clients can connect to. Once connected, the client gets 27 tools for reading, searching, capturing, asking, and (with write scope) modifying your vault.

Muse directory launch pending. MindWiki’s Muse connector is in development and is not yet approved or listed. See the Muse guide for preparation, planned workflows, and connection status. Muse Code has a separate CLI setup.

The endpoint

https://api.mindwiki.io/mcp

This hosted server supports Streamable HTTP and a legacy SSE transport. Client support and account requirements vary. Read, ask, and context tools work on every plan within the Free usage limits; writes, proposal mutations, and index updates require Pro or Power.

Two ways to authenticate

1. OAuth (recommended)

For Claude.ai, Claude Desktop, and ChatGPT, the right path is the remote MCP / OAuth flow. You don't paste any token. Here's what happens:

  1. You add the MCP server URL https://api.mindwiki.io/mcp in your AI client.
  2. The client discovers MindWiki's OAuth metadata automatically.
  3. Your client opens a browser and lands on the MindWiki approval page.
  4. You sign in to MindWiki (if you weren't already) and approve.
  5. Your client receives a token and the connection is live.

Once approved, the client can call MCP tools as long as the connection is active. To revoke access, go to mindwiki.io/account/connections.

OAuth permissions are determined by the approved grant: mcp:read, mcp:capture, and mcp:write. The legacy mcp scope allows all three. The approval page can narrow a compatible request to read-only or read and capture. Vault agent permissions apply in addition to scopes.

2. Personal API key (for clients without OAuth)

For clients that don't yet support remote MCP / OAuth, MindWiki accepts a personal API key as a query parameter:

https://api.mindwiki.io/mcp?token=YOUR_API_KEY

Your API keys are managed at mindwiki.io/account/api-keys. Each key:

  • Has a name you give it.
  • Has explicit read and/or write scopes you select at creation.
  • Is shown exactly once at creation — copy it then.
  • Can be revoked at any time.

API keys obey the scopes you set. A read-only key cannot call write tools (mindwiki_write_page, mindwiki_capture, mindwiki_update_index, mindwiki_create_proposal).

Where to find per-client guides

The exact wording varies between AI clients. We have a step-by-step guide for each major one:

What the AI gets after connecting

The connected client gains access to the 27 MindWiki tools. The most-used ones:

  • Search and read — mindwiki_search, mindwiki_read_page, mindwiki_list_pages
  • Ask the vault — mindwiki_ask, mindwiki_get_relevant_context
  • Capture — mindwiki_capture (OAuth capture or write access; API keys require write)
  • Write — mindwiki_write_page (write scope)
  • Propose — mindwiki_create_proposal (write scope)
  • Audit — mindwiki_get_agent_activity, mindwiki_list_agent_sessions

ChatGPT-compatible names search and fetch are also exposed for clients that look specifically for those tool names.

The full list with parameters and scopes lives at MCP Tools.

OAuth details

For implementers building custom clients:

  • Issuer: https://api.mindwiki.io
  • Authorization endpoint: https://mindwiki.io/oauth/authorize
  • Token endpoint: https://api.mindwiki.io/oauth/token
  • Registration endpoint: https://api.mindwiki.io/oauth/register (Dynamic Client Registration)
  • Revocation endpoint: https://api.mindwiki.io/oauth/revoke
  • Scopes: mcp:read, mcp:capture, mcp:write; mcp is the legacy full-access scope
  • Resource: https://api.mindwiki.io/mcp
  • Code challenge methods: S256 (PKCE required)
  • Grant types: authorization_code, refresh_token
  • Discovery:

- https://api.mindwiki.io/.well-known/oauth-protected-resource

- https://api.mindwiki.io/.well-known/oauth-authorization-server

Troubleshooting

  • The client asks for a token. That client doesn't support remote MCP / OAuth. Use the API key fallback URL https://api.mindwiki.io/mcp?token=YOUR_API_KEY.
  • The approval page doesn't load. Make sure you can sign in at mindwiki.io. The approval UI is hosted there.
  • The connection looks stale. Remove the connector and add it again — that forces re-discovery.
  • Tool calls fail with `INSUFFICIENT_SCOPE`. Your credential does not include the required scope. Reconnect through OAuth with the appropriate approval, or mint a new API key with the needed scope. Also check vault agent permissions.

Where to go next