Muse Code
Configure MindWiki’s hosted MCP server in Muse Code to bring project notes, decisions, and research into a coding session.
Validation status: This setup follows the official Muse Code configuration documentation. End-to-end MindWiki verification with Muse Code is pending. It is separate from the Muse consumer connector, whose directory launch is also pending.
Requirements
Use a MindWiki Pro or Power account with synced notes and a Muse Code installation that supports remote MCP servers and OAuth. MindWiki and Muse subscriptions are separate.
Add the server
Merge this entry into the mcp_servers object in ~/.config/muse/settings.json. Preserve your other settings and existing servers.
{
"mcp_servers": {
"mindwiki": {
"transport": "streamable_http",
"url": "https://api.mindwiki.io/mcp",
"enabled": true,
"mode": "optional"
}
}
}Optional mode lets Muse Code continue if MindWiki is temporarily unavailable. Use required mode only if your workflow must stop without vault access.
Sign in and verify
muse mcp login mindwikiComplete MindWiki’s browser approval. Then use /mcp in Muse Code to inspect the server and tools. Ask it to search for a known note, read the matching page, and cite its source. Verify saving separately if you granted capture or write access.
MindWiki uses OAuth discovery and dynamic client registration. If your Muse Code policy disables dynamic registration, an administrator will need to review that policy before this setup can authenticate. Do not replace OAuth with a token pasted into a prompt.
Disconnect
muse mcp logout mindwikiAlso revoke the connection in MindWiki Connections if you want to invalidate its server-side credentials. Removing a local login alone should not be treated as proof of server-side revocation.
See the Muse troubleshooting guide for plan, scope, sync, and account checks. For exact CLI behavior and configuration updates, consult the official Muse Code extensibility documentation and configuration reference.