Gemini CLI
Use Gemini CLI with a persistent store of research, specifications and project notes. The terminal agent can retrieve earlier work, save findings and leave context for another session or agent.
Let Gemini CLI prepare setup
Paste this into Gemini CLI with its configuration-editing tools enabled. It can prepare the connection; you complete browser sign-in and any host approval.
Configure manually
Add a user-level HTTP server in your terminal:
gemini mcp add --transport http --scope user mindwiki https://api.mindwiki.io/mcpStart Gemini CLI and authenticate the server:
/mcp auth mindwikiGemini CLI discovers MindWiki's OAuth settings. Complete the browser flow, then use /mcp list to inspect the available tools. You do not need to configure a static client secret or paste your access key into the terminal conversation.
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 terminal workflows
- “Search my prior research on this approach, read the relevant notes and distinguish evidence from assumptions.”
- “Compare the project requirements in MindWiki with the work in this directory.”
- “Capture the useful conclusions from this session, including unresolved questions and the next experiment.”
Use short project and topic names in your saved page titles to make later retrieval easier.
Troubleshooting
Use gemini mcp list from the terminal or /mcp list inside the agent to inspect connection errors. Run /mcp auth mindwiki to reauthenticate. If Gemini can connect outside a sandbox but not inside it, inspect that environment's network permissions. Keep tool confirmations in place; setup does not require trusting every future tool call automatically.
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: Gemini CLI MCP documentation, checked October 20, 2026.