Connectors
The MCP servers Delta MCP serves to your AI, and how to see them, sign in, choose which apps use them and put them back.
On this page
A connector is an MCP server that Delta MCP serves to your AI. The server stays exactly as it is. Delta MCP talks to it for your AI, and keeps every change in Activity.
What you see
The Connectors screen has up to three groups.
| Group | What it holds |
|---|---|
| Through Delta | Connectors your AI already uses through Delta MCP, each with its mode. |
| Can go through Delta | Connectors Delta MCP found and can take over. It lists where each one lives: an app’s settings, a Claude Code plugin or your claude.ai account. |
| Stays in Claude | Connectors that cannot go through Delta MCP, with the reason. |
Claude’s own connectors, such as Gmail, Google Calendar and Google Drive, run inside Claude behind its own sign-in. No other app can stand between them and your AI. Servers in Codex or Zed also wait here until their settings can be changed. See Supported AI apps.
Move a connector through Delta MCP
- Open Connectors and pick the connector under Can go through Delta.
- Wait for the check. Delta MCP first makes sure the connector answers, the way your apps would reach it. Nothing moves before.
- If it asks you to sign in, click Sign in and finish in your browser. If it needs a key, paste it.
- Click Optimize.
- Restart what the screen tells you to restart.
If the check fails, the screen says why: it did not answer in time, Delta MCP cannot start it, or it answered with an error. Your apps keep using it as they do now. Click Try again when you are ready.
A connector from your claude.ai account or a plugin is not in your apps’ settings, so Delta MCP adds it to the apps you tick. Its original stays on. Turn it off in Claude (Settings, then Connectors), or turn its plugin off in Claude Code. Otherwise your AI sees both and can use either.
Sign in
Most remote connectors use a sign-in in your browser. Delta MCP registers itself with the service, you sign in once, and it keeps the sign-in and renews it. A sign-in that cannot renew itself shows when it ends. When it has ended, your AI cannot use the connector. Delta MCP tells you, and Sign in again fixes it.
A sign-in only starts from the app, when you ask. The mcpdelta entry inside your AI app never opens a window: without a sign-in, it says one is needed.
Some services let no new app sign in on their own. If you have a key for one, made in its own settings, paste it when Delta MCP asks. GitHub works with a personal access key. Delta MCP keeps sign-ins and keys on your computer, in files only your user account can read.
Choose which apps use it
Under Used in, tick the apps that should use the connector. Unticking the last one puts it back in your apps, after you confirm.
Choose what it can change
Under When your AI wants to change something, pick a mode for the connector. Advanced shows each action and lets you set one apart or switch it off. See Modes.
Add a connector by hand
- Click the + at the top of the list.
- Give it a name.
- Type its address, or the command that starts it.
- Click Add, then move it as above.
Put it back
Click Put back in my apps. Your apps use the connector directly again, exactly as before. You can bring it back at any time. To return all of them at once, see Put everything back.
Keeping its actions up to date
Delta MCP reads a connector’s list of actions again each time a conversation connects to it. It only lists them and never calls one. From a terminal, mcpdelta refresh lists them between conversations: every remote connector, and a local one with no list yet or a newer version on npm. Updating connectors on its own from the app is not yet there.
Something missing or wrong? Open an issue