What is MCP?
MCP (Model Context Protocol) is an open standard that defines how AI models connect to external tools and data sources. NimbleBrain uses MCP to provide a consistent, secure way to integrate with any service.This is technical documentation for developers. If you’re building automations in Studio, you don’t need to understand MCP - just use Connections to add integrations.
Why MCP Matters
MCP provides several advantages for AI-powered integrations:Standardized
One protocol for all integrations. Any MCP-compatible server works with NimbleBrain.
Secure
Credentials are managed separately from the AI model. Tools declare their capabilities upfront.
Extensible
New tools can be added without changing how playbooks work. The AI automatically discovers available tools.
Interoperable
MCP servers work with Claude Desktop, NimbleBrain Studio, and other MCP-compatible clients.
Architecture
MCP Server Components
Each MCP server (what Studio calls a “Connection”) provides:Tools
Functions the AI can call. For example, the Slack server provides:slack_send_message- Post a message to a channelslack_list_channels- Get available channelsslack_get_history- Retrieve message history
Resources
Data the AI can access, like files or database schemas.Prompts
Pre-configured prompt templates for common tasks.Using MCP in Development
NimbleBrain SDK
The TypeScript SDK handles MCP communication automatically:Claude Desktop Integration
Connect Claude Desktop to NimbleBrain MCP servers:- Go to Connections in Studio
- Click Connect on any installed connection
- Copy the configuration JSON
- Add to your
claude_desktop_config.json:
Building Custom MCP Servers
To build your own MCP server for NimbleBrain:- Follow the MCP Specification
- Implement the required transport (SSE for NimbleBrain)
- Publish to the NimbleBrain registry or deploy privately
MCP vs REST APIs
| Feature | MCP | REST API |
|---|---|---|
| AI Discovery | Tools auto-discovered | Manual documentation |
| Type Safety | Schema-defined | Varies |
| Authentication | Standardized | Varies by API |
| Real-time | SSE support built-in | Requires WebSocket |