MCP Integration
Bootspring uses the Model Context Protocol (MCP) to communicate with AI assistants. This open standard enables secure, standardized tool access across different AI platforms.
What is MCP?#
The Model Context Protocol (MCP) is an open protocol developed by Anthropic that enables AI assistants to securely access external tools and data sources.
┌─────────────────────────────────────────────────────────────────────────┐
│ MCP Architecture │
├─────────────────────────────────────────────────────────────────────────┤
│ │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ AI │ MCP │ MCP │ Tools │ Bootspring │ │
│ │ Assistant │◄──────►│ Server │◄──────►│ Features │ │
│ │ (Claude) │Protocol │ (Bootspring)│ │ │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
│ │
│ The AI assistant uses MCP to access Bootspring tools without │
│ direct integration - the protocol handles all communication. │
│ │
└─────────────────────────────────────────────────────────────────────────┘
Why MCP?#
| Benefit | Description |
|---|---|
| Standardized | Works with any MCP-compatible AI assistant |
| Secure | Controlled capability exposure |
| Extensible | Easy to add new tools |
| Portable | Works across platforms (Claude, Cursor, etc.) |
Bootspring MCP Server#
Bootspring runs as an MCP server, exposing 19 tools for AI assistants:
Core Tools#
| Tool | Purpose |
|---|---|
bootspring_assist | General development assistance |
bootspring_context | Project context access |
bootspring_agent | Specialized agent invocation |
bootspring_skill | Code pattern generation |
bootspring_quality | Quality gate execution |
Generation Tools#
| Tool | Purpose |
|---|---|
bootspring_generate | Context file generation |
bootspring_seed | Project seeding/scaffolding |
bootspring_prd | PRD document generation |
bootspring_mvp | MVP planning |
bootspring_content | Content generation |
Workflow Tools#
| Tool | Purpose |
|---|---|
bootspring_orchestrator | Workflow management |
bootspring_loop | Autonomous execution |
bootspring_todo | Task tracking |
bootspring_dashboard | Dashboard integration |
Configuration Tools#
| Tool | Purpose |
|---|---|
bootspring_plugin | Plugin management |
bootspring_capabilities | Feature discovery |
bootspring_telemetry | Usage analytics |
bootspring_memory | Persistent memory |
bootspring_autopilot | Autopilot mode |
Setting Up MCP#
Configuration File#
Create .mcp.json in your project root:
Environment Variables#
Set your API key:
Verifying Connection#
Test the MCP connection:
Expected output:
✓ MCP server running
✓ 19 tools registered
✓ Authentication valid
✓ Ready for connections
How Tools Work#
Tool Invocation Flow#
┌─────────────────────────────────────────────────────────────────────────┐
│ Tool Invocation Flow │
├─────────────────────────────────────────────────────────────────────────┤
│ │
│ 1. User Request │
│ "Help me add authentication" │
│ │ │
│ ▼ │
│ 2. AI Determines Tool │
│ → bootspring_agent with auth-expert │
│ │ │
│ ▼ │
│ 3. MCP Protocol │
│ AI ──► MCP Server ──► Bootspring │
│ │ │
│ ▼ │
│ 4. Tool Execution │
│ Bootspring processes request │
│ │ │
│ ▼ │
│ 5. Response │
│ Bootspring ──► MCP Server ──► AI ──► User │
│ │
└─────────────────────────────────────────────────────────────────────────┘
Tool Schema#
Each tool has a defined schema:
Tool Responses#
Tools return structured responses:
Compatible Platforms#
Claude Desktop#
Native MCP support:
Claude Code (CLI)#
Automatic detection via .mcp.json:
Cursor IDE#
Configure in settings:
VS Code (Copilot Chat)#
Coming soon with MCP support in Copilot.
Security Model#
Capability Exposure#
Bootspring only exposes safe operations:
┌─────────────────────────────────────────────────────────────────────────┐
│ Security Model │
├─────────────────────────────────────────────────────────────────────────┤
│ │
│ Exposed (Safe) │ Not Exposed (Protected) │
│ ───────────────────── │ ──────────────────────── │
│ • Read project context │ • Direct file system access │
│ • Generate code │ • Shell command execution │
│ • Run quality checks │ • Network requests │
│ • Access documentation │ • Environment variables │
│ • Invoke agents │ • Sensitive credentials │
│ │ │
└─────────────────────────────────────────────────────────────────────────┘
API Key Scoping#
API keys have scoped permissions:
| Key Type | Permissions |
|---|---|
| Development | Full access in local environment |
| CI/CD | Quality checks only |
| Read-only | Context and documentation |
Request Validation#
All tool requests are validated:
- Schema validation: Input matches expected format
- Permission check: API key has required access
- Rate limiting: Prevents abuse
- Audit logging: All requests logged
Advanced Configuration#
Custom Tool Parameters#
Override default tool behavior:
Tool Filtering#
Enable/disable specific tools:
Custom Server Port#
Run on a specific port:
Debugging#
Enable Debug Logging#
View Tool Calls#
Output:
[MCP] Tool call: bootspring_agent
[MCP] Input: { agent: "frontend-expert", task: "..." }
[MCP] Duration: 1234ms
[MCP] Output: { success: true, data: {...} }
Test Individual Tools#
Troubleshooting#
Connection Issues#
Symptom: AI assistant can't connect to Bootspring
Solutions:
- Verify
.mcp.jsonexists and is valid JSON - Check
BOOTSPRING_API_KEYis set - Run
bootspring mcp --test - Restart the AI assistant
Tool Not Found#
Symptom: "Tool bootspring_xyz not found"
Solutions:
- Check tool name spelling
- Verify tool is enabled in config
- Check tier access (some tools require Pro/Team)
Slow Responses#
Symptom: Tools take a long time to respond
Solutions:
- Check network connectivity
- Reduce context size
- Use more specific queries
- Check server status at status.bootspring.com
Authentication Errors#
Symptom: "Invalid API key" errors
Solutions:
- Verify API key is correct
- Check key hasn't expired
- Ensure key has required permissions
- Regenerate key in dashboard
Protocol Details#
Message Format#
MCP uses JSON-RPC 2.0:
Transport#
Bootspring MCP supports:
- stdio: Default for local development
- HTTP: For remote/CI environments
Related#
- MCP Tools Reference - Full tool documentation
- Configuration - Setup guide
- Troubleshooting - Common issues
- MCP Specification - Protocol details