Connecting AI Assistants via MCP

ActionBridge runs one MCP server (Model Context Protocol — an open standard that lets AI assistants connect to apps) for the whole AB family: assistants like Claude, ChatGPT, Cursor, Windsurf, Codex CLI, and Antigravity can read and manage your AB Projects tasks and documents, and your AB Sales pipeline. Setup is a URL and a sign-in — and the URL is the step people get wrong.

Before you start

• An existing AB account. If you don’t have one yet, set it up via Microsoft Teams first (see Supported Platforms).
• The server URL: https://mcp.actionbridge.io/mcp
• Your Microsoft 365 work or school account, or your AB email and password, to sign in.

The same setup is also documented on actionbridge.io/en-US/mcp.

Where to enter it, per client

Claude Desktop

1. Open the connector list. Claude Desktop → Settings → Connectors → Add Custom Connector.
2. Enter the details. Name: ActionBridge · URL: https://mcp.actionbridge.io/mcp
3. Click Connect. A browser window opens asking you to sign in.
4. Sign in with Microsoft, or with your AB email and password.
5. Done. Claude Desktop registers automatically and lists the AB tools.

Claude Cowork

In Cowork, open your MCP configuration and add:

URL:  https://mcp.actionbridge.io/mcp
Auth: OAuth (automatic)

Cowork opens a browser window the first time it connects, using the same sign-in as Claude Desktop.

ChatGPT

1. Open connectors. ChatGPT → Settings → Connectors → Add custom connector (needs a Plus, Pro, Business, or Enterprise plan).
2. Enter the details. Name: ActionBridge · MCP Server URL: https://mcp.actionbridge.io/mcp — make sure the /mcp path is included.
3. Click Connect and sign in with Microsoft or your AB email and password.
4. Done. ChatGPT returns to the connector list with ActionBridge shown as connected.

Cursor, Codex CLI, Windsurf, and Antigravity

These editors use a JSON configuration file for MCP servers. The surrounding format varies by tool, but the server block is the same:

{
  "mcpServers": {
    "actionbridge": {
      "url": "https://mcp.actionbridge.io/mcp"
    }
  }
}

The first time the editor connects, it opens a browser window so you can sign in. No client ID or secret is required.

What you get once connected

• Tools — ab_* tools for AB Projects (tasks, schedule, Documents) and ab_crm_* tools for AB Sales (leads, opportunities, activities). The full list is in the MCP Tools Reference.
• Prompts — ready-made slash commands (like ab-standup for a daily brief) that appear in clients that support MCP prompts.
• Resources — read-only feeds (your tasks today, this week, your projects) that the client can pull as background context.

Managing your MCP access

When you connect a client, ActionBridge automatically issues an API key (a private access token) behind the scenes, scoped to your account — the assistant acts only as you and only on data you can already see (see Who Can See What).

• To disconnect a client: remove the ActionBridge connector in that AI client (delete the custom connector in Claude/ChatGPT, or remove the server block from the editor’s config). It has to sign in again if re-added.
• To revoke access server-side (say, a device was lost): contact support@actionbridge.io — a self-serve key-management screen isn’t available yet.
• Everything an assistant does is auditable: each change is recorded in the item’s change history and posted to the linked Teams channel with clear AI disclosure.

Troubleshooting

Still stuck? Contact support@actionbridge.io. If your AI client shows a reference code — for example ofid_... from ChatGPT, or any request ID — include it: it lets the team pull the exact session from the server logs.