What is MCP?
MCP (Model Context Protocol) is an open protocol that allows AI agents to connect to external tools and services. Think of it as a universal adapter that lets your agent interact with Gmail, Salesforce, Slack, and any other service.How MCP Works
- Agent receives user request - “Send an email to john@example.com”
- Agent decides to use a tool - Determines Gmail tool is needed
- MCP protocol bridges the connection - Standardized communication
- Connector executes the action - Actually sends the email via Gmail API
- Result returns to agent - “Email sent successfully”
Key Concepts
Connectors
Connectors are MCP-compatible servers that provide tools to your agent.Tools
Tools are individual actions your agent can perform through a connector.Tool Calling
When your agent needs to use a tool:- Agent analyzes user request - Understands what action is needed
- Agent selects appropriate tool - Chooses “send_email” from Gmail connector
- Agent prepares parameters - Extracts to, subject, body from context
- MCP executes tool - Connector sends the email
- Agent receives result - Uses response to continue conversation
Two Types of Connectors
1. Pre-built Connectors
BoostGPT provides 30+ ready-to-use connectors:- Managed by BoostGPT - We handle hosting, updates, and maintenance
- OAuth authentication - Secure connection to your accounts
- One-click deployment - Just authenticate and connect
2. External MCP Servers
Connect any MCP-compatible server from the internet:- You provide the URL - Point to any MCP server
- Third-party or self-hosted - Host your own or use community servers
- Custom tools - Access specialized tools not in our library
MCP Protocol Flow
Authentication
OAuth Flow (Pre-built Connectors)
API Key (External Servers)
Security
Pre-built Connectors
- OAuth 2.0 - Industry-standard secure authentication
- Encrypted storage - Tokens encrypted at rest
- Scoped permissions - Only request necessary permissions
- Revokable access - Disconnect anytime from Dashboard
External Servers
- HTTPS required - All MCP servers must use HTTPS
- You control access - Manage authentication yourself
- Audit logs - See all tool executions in agent Insights
Real-World Example
Building a Sales Agent
MCP vs Direct API Integration
| Feature | MCP Protocol | Direct API |
|---|---|---|
| Setup | Deploy connector, add to agent | Write custom code for each API |
| Maintenance | Automatic updates | Manual updates required |
| Authentication | OAuth handled for you | Implement OAuth yourself |
| Agent Access | Automatic tool calling | Manual prompt engineering |
| Multi-service | One pattern for all | Different code per service |
Supported Tool Types
MCP connectors can provide various tool types:Data Access
- Read data (emails, contacts, files)
- Search and filter
- Query databases
Actions
- Send messages
- Create records
- Update information
- Delete items
Scheduled Tasks
- Set reminders
- Schedule events
- Automate workflows
Real-time
- Subscribe to events
- Stream data
- Webhooks
Building Your Own Connector
Want to create a custom MCP connector? See our guide:Debugging Tools
Agent Insights
View all tool executions:Test in Playground
Limitations
Rate Limits
Each service has its own rate limits:- Gmail: 100 emails/day (free), 2,000/day (Google Workspace)
- Salesforce: API limits by license tier
- HubSpot: 100 requests/10 seconds
Permissions
Agents can only use tools you’ve connected:Connector Availability
By plan:| Plan | Connectors |
|---|---|
| Free | 1 connector |
| Starter | 5 connectors |
| Pro | 20 connectors |
| Scale | Unlimited |