Connect an MCP Server to Percy

Features Configuration → MCP Servers (also linked from the AI Assistant tab) connects Percy to tools that live outside Perceny: a CRM, an inventory system, a knowledge base, anything that speaks the Model Context Protocol over HTTPS. Once a server is connected, its tools appear to Percy Assistant on the phone and in texts, to Percy Copilot for your team, or to both.

The tab is only visible to members whose role has the Manage MCP Servers permission. Managers do not have it by default; grant it under Customize what a role can do.

Add a serverCopy a link to this section

Add Server opens a form with two ways in:

• Fill it in. A name, the server address (HTTPS), and the transport. Streamable HTTP is the default; a server that only speaks the older SSE transport is picked up automatically on the first test.
• Paste a config. Paste the JSON block a vendor publishes for Claude Code ("mcpServers": { ... }) and Perceny reads the name, address and headers out of it. Each server in the block becomes a row.

The tool prefix is derived from the name and is how Percy tells one server's tools from another's: a server called "Shopify" offers shopify__find_order. Change it only if two servers would clash.

Keys and sign-insCopy a link to this section

Headers carry an API key or bearer token the server expects on every request. They are stored encrypted and never shown again; the row says which header names are set. Typing a header on an edit replaces the saved ones; Remove Saved Headers clears them without replacing them.

A server that uses OAuth asks for a sign-in instead: Authorize sends you to the provider, and the row shows Needs authorization until you come back. Only the authorization you started can finish, and a test run while you are away never disturbs it.

Test and choose toolsCopy a link to this section

Test connects, lists the server's tools and records the result on the row: Connected with the tool count, Needs authorization, or Failed with the reason. Perceny tests every connected server again each night and when you switch a server back on.

Tools opens the list. Each tool can be turned on or off for each surface:

• Percy Assistant gets only read-only tools unless you turn a write tool on for it. A caller should never be able to change your data through a tool you did not choose.
• Percy Copilot gets every tool. A tool that writes is parked behind the same confirmation step as Percy's own actions, so a team member approves before anything changes.

What Perceny refusesCopy a link to this section

A server address must be a public HTTPS host. Addresses inside private networks, loopback and cloud metadata ranges are refused when you save and again on every call, and a redirect to another address is never followed. The tool names offered to the model are bounded and sanitized, and a tool's answer is handed to Percy as data, never as instructions.

LimitsCopy a link to this section

Ten servers per business, forty tools offered on one turn, and a per-server rate limit on calls. A server that is slow to answer is cut off after a few seconds on a call and a longer wait in Copilot, and Percy tells the caller or member that the tool did not answer.

In the staff appCopy a link to this section

There is no menu row for it. Open Automation & AI → AI Assistant (on the web or in the app's More tab) and pick MCP Servers under More AI Settings; the link shows for anyone with the permission.