> For the complete documentation index, see [llms.txt](https://docs.zero.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zero.inc/settings/mcp-connectors.md).

# MCP Connectors

Zero ships with integrations for the tools most teams use. MCP connectors are how you add the rest yourself: connect any third-party tool that offers an MCP server and its tools become available everywhere Zero's AI works — [Chat](/getting-started/chat.md), the **Run AI Agent** step of [Agents](/features/agents.md), and [AI Properties](/features/ai-properties.md). Create an issue in your tracker, look something up in your product database, act in whatever system you run, without waiting for anyone to build an integration for it.

## Add a connector

Workspace admins add connectors in **Settings → Connections → MCP Connectors**.

1. Click **Add MCP Connector**.
2. Give it a **Name** and paste the **MCP Server URL** the tool provides.
3. If the server uses OAuth with its own app credentials, fill in the optional **OAuth Client ID** and **OAuth Client Secret**. Most servers do not need them.
4. Under **OAuth Connection**, click **Connect Integration**. The tool asks you to authorize Zero, then returns you to the settings page.

Zero reads the server's tool list and shows it under **Tools** with a count. The connector reads **Connected** when it is ready, or **Error** when it is not — **Reconnect Integration** fixes expired authorization, and **Sync tools** refreshes the list after the server changes. **Rename** and disconnect live on the same page.

## Private or public

A connector belongs to whoever connected it, and only they can switch it between **Private to you** and **Public in workspace**.

## Where the tools show up

* **Chat** — open the **+** menu in the composer and pick the connector under **MCP Connectors** to enable its tools for that chat.
* **Agents** — in a **Run AI Agent** step, the tools picker has an **MCP Connectors** group where you can allow a connector's tools, individually or all at once.
* **AI Properties** — the **Allow agent to** picker has the same **MCP Connectors** group, so a property can be filled using data from an external tool.

Tools always appear under their connector's name, so you can see which system an action is about to touch.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zero.inc/settings/mcp-connectors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.