MCP MCP server
What it can do
Everything the assistant can manage in Space, what it deliberately cannot do, and how it differs from chatting in the app.
For developers and power users
Coverage
Every action in Space is either a tool here, or listed under Not tools, on purpose below.
| Tool family | What it covers |
|---|---|
*_skill, *_http_tool, *_mcp_server, *_function | Skills, API tools, MCP servers and Functions |
*_knowledge_base, knowledge_bases_*, files_* | Knowledge bases and the Library |
*_table, tables_* | Tables: rows, columns, permissions |
*_playbook, playbooks_* | Playbooks: validation, test runs, real runs |
*_automation, automations_* | Schedules and triggers |
*_page, pages_* | Pages, their actions, workflow inputs and uploads |
portability_* | Export and import |
*_agent, agents_*, *_channel | Agents, tasks, links and channels |
integrations_* | Connections, policies, plugins |
chat_*, *_review, reviews_decide, notifications_* | Conversations, approvals, reviews, notifications |
sharing_*, tool_policy_* | Sharing and access policy |
*_user, users_*, *_group, groups_*, org_*, auth_* | People, groups, organization settings, your own account |
usage_*, logs_*, system_*, control_room_* | Usage, quotas, audit, traces, health, live activity |
The assistant also gets a get_authoring_guide tool: step-by-step instructions for building each kind of resource, kept in step with what the copilot itself follows. Guides are also offered as resources (botcircuits://guides/<topic>), and there are three ready-made prompts: build a resource, set up an agent and troubleshoot.
Not tools, on purpose
For safety, these are only available in the web app:
- Anything that takes or returns a secret: setting credentials, passwords, AI keys and webhook secrets. An assistant's AI would see them, so the assistant sends you to the web app instead.
- Sign-in routes (the server handles its own sign-in) and browser redirects.
- Routes other systems call with their own signature, such as incoming webhooks.
- The live activity stream (a snapshot tool gives the same data).
- WebSocket channels, which are for your own applications.
- Creating an external page link, and answering secure workflow questions. Do those on the page itself.
Chat from your assistant
The assistant can send messages to the copilot and read its replies. Unlike the app, replies arrive whole rather than word by word, and include the text, the status and any pending approvals, but not the per-tool detail.
Some abilities exist only inside the copilot's own chat, such as starting a multi-agent workflow. The assistant reaches those by chatting with the copilot.
Pages, Functions and portable setups
For building something larger, such as a page that runs a workflow:
- Create the Functions first, and attach any libraries they need as a ZIP.
- Create the playbook.
- Create the page with its workflow action.
Opening a page never starts a workflow, and schedules run unattended, so they need all their inputs. Secure answers must be typed on the page, never through the assistant.
Export and import use a TAR file you save and open locally. It contains setup definitions and Function bundles, not documents or credentials.
How it differs from chatting in the app
| In the app's chat | Through MCP |
|---|---|
| Playbooks are described as a list of steps | They're a workflow of states, each naming its next step |
| Saving a playbook test-runs it automatically | Call the simulate tool yourself |
@ada finds an agent by name | Use the agent's id |
Automations take task, trigger, tools | They take instruction, trigger_type, pre_approved_tools |
| “Reply to the sender” is on by default | It's off by default |
| Discussion and hand-over steps in playbooks | Use one run agent state per turn, or ask the copilot |
| Every change asks you to confirm | Your assistant's permission prompt is the only confirmation |
Size of the tool list
There are many tools, so the list can use some of your assistant's working memory. Assistants that load tools on demand, such as Claude Code, handle this well. If yours doesn't, you'll notice it as space used before you've typed anything.
Keeping it up to date
When Space is updated with new abilities, the MCP server's description of them is refreshed by the people who maintain it. If a tool seems missing, the snapshot may be older than Space. Ask the maintainers to refresh it.