Model Context Protocol (MCP) Servers Guide (Coming Soon)
Model Context Protocol (MCP) servers extend your chatbot’s capabilities by connecting it to external services and data sources. This guide explains how to set up and use MCP servers in your chatbot.
Understanding MCP Servers
MCP servers act as bridges between your chatbot and external services, allowing it to:
- Access and manipulate data from various sources
- Integrate with third-party services
- Enhance the chatbot’s functionality with real-time data
Server Types
SSE (Server-Sent Events) Servers
- Most MCP servers use SSE for real-time communication
- Require an endpoint URL from mcp.composio.dev
- Support various services like Google Sheets, Airtable, Trello, etc.
Command-based Local Servers
Run an MCP SSE proxy to turn your local MCP server into a remote one. This example repo shows you how to run an MCP proxy to turn a local MCP server into a remote / SSE MCP server. If you follow this route, you will need to make sure you expose to appropriate ports via ngrok or similar tools.
Setting Up MCP Servers
Getting Started
- Navigate to your chatbot’s MCP Servers page
- Browse available server templates
- Click “Install” on your desired server
Configuration Steps
-
Get the SSE Endpoint:
- Visit mcp.composio.dev
- Select your desired service
- Choose “Cursor” as your platform
- Copy the generated SSE endpoint URL (Only need to copy the URL, not the whole command)
-
Using a custom local server:
Run an MCP SSE proxy to turn your local MCP server into a remote one. This example repo shows you how to run an MCP proxy to turn a local MCP server into a remote / SSE MCP server. If you follow this route, you will need to make sure you expose to appropriate ports via ngrok or similar tools.
-
Install the Server:
- Paste the SSE endpoint URL in the installation dialog
- Configure server settings:
- Active: Enable/disable the server
Authentication
For services requiring authentication (e.g., Google Sheets, Google Calendar):
- Click “Install” on the service
- Enter the SSE endpoint URL
- The authentication will be automatically associated with the URL
- Simply chat with the chatbot to authenticate, for example (“authenticate with google sheets”)
- Visit the URL provided by the chatbot to complete the authentication process
MCP servers are not available for public use due to obvious security reasons. The chatbot can access these servers only upon successful authentication with the okchat dashboard.
Use claude 3.5 sonnet model for best results. Other models may not work as expected.
Important Concepts
Active Servers Limit
- Maximum of 3 active MCP servers per chatbot
- This limit ensures optimal performance
- You can install more servers but only 3 can be active at once
- Toggle servers active/inactive as needed
Public vs Private Servers
- Public Servers: Available for use by other chatbots
- Private Servers: Only accessible by your chatbot
- Consider making servers public if you want to share functionality
Best Practices
-
Server Management:
- Keep only necessary servers active
- Regularly review and update server configurations
- Test server connections after setup
-
Security:
- Use authenticated endpoints for sensitive data
- Keep authentication credentials secure
- Review public/private settings regularly
-
Performance:
- Monitor server response times
- Deactivate unused servers
- Use appropriate rate limits
Available MCP Servers
Google Sheets
- Store and retrieve data from spreadsheets
- Real-time updates and modifications
- Requires Google authentication
Airtable
- Connect to Airtable bases
- Access and modify records
- Real-time database operations
Trello
- Manage boards and cards
- Track tasks and projects
- Real-time updates
Google Calendar
- Manage events and schedules
- Set reminders
- Check availability
And More
- Additional servers are regularly added
- Check the templates page for the latest options
Troubleshooting
Common Issues
-
Connection Problems:
- Verify the SSE endpoint URL
- Check server status at mcp.composio.dev
- Ensure authentication is valid
-
Authentication Errors:
- Re-authenticate the service
- Check permission settings
- Verify API access
-
Performance Issues:
- Review active server count
- Check server logs
- Monitor rate limits