An external MCP server can make its published tools available to an authorized Playbooks operator. This is useful when a system already exposes MCP operations or when you need tools beyond a built-in connector.
This page covers tools coming into Playbooks. To use Playbooks from another assistant or coding client, see the Playbooks MCP developer guide.
Choose a server connection
| Mode | Connection | Review |
|---|---|---|
| Managed STDIO | Run a configured server in managed execution | Package or command, dependencies, credentials, and discovered tools |
| Remote HTTP | Connect to a remotely operated MCP endpoint | Server identity, authentication, available tools, and data handling |
Use a server you trust with the data and operations involved. A managed server has isolated scratch space; it does not automatically receive a Project repository, desktop session, or unrestricted platform access.
Managed STDIO execution is gated by deployment and runtime verification. A saved definition or visible setup option does not establish that managed execution is enabled in your environment. Remote HTTP connects to an externally operated server.
Configure and verify
- Open MCPs in the owning configuration surface.
- Add the server definition and complete the supported authentication setup.
- Make it available to the intended eligible consumer.
- Inspect the discovered tools and their requirements.
- Start with a small task whose outcome you can verify.
Discovery tells you which operations the server exposes. It does not by itself authorize every invocation. Current account access, resource permissions, approvals, and funding still apply.
Add a server from the Composer
Type /mcp and choose the available create or add action in the slash command menu. Review the owner and eligible consumer before saving. Use an endpoint or installation definition supplied by the server's trusted maintainer; a server name alone is not enough to establish its behavior.
To identify an available server in a task, select it through the mention picker. Then describe the operation and the inputs. A mention does not authorize the server, assign it permanently, or expose all of your Project files to it.
Example: query a reporting service
Suppose your reporting service exposes an authenticated Remote HTTP MCP server with a supported read operation. Configure the endpoint and authentication, make it available to the intended consumer, and inspect the discovered tools.
Then make a bounded request:
Use the reporting server to retrieve the previous month's totals for the selected account. Include the reporting period, units, and any missing data. Summarize the result without changing the source records.
The server must actually provide the requested operation. Discovery identifies the tool interface; the result still needs review for the intended account, date range, and completeness.
Understand setup and execution
| Stage | Meaning |
|---|---|
| Definition saved | Configuration has been recorded |
| Managed server prepared | Dependencies and a reusable runtime artifact have been prepared |
| Tools discovered | The server returned a tool inventory for the session |
| Tool returned a result | One invocation produced a response; review its contents and any external effect |
For Managed STDIO, saving configuration does not install dependencies or start the server. Not initialized describes an unused configuration. Where managed execution is enabled, first authorized use performs preparation, startup, and discovery. These stages are distinct from the requested tool operation.
A managed server receives explicit inputs and disposable scratch space. It does not receive a mounted Project repository or access to your desktop browser. A tool that expects those resources may need a different integration. Returning a path inside its scratch space does not transfer that file into your Playbooks File system.
Resolve failures at the right stage
| Failure | Next check |
|---|---|
| A response is lost after a write | The external destination before retrying |
| A tool rejects the request | Required inputs, account access, and operation permissions |
| Preparation or startup fails | Reported dependency, launch, or configuration issue |
| Remote endpoint cannot be reached | Endpoint, server availability, and supported authentication |
| Tools cannot be discovered | Server protocol response and initialization requirements |
Use the reported failure and available recovery controls. Preparation success does not prove that every tool is compatible, and a configuration change does not make an uncertain external write safe to repeat.
Maintain access
When a server changes, review changed operations and authentication requirements before relying on it for important work. Reconnect or update credentials through the secure configuration flow. Keep secrets out of Instructions, Skills, and conversation text.
A template can describe portable MCP requirements without transferring the publisher's credentials or live session. Each recipient must authorize their own setup. See Remixing.