MCP Connectors
Add workspace MCP Connectors so Playbooks can use external systems and custom tools
Last updated
Was this helpful?
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.
Add the Connector in your workspace MCP Connectors settings.
Open the Playbook editor.
Open the Tools panel or type / in a Section.
Turn on or select the connected MCP tool.
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 for setup and connector details.
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.
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.
Last updated
Was this helpful?
Was this helpful?
Use the connected CMS Tool to find the article for `target_url`, update the draft body, and preserve the existing metadata.