Connect your AI assistant to Deacon

1. In ChatGPT open Settings → Connectors → Advanced and turn on Developer mode. It is limited to some plans, and on Business and Enterprise an admin may need to allow it first.
2. Back in Connectors choose Create. Name it, paste the server URL, and set authentication to OAuth.
3. Start a chat, open the + menu, choose Developer mode and switch the connector on. Sign in to Deacon when asked.

1. Use claude.ai in a browser or Claude Desktop. Custom connectors can’t be added from the mobile app, but once added they work there too.
2. Open Settings → Connectors (newer versions label it Customize → Connectors) and choose Add custom connector.
3. Paste the server URL and add it. Sign in to Deacon when the window opens, then switch the connector on in a chat.

The free plan allows one custom connector. On Team and Enterprise an organization owner adds it first, then each member clicks Connect.

1. Open Settings → Connectors and choose + Custom connector, then Remote. It needs a paid plan, and on Enterprise an admin must allow it.
2. Enter a name and the server URL, choose Streamable HTTP if asked, and set authentication to OAuth.
3. Finish the Deacon sign-in in the browser tab, then enable the connector in a thread.

1. In Le Chat open the side panel, then Intelligence → Connectors, and choose + Add Connector.
2. Switch to the Custom MCP Connector tab, enter a name and the server URL, and choose Connect.
3. Sign in to Deacon, then enable the connector in a new chat. Adding one needs an admin on team workspaces.

claude mcp add --transport http deacon https://deacon.kecker.co/mcp

Then run /mcp inside a session and choose Authenticate (or run claude mcp login deacon in your shell) to sign in to Deacon. Check with claude mcp list.

Add this to ~/.codex/config.toml:

[mcp_servers.deacon]
url = "https://deacon.kecker.co/mcp"

Then run codex mcp login deacon to sign in to Deacon. codex mcp list shows what is configured.

gemini mcp add -s user --transport http deacon https://deacon.kecker.co/mcp

Restart Gemini CLI and run /mcp to check the connection. If it asks you to sign in, follow the browser prompt. Prefer editing by hand? Put "deacon": { "httpUrl": "https://deacon.kecker.co/mcp" } under mcpServers in ~/.gemini/settings.json.

agy mcp add deacon https://deacon.kecker.co/mcp

The address is recognised as an HTTP server automatically. Run agy mcp list to confirm, then sign in to Deacon if prompted.

Add this to ~/.cursor/mcp.json (or .cursor/mcp.json inside one project):

{
  "mcpServers": {
    "deacon": { "url": "https://deacon.kecker.co/mcp" }
  }
}

Cursor opens a browser tab to sign in to Deacon the first time a tool is used. Restart Cursor if the server doesn’t show up.

Press Cmd/Ctrl+Shift+P, run MCP: Add Server, pick HTTP and paste the URL. Or add this to .vscode/mcp.json:

{
  "servers": {
    "deacon": { "type": "http", "url": "https://deacon.kecker.co/mcp" }
  }
}

Note the key is servers, not mcpServers. Use Copilot Chat in Agent mode, trust the server, and sign in to Deacon when the browser opens.

Open the MCP config from the Cascade panel (… menu → MCP config) and add:

{
  "mcpServers": {
    "deacon": { "serverUrl": "https://deacon.kecker.co/mcp" }
  }
}

Refresh the MCPs list, or restart Windsurf, then sign in to Deacon when prompted.

Open Settings → AI → MCP Servers, or add this to settings.json:

{
  "context_servers": {
    "deacon": { "url": "https://deacon.kecker.co/mcp" }
  }
}

Zed starts the sign-in to Deacon for you. The key must be context_servers.

Add a remote MCP server (Streamable HTTP) with the URL above. Sign-in uses standard OAuth, so there is no token or key to copy. If your client only supports local (stdio) servers, bridge it with npx mcp-remote https://deacon.kecker.co/mcp.