Academy · Developer
MCP integration
In one line. The Model Context Protocol connects Botminds to the wider agent ecosystem in both directions: your agents can consume external MCP servers, and the platform hosts its own MCP tool surface so AI assistants can operate Botminds. You’ll be able to. Pick the right direction for your integration, and know what governs each.
Two directions, one protocol
MCP is the open standard for giving AI tools capabilities. On this platform it runs both ways:
| Direction | What it means | Governed by |
|---|---|---|
| Inbound capabilities — your agents consume external MCP servers | An agent gains tools from any MCP server you register: an internal system, a SaaS product, a partner API | The agent’s Capabilities tab; scope filters per server (A7) |
| Outbound operation — external AI tools drive Botminds | The platform hosts an MCP server exposing curated platform operations — list collections, inspect runs, query documents — so an assistant like Claude can work with your workspace | Tool profiles + platform authentication; every call carries workspace scope |
Consuming MCP servers (the common case)
Covered in depth in A7 · MCP servers: register the server in Studio, filter which of its tools are exposed, attach it to an agent. Two disciplines carry from there:
- Scope tightly. An empty tool filter exposes everything the server offers; curate the list to the job.
- Prefer read-only servers for agents that face users, and treat destructive tools with the same caution you’d give a production credential.
The hosted Botminds MCP
The platform mounts its own MCP server (under /mcp on the orchestrator) whose tools are the platform’s operations, organized into profiles — curated tool subsets shaped for a purpose rather than one giant surface. Calls authenticate with platform-service credentials and are scoped to a workspace; the tools respect the same RBAC as the UI.
This is the surface the Global Co-pilot itself runs on — when it answers “how many documents landed today,” it is calling these same tools. Pointing an external assistant at it gives that assistant the same governed reach.
The hosted MCP surface and its profiles are evolving faster than most of the platform. Treat the profile catalog you see in your environment as the source of truth for what’s exposed.
Choosing your integration style
| You want | Use |
|---|---|
| Deterministic system-to-system calls, contracts, SLAs | Runtime API — REST, keys, stable paths |
| An AI assistant that operates the platform conversationally | The hosted MCP surface |
| Your Botminds agents reaching into other systems | Inbound MCP (A7) or custom tools |
The rule of thumb: machines integrate over REST; minds integrate over MCP.
Where to go next
- Registering and scoping servers: A7 · MCP servers.
- The REST alternative: V1 · Runtime API.
- What governs any caller: G1 · Access & roles.
Prefer learning inside the product? The same academy lives in the platform's Learn menu — every screen links to the chapter that explains it.
See the platform live