Outboundry's MCP (Model Context Protocol) server lets compatible AI assistants such as ChatGPT, Claude, Cursor, and VS Code interact with your Outboundry workspace.
Once connected, you can ask your AI assistant to perform Outboundry tasks using natural-language instructions instead of manually navigating through the app. For example, you could ask your assistant to find leads who engaged with your outreach, create a follow-up campaign, or review and respond to conversations.
MCP is an open standard that allows AI assistants to connect to applications and use their data and actions.
Outboundry provides an MCP server that allows compatible AI tools to securely access and operate within your Outboundry workspace.
You connect your AI assistant once, authorize the required access, and then use the assistant to work with Outboundry.
Note: Outboundry is the MCP server. You use a separate MCP-compatible AI client, such as ChatGPT, Claude, Cursor, or VS Code, to interact with it.
Before connecting an AI assistant to Outboundry, make sure you have:
An active Outboundry account.
Access to the Outboundry workspace you want to connect.
An AI client that supports MCP and HTTP transport.
The appropriate permissions within your Outboundry workspace.
The Outboundry MCP server uses a single endpoint:
https://api.outboundry.com/api/v1/mcp
You can also copy the endpoint directly from the Outboundry MCP Settings page.
In Outboundry, go to:
Settings → Developer → MCP
You can also open the MCP Settings page directly.
The MCP page provides:
An explanation of MCP
The Outboundry MCP endpoint
A button to copy the endpoint
Your active MCP connections
Connection status
Connected client
Workspace
Connected user
Connection date
Last activity
Request count
Options to reconnect or disconnect a connection
Copy the Outboundry MCP endpoint from the MCP Settings page.
https://api.outboundry.com/api/v1/mcpThe same endpoint is used regardless of which supported AI client you're connecting or which Outboundry workspace you're using.
Outboundry supports OAuth 2.1 for major MCP clients. If your MCP client doesn't support OAuth, you can use a workspace API key as a fallback.
Choose your AI client below for the setup instructions.
Availability: Pro, Team, or Enterprise
In ChatGPT, go to:
Settings → Apps and Connectors → Advanced
Enable Developer Mode.
Go to:
Settings → Apps and Connectors → Create app
Enter:
Name: Outboundry
Endpoint: https://api.outboundry.com/api/v1/mcp
Authentication: OAuth
Click Create.
A browser window opens and takes you to the Outboundry authorization page.
Sign in to your Outboundry account if required and review the requested access.
Select the workspace you want to connect and click Authorize.
Return to ChatGPT.
Once the authorization is complete, the Outboundry connection becomes available to ChatGPT.
ChatGPT <> Outboundry
In Claude, go to:
Settings → Connectors
Choose the option to add a custom connector.
Paste:
https://api.outboundry.com/api/v1/mcp
Click Connect.
A browser window opens.
Sign in to Outboundry, select the workspace you want to connect, review the requested permissions, and click Authorize.
Once authorization is complete, the Outboundry connection becomes available in Claude.
Claude Code can connect to Outboundry from the terminal.
Run:
claude mcp add --transport http outboundry https://api.outboundry.com/api/v1/mcpA browser window opens.
Sign in to Outboundry and click Authorize after reviewing the requested access.
Return to Claude Code. The Outboundry MCP server is now connected.
Open the VS Code Command Palette.
Search for:
MCP: Add Server
Choose HTTP as the transport type.
Enter:
https://api.outboundry.com/api/v1/mcp
When prompted, authorize the connection in your browser.
Sign in to Outboundry, select your workspace, review the requested permissions, and click Authorize.
The Outboundry MCP server is now connected to VS Code.
In Cursor, go to:
Settings → MCP
Click Add New Server.
Choose HTTP and enter:
https://api.outboundry.com/api/v1/mcp
When prompted, authorize the connection in your browser.
Sign in to Outboundry, select the workspace you want to connect, review the permissions, and click Authorize.
The Outboundry MCP server is now available in Cursor.
If you're using an MCP client other than the supported clients above:
Add a new MCP server.
Select Streamable HTTP or HTTP transport.
Enter the Outboundry MCP endpoint:
https://api.outboundry.com/api/v1/mcp
Use OAuth 2.1 if your client supports it.
If OAuth isn't supported, authenticate using an Outboundry workspace API key.
Complete the authorization process in your browser.
Important: HTTP transport is required. Clients that don't support streamable HTTP cannot connect to the Outboundry MCP server.
When an AI client connects to Outboundry, you'll be redirected to the Outboundry authorization page.
The authorization screen shows:
The AI client requesting access
The permissions being requested
The Outboundry workspace that will be connected
Review the information carefully before approving the connection.
Select the appropriate workspace and click Authorize.
Each MCP connection is associated with one specific workspace. A connection cannot access another workspace unless that workspace is separately authorized.
The MCP connection provides four main groups of capabilities.
The AI assistant can access:
Lead lists
Contact information
Enrichment data
Reply history
This allows you to ask questions about your prospects and use lead information while performing other tasks.
The AI assistant can:
Create campaigns
Build campaign sequences
Change campaign settings
Start campaigns
Pause campaigns
The AI assistant can send and schedule:
Email messages
LinkedIn messages
Sending still follows Outboundry's existing sending rules and limits.
The AI assistant can access conversations and:
Summarize replies
Draft responses
Reply to conversations
This allows you to use your AI assistant to help manage conversations in your Unified Inbox.
MCP does not bypass Outboundry's existing permissions or sending safeguards.
Daily sending caps, warmup limits, scheduling windows, and mailbox-level throttles continue to apply.
For example, if an AI assistant is asked to send more emails than a mailbox's daily limit allows, Outboundry will enforce the applicable limit.
Every MCP connection is tied to a specific Outboundry workspace.
If you want to connect another workspace, authorize a separate connection for that workspace.
The MCP connection inherits the permissions of the user who authorized it.
For example, if your Outboundry role doesn't allow you to create campaigns, an AI assistant connected through your account won't be able to create campaigns either.
You can manage all your active MCP connections from:
Settings → Developer → MCP
The connections table shows information such as:
AI client
Workspace
Connected by
Connection date
Last activity
Request count
Connection status
This makes it easy to identify which AI tools currently have access to your workspace.
The connection is authorized and working.
The AI client can access Outboundry according to the permissions of the connected user.
The connection's authentication is no longer valid.
Click Reconnect to authorize the connection again.
If a connection shows Needs Re-auth:
Go to Settings → Developer → MCP.
Find the affected connection.
Click Reconnect.
Complete the authorization process in your browser.
Once authorization is complete, the connection becomes active again.
You can revoke an AI client's access to your workspace at any time.
Go to Settings → Developer → MCP.
Find the connection you want to remove.
Click the connection's action menu.
Select Disconnect.
Confirm the disconnection.
Disconnecting immediately revokes the connection's access to the workspace.
You can reconnect the AI client later if needed.
OAuth 2.1 is the recommended authentication method because it provides a separately identifiable and revocable connection for each client and workspace.
If your MCP client doesn't support OAuth, you can use an existing Outboundry workspace API key as a fallback.
When using an API key:
The key is used as a bearer token.
The connection appears as Other tool because the API key doesn't identify a specific MCP client.
The API key is a long-lived credential, so treat it as a secret.
Recommendation: Use OAuth whenever your MCP client supports it.
Only connect AI clients that you trust.
An authorized MCP connection can perform actions within the permissions available to the user who connected it.
Before authorizing a connection:
Verify the AI client you're connecting.
Confirm the correct Outboundry workspace is selected.
Review the permissions displayed on the authorization screen.
Disconnect integrations you no longer use.
Workspace administrators can view and revoke MCP connections from the MCP Settings page.
If the authorization page opens while you're signed into the wrong Outboundry account, don't authorize the connection.
Switch to the correct account and restart the authorization process.
The authorization screen identifies the currently signed-in account to help you verify that you're connecting the correct user.
The connection's authentication token may have expired or been invalidated.
Go to:
Settings → Developer → MCP
Find the connection and click Reconnect.
Copying the endpoint URL does not create a connection by itself.
You must add the endpoint to your MCP-compatible client and complete the authorization process.
If your client supports MCP but doesn't implement OAuth 2.1, you can use a workspace API key as the authentication method.
Make sure the client supports Streamable HTTP.
Outboundry MCP requires HTTP transport.
If your MCP client doesn't support Streamable HTTP, it cannot connect to the Outboundry MCP server.
If you authorize the same client for the same workspace again, the newer authorization replaces the previous connection rather than creating a duplicate connection.
Yes.
Each workspace requires its own authorization. Each connection is independently scoped and can be revoked separately.
Your MCP connection follows your current Outboundry permissions.
If your role is downgraded, the AI assistant's effective permissions are also reduced.
No.
ChatGPT, Claude, Claude Code, VS Code, and Cursor support OAuth 2.1, so you can authorize the connection directly through Outboundry without manually handling an API key.
Outboundry supports MCP-compatible clients that support the required HTTP transport. Setup instructions are currently available for ChatGPT, Claude, Claude Code, VS Code, Cursor, and other compatible MCP clients.
Yes. The MCP connection can create and manage campaigns, build sequences, change campaign settings, and start or pause campaigns, subject to your Outboundry permissions.
Yes. The MCP connection can send and schedule email and LinkedIn messages on your behalf.
Outboundry's normal sending limits, warmup requirements, scheduling windows, and mailbox throttles still apply.
Yes. The connection can access lead lists, contact information, enrichment data, and reply history according to the permissions of the user who authorized it.
Yes. The MCP connection can access conversations and help summarize, draft, and send replies.
No.
Each connection is scoped to exactly one workspace. To connect another workspace, authorize a separate connection.
Yes.
Go to Settings → Developer → MCP, find the connection, and select Disconnect.
The connection's access is revoked immediately.
No.
MCP is designed for AI-assisted, conversational workflows. Outboundry's REST API and webhooks remain available for deterministic integrations and non-conversational automation.
Once your AI assistant is connected to Outboundry, you can describe the task you want it to perform in natural language.
For example:
"Show me the leads who replied to my recent campaign."
"Create a follow-up campaign for the leads who haven't replied."
"Summarize my latest replies and identify the prospects who seem interested."
"Find the leads who opened my emails but haven't replied yet."
"Pause the campaign called [campaign name]."
"Draft replies to the conversations that need my attention."
The exact actions available to your AI assistant depend on the client's capabilities, your Outboundry permissions, and the data available in your workspace.
Start with a trusted AI client.
Use OAuth whenever available.
Start with Co-pilot-style or review-based workflows when you're testing AI-driven outbound actions.
Review the workspace and permissions before authorizing.
Monitor your MCP connections regularly.
Disconnect clients you no longer use.
Never share your workspace API key publicly or paste it into an untrusted application.
Remember that MCP does not bypass Outboundry's sending limits or your workspace permissions.