Third-Party MCP Servers
Connect outside tools — Salesforce, HubSpot, GitHub, Linear, Jira, Notion, Stripe, and more — so your Statisfy agents can use them. Once connected, a server’s actions become a toolkit you can add to any agent in Agent Studio.What’s an MCP server? MCP (Model Context Protocol) is a common standard that lets AI assistants talk to outside tools. A “server” is just one connected tool — connect GitHub, for example, and your agents can read issues or open pull requests on your behalf.
This page is about connecting other tools into Statisfy so your agents can use them. If you instead want to connect an AI assistant like Claude to Statisfy, see MCP Server — that’s the opposite direction.
Prerequisites
Before you start, make sure you have:- Admin access — the MCP Servers tab under Integrations is visible to organization admins only.
- The tool’s credentials ready — for API-key servers (such as Stripe), have the API key on hand; for OAuth servers, your sign-in details for that tool.
- The server you want available in the catalogue — most common tools ship as ready-to-connect cards.
If you don’t see a standard OAuth-based MCP card for the tool you need in the catalogue, ask your Statisfy contact to provide it — or add it yourself as a custom server (custom servers support API Key authentication only).
Step 1 — Connect a server
Open Integrations → MCP Servers. You’ll see a catalogue of ready-to-connect servers, each with a badge showing how it signs in:- OAuth — sign in through the tool’s own login screen (no key to copy). Servers include Salesforce, HubSpot, GitHub, Linear, Atlassian (Jira), and Notion.
- API Key — paste a key from the tool (for example, Stripe). API-key servers are added through the Add Custom MCP Server option as well.
| Button | What it does |
|---|---|
| Connect | Start the sign-in (OAuth screen or API-key dialog) |
| Refresh | Re-check the connection and reload its available tools |
| Disconnect | Remove the connection — agents using its tools stop receiving them |
| Add another instance | Connect a second account of the same tool (where supported) |
Step 2 — Add your own server (optional)
If the tool you want isn’t in the catalogue, click the Add Custom MCP Server tile. In the Add Custom MCP Server dialog, fill in:- Name — what it’s called in Statisfy
- SSE URL — the server’s web address (your tool’s provider gives you this; SSE just means it streams updates live)
- Auth Type, API Key, and a Header name if the server needs a key
The Add Custom MCP Server option currently supports API Key authentication only.
Step 3 — Choose which tools need approval
Click a connected server, then click Available Tools to open its tools list. By default, tools run automatically when an agent calls them. If a tool does something sensitive (sending, deleting, charging), you can require a human to approve each use:- Check the box next to any tool to mark it approval-required.
- Use Select all / Clear all to do this in bulk, or Reset to undo.
- Click Save Approval-Required.
Step 4 — Use the tools in your agents
Connected servers show up as toolkits (marked with a plug icon, in the MCP category) in the Agent Studio toolkit picker. Add a toolkit to an agent the same way you add any other — see Creating Agents.When an approval-required tool is used
- In an Agent Studio flow: because automated flows can’t stop and wait, picking an agent that uses approval-required tools shows an “Auto-approve these tools?” prompt. Choosing Auto-approve lets the flow run those tools without pausing.
Disconnecting
Click Disconnect on a server’s card to remove it immediately. Any agent that relied on that server simply loses those tools; the agent itself is unaffected.Troubleshooting
A tool isn't showing up in the toolkit picker
A tool isn't showing up in the toolkit picker
Open the server card and click Refresh to reload its tools, then reopen the toolkit picker. If it’s a custom server, confirm the SSE URL and auth details are correct.
An agent keeps pausing for approval
An agent keeps pausing for approval
A tool it uses is marked approval-required. Open the server’s Available Tools list and uncheck that tool if it’s safe to run automatically, then Save Approval-Required — or, for flows, choose Auto-approve when prompted.
The connection shows as failed
The connection shows as failed
Click Refresh. For OAuth servers, reconnect to refresh the sign-in; for API-key servers, re-enter the key (it may have been rotated in the source tool).