Other MCP Clients

If your AI client speaks MCP, MindWiki works with it. The setup follows the same two-path pattern: OAuth where supported, API key everywhere else. This page covers the general pattern and notes for clients we don't have a dedicated guide for.

The two paths in one minute

Remote MCP / OAuth (preferred):

https://api.mindwiki.io/mcp

Paste this as your server URL. Approve in your browser. Done.

Personal API key (fallback):

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

Mint the key at mindwiki.io/account/api-keys with the scopes you want. Use this URL in your client.

Cursor

Cursor supports MCP via its config. Add MindWiki the same way you would in Claude Desktop or Codex:

json
{
  "mcpServers": {
    "mindwiki": {
      "url": "https://api.mindwiki.io/mcp?token=YOUR_API_KEY"
    }
  }
}

Cursor's specific config file location varies by release — consult Cursor's MCP docs for the exact path. Once configured, Cursor sees all 20 MindWiki tools.

Continue, Zed, and other IDE assistants

Most modern IDE assistants that support MCP follow the same pattern:

  • Find the MCP servers section in settings or config.
  • Add a server with url: https://api.mindwiki.io/mcp?token=YOUR_API_KEY (or just https://api.mindwiki.io/mcp if the client supports remote OAuth).
  • Restart or reload the assistant.

If the client requires a name field, use mindwiki.

Custom MCP clients

If you're building your own MCP-aware client, the OAuth flow is documented in MCP Server. The key endpoints:

  • Discovery: https://api.mindwiki.io/.well-known/oauth-authorization-server
  • Authorization: https://mindwiki.io/oauth/authorize
  • Token: https://api.mindwiki.io/oauth/token
  • DCR registration: https://api.mindwiki.io/oauth/register

PKCE with S256 is required. Scope is mcp.

For non-OAuth integrations, an API key in the URL works just as well.

Generic checklist for any client

If a client is supposed to support MCP but you're not sure how to add MindWiki:

  • Find the MCP / connector / integration setting in the client.
  • Look for a "remote MCP server" or "custom MCP" option.
  • Provide either the OAuth URL or the API-key URL.
  • If the client asks for transport, MindWiki uses standard MCP-over-HTTP at the URL above.
  • Verify by asking the client to use a MindWiki tool — mindwiki_search or search is a good first call.

Verifying connections

Regardless of client, confirm on the MindWiki side:

If a client never appears in either, the connection didn't complete. Re-run setup.

Want a guide for your client?

If you'd like a dedicated guide for a specific MCP client, send the request to support@mindwiki.io. We add guides for clients we see frequently.

Where to go next