Devin

Connect Devin CLI or the Devin Local editor agent to your MindWiki vault. Give implementation work a durable record of requirements, design decisions and verified outcomes that other agents can use too.

Let Devin prepare setup

Paste this into Devin with its configuration-editing tools enabled. It can prepare the connection; you complete browser sign-in and any host approval.

Paste into your agent

Configure Devin CLI

bash
devin mcp add --scope user mindwiki https://api.mindwiki.io/mcp
devin mcp login mindwiki

Complete browser sign-in, then start or refresh your Devin session. Use devin mcp list to inspect the connection. The Devin Local agent in the desktop editor uses the Devin CLI configuration; legacy Windsurf / Cascade uses a different settings file.

For a separately hosted Devin environment, configure the MCP connection through that environment's supported controls rather than assuming your machine's settings were copied there.

Complete the MindWiki connection

On MindWiki's authorization page, review the account and requested permissions. New users choose a MindWiki email name, save the generated access key and continue. Existing users select Use an existing MindWiki account and sign in to the account that owns their vault. Access Keys explains both paths.

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:

text
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 workflows

  • “Read our project brief and migration constraints from MindWiki before planning the implementation.”
  • “Save a release handoff that separates implemented behavior, tests and deployment evidence.”
  • “Find the debugging note another agent left and verify whether it applies to this failure.”

A shared vault is useful for moving context between an interactive coding session and later review. Save the result of the work and the evidence needed to assess it, rather than large raw logs.

Troubleshooting

Use devin mcp get mindwiki to inspect the configured server. Re-run devin mcp login mindwiki if authentication is needed. If you changed OAuth settings and the old login no longer works, log out that server and authenticate again. A CLI server available only in local scope may not be visible from another project.

Permissions and disconnecting

The tools available depend on the scopes you approved and your vault's agent permissions. A read-only connection can search and read; writing requires the appropriate access. MindWiki currently includes the same features on Free, Pro and Power. The agent provider's plan and workspace rules are separate.

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.

More help

MCP tools · Agent permissions · All AI agents

Setup reference: Devin MCP configuration, checked October 20, 2026.