Other MCP Clients

Connect another MCP-compatible assistant to the same MindWiki vault. You need a client that can use a remote HTTPS MCP server and complete browser-based OAuth; a chat box alone cannot install an integration.

Start with the native connection controls

1. Open your client's MCP or external-tools settings.
2. Add a remote server named MindWiki.
3. Set the URL to https://api.mindwiki.io/mcp and choose Streamable HTTP if a transport is requested.
4. Use OAuth discovery and complete the browser sign-in.
5. Enable the server's tools for your current conversation or agent session.

Use your client's own configuration format. Some use mcpServers, others use different keys or a command-line setup. You do not need to run a local MindWiki server, supply a static OAuth client secret, or send your sign-in key to the agent.

Let a configuration-capable agent help

This works as setup assistance when the agent can edit its own client configuration. If the host requires installation through a settings panel, use that panel first.

Complete the MindWiki connection

On MindWiki's authorization page, MindWiki Email + Access Key is the recommended sign-in method. Existing email-and-password accounts can choose Legacy Sign In; Sign in with Apple remains available. All methods open the same account and vault—no replacement account is required. New users choose Create a new vault, save their generated access key and continue. Review the requested permissions and choose read-only access when that is all you need. Access Keys explains the supported methods.

Return to your agent after approving. Your sign-in key belongs on MindWiki's pages, not in chat or an MCP configuration file. The client handles its own OAuth credentials.

Check that it works

Ask your agent:

Use MindWiki to read my account status, then search for a note about one of my projects. Read a matching page and cite its title and path. Tell me if the vault is empty rather than making up a result.

Inspect the tool result and compare it with a page in MindWiki Cloud. For a new vault, the agent can read the operating guide and initialize the starter pages when account status permits it.

To check saving after granting write or capture access, ask “Save a new MindWiki capture titled Connection check with today's date, then read it back and give me its path.” The same file is available in your MindWiki apps.

Useful shared-memory workflows

Ask the agent to read a project brief before working, save a concise decision afterward, or continue from a handoff written by another agent. A vault is shared knowledge for your connected agents, not a replacement for the host's own tool permissions or execution environment.

Custom integrations and scripts

Use a maintained MCP client runtime to handle OAuth, refresh and credential storage. Start from the MCP Server guide. For scripts that use HTTP directly, create a dedicated scoped API key and follow API Access. Sign-in access keys and integration API keys are different credentials.

Troubleshooting

If the client only supports launching local processes, check whether it has a maintained remote MCP transport before using this hosted URL. If authentication succeeds but tools do not appear, refresh the server's discovered tools and start a new session. For write errors, check the approved scope and your agent permissions.

Permissions and disconnecting

Available tools depend on the scopes you approved, your MindWiki plan and vault permissions, and the tools your client exposes. Free includes one external AI connection with core vault tools. See MCP tool access.

To disconnect just this client, revoke its grant in MindWiki Connections. Other agents keep their own connections. Never send access keys or OAuth tokens to support.

Choose a dedicated guide

Claude Code · Codex · Cursor · GitHub Copilot · Gemini CLI · Cline · Devin · Windsurf · Muse Code