Connected Tools (MCP) lets Personyze call the MCP servers you already run — your CRM, your ticketing system, your data warehouse, anything that speaks MCP. Once a server is connected, its tools sit beside Personyze’s own in the panel’s Assistant, so one question can look something up in your CRM and act on it in Personyze.
What it does
The Assistant — the Ask Personyze button in the panel, and its own Assistant page — answers questions about your account with Personyze’s tools: campaigns, actions, reports, audiences and visitors. With a server connected, it can also use that server’s tools in the same answer. For example:
- “Which of last week’s demo bookings are open deals in the CRM?” — it reads the bookings in Personyze, then looks each company up through your CRM’s tools.
- “Do the visitors who opened a support ticket this month still see the upgrade popup?” — your ticketing tool gives the people, Personyze gives the campaign.
While it works, the Assistant lists what it is consulting under Checked, and each answer lists what it used under Based on. A connected tool appears there with its server’s name in front: crm: search.
The two MCP cards
| Card | Who calls whom | Who asks the questions |
|---|---|---|
| Claude & ChatGPT (MCP) | An outside assistant calls Personyze’s MCP server. | You, in Claude, ChatGPT or another assistant. See Personyze MCP server. |
| Connected Tools (MCP) | Personyze calls your MCP servers. | You, in the panel’s Assistant. |
The two do not chain: an outside assistant connected through the MCP server sees Personyze’s tools, not the servers you connected here. Connect those to that assistant directly.
Connecting a server
- Open Integrations in the left menu, then Marketplace, and click the Connected Tools (MCP) card. It is also under Automate & build in What do you want to do?.
- Under Connected servers, click Connect a server.
- Fill in the New server form, then click Save.
| Field | What to enter |
|---|---|
| Name | A short name, such as crm. It labels the server’s tools (crm__search), so two servers can both have a search. Lower-case letters, digits and underscores, starting with a letter. It cannot be changed later. |
| Server URL | The server’s address, starting with https:// — for example https://mcp.example.com/mcp. |
| Auth header | The header the credential goes in. Usually Authorization; some servers want their own, such as X-Api-Key. |
| Credential | The value of that header, for example Bearer abc123. Leave it empty for a server that needs none. |
The server joins the list with its address, and the header with its credential masked. Personyze asks each server for its tools every time the Assistant works on a question, so a tool added on your server is offered from the next question on.
What a server needs
- A public HTTPS address. A server on your own network, or on
http://, cannot be reached. - MCP’s Streamable HTTP transport.
- A credential sent as a request header, if it needs one.
Managing connected servers
- Disable keeps the server in the list, marked disabled, and stops offering its tools. Enable brings them back.
- Edit changes the URL, the header and the credential. The credential box starts empty, because a stored credential cannot be read back: leave it empty to keep the one stored, or type a new one to replace it.
- The bin icon disconnects the server. Its tools stop being available to the Assistant at once.
Limits
| Limit | What it means |
|---|---|
| The panel’s Assistant only | Connected tools are used by the Assistant. Campaigns, the AI Chat on your site and outside assistants do not call them. |
| 128 tools per question | Across all your servers. Tools past that are left out of that question. |
| 30 seconds per call | A tool that takes longer fails for that question, and the Assistant says so. |
| Long results are shortened | A very long answer from a tool is cut down before the Assistant reads it. |
| 12 steps per question | The Assistant’s ordinary limit. Each round of lookups is a step. |
A credential is stored as you enter it, shown masked afterwards, and sent only to the server it belongs to.
When a server does not answer
One failing server does not stop the others: its tools are left out of that question, the rest still work, and the answer carries a line naming the server and the reason — for example MCP server “crm”: authentication failed (401), which means the stored credential is missing, expired or revoked. Click Edit and enter a new one.
The form refuses what could never work, while you are still looking at it:
- Name must start with a letter and contain only lowercase letters, digits and underscores.
- URL must start with https:// — a server reached over http, or only on your own network, cannot be used.
- A server named “crm” already exists.
Related
- Personyze MCP server — the other direction: Claude, ChatGPT and other assistants working in Personyze
- Personyze AI — what the Assistant can do in your account
- Integrations — every integration, and where to find it
- AI in Personyze — every place AI works in the panel