Skip to content
Connect your AI

GitHub Copilot

Use MindWiki from GitHub Copilot agent sessions in VS Code. Bring project requirements and previous decisions into implementation, then save the findings that should survive the editor session.

Let your agent prepare setup

If your Copilot agent can edit MCP configuration, copy this into the session. Complete the editor's own server approval and browser sign-in when prompted.

Paste into your agent

Add MindWiki in VS Code

  1. Open the Command Palette and run MCP: Add Server.
  2. Choose HTTP and enter https://api.mindwiki.io/mcp.
  3. Use mindwiki as the server ID.
  4. Choose the configuration destination for your Copilot session. For a personal setup, use the available global configuration option.
  5. Review the server prompt, start the connection and complete browser sign-in.
  6. Open the session's tool controls and enable the MindWiki tools you want the agent to use.

The editor's selected agent harness determines which MCP settings and tools it uses. A configuration for a different harness or a local editor does not automatically configure GitHub's hosted coding agent.

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:

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

  • “Read our requirements from MindWiki and compare them with the code before proposing this change.”
  • “Find the previous incident note for this error, then check whether the same cause applies here.”
  • “Save a short handoff with the files changed, tests run and remaining work.”

Use the first read prompt to inspect an actual tool result in Copilot's conversation. Once that works, test a small capture separately before relying on the agent to maintain a project handoff.

Troubleshooting

If no tools appear, inspect the selected harness, MCP server status and tool picker. If your organization blocks custom servers, ask an administrator about its approved connection policy. If sign-in expires, use the server's authentication controls and retry the read check.

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.

More help

MCP tools · Agent permissions · All AI agents

Setup reference: VS Code MCP setup, checked October 20, 2026.