​

Third-Party MCP Servers

Connect outside tools — Salesforce, HubSpot, GitHub, Linear, Jira, Notion, Stripe, PostHog, 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.

​

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 or PostHog), 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.

​

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 or PostHog). API-key servers are added through the Add Custom MCP Server option as well.

On each server card you’ll find: For API-key servers, the Connect dialog asks for the API Key, an optional server address, and a label to tell multiple connections apart.

​

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

​

Step 3 — Choose which tools need approval

On a connected server’s card, click its tool count (for example, 12 tools) to open its Available Tools list. Tools are grouped by what they do (Read-only tools, Write/Delete tools, Interactive tools, Others). If a tool does something sensitive (sending, deleting, charging), you can require a human to approve each use:

1. Set a whole group to Always allow or Needs approval, or change individual tools (the group then shows Custom).
2. Click Reset to undo unsaved changes.
3. Click Save Approval Policy.

A policy you save here applies wherever the server’s tools run, unless Stella, the Workbench agent or a Digital Worker sets its own (see Choosing tools for the Workbench agent and Digital Workers). It covers every tool on that server: tools you didn’t change are saved with the setting the list shows (by default, Always allow). When you’ve never saved a policy for a server, the default depends on who calls the tool:

• Agent Studio agents and flows run the tool automatically.
• The Workbench agent pauses tools that change something in the external system for approval.
• Digital Workers run read-only tools automatically. For tools that change something in the external system, the worker falls back to its Default mode under Autonomy: Smart runs them automatically, HIL pauses them for approval.

​

Step 4 — Use the tools in your agents

Connected servers show up as toolkits (marked with a plug icon) in the MCP Servers section of the Agent Studio Add Tools picker. API Tools toolkits for your connected integrations, such as Zendesk, Notion, and Salesforce CPQ, appear in a separate API Tools section. Add a toolkit to an agent the same way you add any other. See Creating Agents. Beyond Agent Studio, the same connected tools can be enabled for:

• The Workbench agent — in its settings, pick the servers and API toolkits it may use (see below). See Workbench.
• A Digital Worker — on the worker’s MCP/API Tools tab. See Configuring a Digital Worker.
• Stella — under Settings → Config → Admin → Stella AI, in MCP Servers and API Tools. See Stella’s external tools.

​

Choosing tools for the Workbench agent and Digital Workers

The Workbench agent setting and a Digital Worker’s MCP/API Tools tab share the same editor, with two sub-tabs:

• MCP Servers — click Add server and pick a connected server. Then select the tools the agent may use, and optionally fill in Prompt for this server to steer when it uses them.
• API Tools — click Add API Toolkit and pick a connected integration, such as Zendesk, Jira, Notion, or Salesforce CPQ. All of the toolkit’s actions start selected. Clear the actions the agent doesn’t need, and optionally fill in Prompt for this toolkit.

On both sub-tabs, each tool has an Always allow / Needs approval dropdown, and each group (Read-only tools, Write/Delete tools, and so on) has one too. Setting a group applies to every tool in it; changing a single tool makes the group show Custom. Always allow runs the tool without asking; Needs approval pauses it for human review. These approval settings belong to the surface you set them on. Stella, the Workbench agent and each Digital Worker keep their own, so the same tool can pause for review in one place and run on its own in another. They override everything else: the server’s approval policy on the Integrations page, the toolkit’s defaults, and a Digital Worker’s Default mode. A newly added server starts from its Integrations page policy, and a newly added API toolkit starts from its defaults (write actions need approval, read actions don’t). Only connected servers and Toolkits appear in these lists. If API Tools shows No API Tools are available, connect the integration on the Integrations page (Admin Apps tab) first. For the actions each Toolkit offers, see API Tools toolkits. If a server or API toolkit disconnects, Statisfy keeps your selection. Reconnect it on the Integrations page to edit the selection again.

​

Stella’s external tools

Admins can let Stella use connected MCP servers and API Tools in chat, in addition to its built-in tools. This selection is separate from the Workbench agent’s and from each Digital Worker’s.

1. Go to Settings → Config, choose Admin, and open the Stella AI tab.
2. Find MCP Servers and API Tools.
3. On the MCP Servers and API Tools sub-tabs, add the servers and API toolkits Stella may use and select their tools.
4. Click Save.

If another admin saves this setting while you’re editing, Statisfy warns you. Click Discard my changes to keep their version, or Overwrite with my changes to replace it. Tools set to Needs approval in Stella’s setting pause for your approval in the chat; tools set to Always allow run on their own. A server saved in this setting before per-surface approval existed keeps following its Integrations page policy (and on a server with no saved policy, Stella pauses every tool that changes something). See Approving Stella’s actions. Tools you marked approval-required stay gated in these surfaces too — they pause for human review instead of running automatically.

​

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.
• In a Digital Worker session: the call pauses until someone approves it. When the worker is replying to a customer, the tool-approval card appears in that conversation in the Digital Workers pool. During the worker’s own proactive work, the card goes to the worker’s reviewer, in their Workbench queue.

​

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

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

A tool it uses is set to Needs approval. For Stella, the Workbench agent or a Digital Worker, set that tool to Always allow in that surface’s MCP Servers or API Tools settings. For an Agent Studio agent, open the server’s Available Tools list, set the tool to Always allow if it’s safe to run automatically, then click Save Approval Policy — or, for flows, choose Auto-approve when prompted. For a Digital Worker on a server with no saved policy, remember that tools that change something follow the worker’s Default mode: a HIL worker pauses every one of them for approval.

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).

​

Support

Questions? Email support@statisfy.com or contact your Customer Success Manager.