> ## Documentation Index
> Fetch the complete documentation index at: https://docs.squawkvoice.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Connectors

> Connect your own MCP server so your AI agents can call its tools during a conversation

An MCP connector links SquawkVoice to an MCP server that you run or use. Once it's connected, you can give an AI agent any of the server's tools, and the agent calls the tool during a conversation, for example to look up an order or create a record in your own system. The connector stores the server's address, how to authenticate and how long a call may take, so you set that up once and reuse it across your agents.

## Getting There

Go to **Manage → MCP Connectors**. It's an **Advanced** page, so it isn't in the starting sidebar. Add it with **Customize sidebar**, or open it from the **Manage** page or with Cmd/Ctrl+K. See [Navigating Studio](https://docs.squawkvoice.ai/navigating-studio.md).

## The Connectors List

Each connector shows its name, a status chip, its transport, the server's host, how many tools it has and when its tools were last found. Search by name with **Search connectors by name**, and select **New Connector** to add one.

The status chip tells you how the last look for tools went:

| Status | Meaning |
| - | - |
| **Connected** | The last look for tools succeeded. |
| **Needs attention** | The last look failed. Open the connector to see which step failed. |
| **Not checked yet** | SquawkVoice hasn't looked for the connector's tools yet. |

## Adding a Connector

Select **New Connector** to open the **New MCP connector** drawer.

| Field | What to enter |
| - | - |
| **Name** | A name that's different from your other connectors. |
| **Description** | Optional. What the server gives your agents access to. |
| **Server URL** | The server's address, for example `https://mcp.example.com/mcp`. Use `https://` where you can. Leave out any username, password, query string or `#` part, and add query parameters in their own section instead. |
| **Transport** | **Streamable HTTP** is the current standard and the default. Choose **SSE (legacy)** only for an older server that still uses server-sent events. |
| **Timeout (seconds)** | How long a tool call may take, from 1 to 25 seconds. |
| **Authentication** | An [Auth Profile](https://docs.squawkvoice.ai/manage/auth-profiles.md) that holds the credentials sent to the server, or **None** if it needs none. |
| **Headers** | Sent with every request. Don't put secrets here: credentials belong in an Auth Profile. |
| **Query parameters** | Added to the server URL on every request. No secrets here either. |

### Test and Save

* **Test connection** checks the details you've entered, saved or not. It reports each step (the Auth Profile, the connection and the list of tools) and shows the server's name and version when it answers. Nothing is saved.
* **Save and find tools** saves a new connector and asks the server for its tools. If the server can't be reached, the connector is still saved and shows **Needs attention**, with the step that failed. Fix the problem, then use **Refresh tools**.
* **Refresh tools** asks a saved connector's server for its tools again, using the saved settings, so save any changes first. Under **Since the last refresh** it lists the tools that are **New**, **Changed** or **Removed**, and which agents use a changed or removed tool, each tagged **Published**, **Draft** or both. Those agents keep the tool as it was when it was added until you review it on each agent.

Saving changes to an existing connector looks for tools again when you've changed the URL, transport, Auth Profile, headers or query parameters. Changing only the name, description or timeout saves without looking.

### The Tools List

A saved connector lists the tools its server offers, each with its description and required arguments. Select **Show input schema** to see the full schema. A tool can carry a badge from the server's own hints: **Read-only**, or **Can change or delete data**. A tool with no hint has no badge.

## Giving an Agent a Tool

Add a tool to an agent from the **Integrations** button on its **In-conversation Actions** card. Each tool you pick becomes its own action with a flow you can edit. See [Add a Tool From an MCP Connector](https://docs.squawkvoice.ai/build/ai-agents/in-conversation-actions.md#add-a-tool-from-an-mcp-connector).

## Changing and Publishing

A connector is shared by your whole account, so what you save on it, such as its URL, timeout or Auth Profile, applies at once to every agent that uses it, including [published agents](https://docs.squawkvoice.ai/build/ai-agents.md#publishing-your-agent), with no **Publish**. Which tool an action uses is part of the agent, so on a published agent, adding a tool or changing the tool an action uses reaches callers at your next **Publish**. See [What Waits for Publish](https://docs.squawkvoice.ai/build/ai-agents.md#what-waits-for-publish).

## When a Tool Is Called

During a conversation the agent calls the tool with the arguments it worked out from the caller. If a call fails, the agent is told it failed and can tell the caller. Keep your tools quick, because a call that runs past the **Timeout** fails.

## Deleting a Connector

Select the **Delete** icon next to a connector. SquawkVoice first checks whether an agent uses it:

* **Not in use**: a **Delete MCP connector?** confirmation appears. Select **Delete Connector** to confirm. The connector and its list of tools are deleted, and this can't be undone.
* **In use**: a dialog lists **AI agents using this connector**, each tagged **Published**, **Draft** or both, and the connector can't be deleted. Remove its tools from those agents first, and publish any agent tagged **Published**, then try again.

A connector that an Auth Profile is chosen on also keeps that profile from being deleted. See [Auth Profiles](https://docs.squawkvoice.ai/manage/auth-profiles.md#delete-a-profile).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.