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

# MCP Connectors

Add workspace MCP Connectors so Playbooks can use external systems and custom tools

MCP Connectors extend the Playbook tool list with systems configured in your workspace. Use them when a Playbook needs to read context from or take action in tools such as Notion, GitHub, Asana, your CMS, or another MCP-compatible service.

MCP Connectors can appear inside the same category groups as built-in Tools when AirOps recognizes the connector category. If a connector does not have a category, it appears with the other workspace connectors.

## How to Configure

1. Add the Connector in your workspace MCP Connectors settings.
2. Open the Playbook editor.
3. Open the **Tools** panel or type `/` in a Section.
4. Turn on or select the connected MCP tool.
5. Describe when the Playbook should use the connector and what action it should take.

Connected MCP tools appear in the Playbook editor's Tools list alongside the built-in catalog. See [MCP](/developers/getting-started.md) for setup and connector details.

{% hint style="info" %}
Use the native **Slack** Tool when a Playbook needs to read channel history or send messages. You can still add Slack through an MCP Connector if your workspace uses a custom connector setup.
{% endhint %}

## Parameters

MCP Connector parameters depend on the connector and the tools it exposes. Check the connector's schema in the Playbook editor, then name the exact resource, action, filters, and output format the Playbook should use.

When you add MCP Connector instructions, include:

* The connected system the Playbook should use.
* The record, page, issue, project, CMS entry, or file to read or update.
* The action the Playbook should take and any approval rules before writing changes.

## Examples

```markdown
Use the connected CMS Tool to find the article for `target_url`, update the draft body, and preserve the existing metadata.
```


---

# 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.airops.com/actions/playbooks/tools/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.