Integrations

Bring the tools you already use into one knowledge workflow. MindWiki connects AI clients, your apps, email capture, and custom scripts to the same vault, so research and decisions can move into useful work without repeatedly copying context between systems.

Start with the connection closest to your work. Use MCP for an interactive agent, email for quick inbound capture, the apps to read and write yourself, or the REST API for a custom integration.

Choose your connection

You want to	Use	Start here
Ask an AI to use your saved knowledge	An authorized MCP connection	Choose an agent below.
Work in your browser	MindWiki Cloud	Open your vault.
Write locally and work with attachments	MindWiki Mac app	Apps & Sync.
Capture and read away from your desk	MindWiki iPhone app	Apps & Sync.
Save an email or quick forwarded note	Your personal capture email	Capture Methods.
Build a script or custom service	Scoped REST API credentials	API Access.

These paths share account data, but they expose different controls. An email capture address accepts incoming material; an API key authenticates scripts; your sign-in access key authenticates you on MindWiki. Use each for its intended purpose.

AI client setup guides

Choose the guide for your client and interface:

MCP lets a compatible client discover MindWiki's tools. The client decides how to install a server, which tools to expose, and when to ask for approval. Its plan, workspace policy, or administrator settings can affect connector availability. A platform-specific guide is more useful than one generic configuration pasted everywhere.

The normal MCP connection flow

Add MindWiki using the client's supported connector or MCP settings.
Use https://api.mindwiki.io/mcp as the remote server endpoint where requested.
Complete authorization on MindWiki's own page.
Sign into your existing MindWiki account to reuse its vault, or finish new-account setup.
Review the requested access, approve, and return to the client.
Enable the connection for your conversation or workspace if the client requires it.
Ask the agent to read a real page, then verify the result.

Coding-agent guides include a copyable setup sentence when the agent can configure its own environment. Keep account authorization in your hands; pasting a setup request does not grant account access by itself.

Keep one account as you add agents

A second agent should connect to your existing account. It receives a separate grant, while your pages, files, and capture address stay together. This makes it possible to research with one tool, plan with another, and implement with a third.

Manage OAuth grants in Connections. Use a separate API key per script or integration so you can revoke it individually. Removing one credential stops future requests using it; it does not delete your vault or erase content already retrieved by another service.

Connect email and custom workflows

Forward an email to the capture address shown in your account. The message becomes a page you and your agents can retrieve. Email attachment information is recorded, while original file uploads use the supported Mac attachment workflow.

For scripts, the REST API supports documented vault operations such as retrieval and capture. Keep API keys in environment variables or a secret manager. A custom integration is something you build against that API; it does not imply a ready-made connector exists for every external application.

A useful first integration test

Save one short project brief. Ask the connected agent to retrieve it, name its path, and summarize the next action. If you granted capture access, ask it to save a concise follow-up and open the page yourself.

Once this loop works, introduce a second agent or a recurring Context Pack. You will have a concrete workflow to extend rather than a collection of configured connections with no saved work behind them.

Next: Quick Start, MCP Server, and Shared Agent Memory.