MCP (Model Context Protocol) servers extend your chatbot with standardized AI capabilities. Unlike custom tools that connect to your APIs, MCP servers provide pre-built tools following an open protocol.Documentation Index
Fetch the complete documentation index at: https://docs.bubblav.com/llms.txt
Use this file to discover all available pages before exploring further.
What is MCP?
Model Context Protocol is an open standard for connecting AI systems to external tools and data sources. MCP servers expose:- Tools: Actions the AI can perform
- Resources: Data the AI can access
- Prompts: Pre-defined conversation templates
MCP is an advanced feature. Most users should start with Integrations Overview or Custom Tools.
When to Use MCP vs Custom Tools
| Feature | Custom Tools | MCP Servers |
|---|---|---|
| Setup complexity | Simple | Advanced |
| Protocol | HTTP/REST | MCP (SSE over HTTP) |
| Best for | Your own APIs | Pre-built AI tools |
| Authentication | Built-in options | Server-specific |
- Connecting to your own backend
- Simple API integrations
- Need built-in auth options
- Using pre-built MCP servers
- Need advanced AI capabilities
- Building with MCP ecosystem
Adding an MCP Server
Configure Server
Fill in the server configuration:Server Name (required)
- A friendly name for this server
- Example: “File Browser”, “Database Query”
- The MCP server endpoint URL using Server-Sent Events (SSE)
- Example:
https://mcp.example.com/sse - Must be accessible over HTTPS
Add Authentication Headers (optional)
If your MCP server requires authentication, add custom headers:
- Header Key: e.g.,
Authorization,X-API-Key - Header Value: Your authentication token or key
Authorization: Bearer your-token-hereX-API-Key: your-api-key
Configuration Examples
Remote MCP Server
Connect to a remote MCP server with authentication:| Field | Value |
|---|---|
| Name | Custom Server |
| URL | https://mcp.example.com/sse |
| Headers | Authorization: Bearer your-token-here |
Public MCP Server
Connect to a public MCP server without authentication:| Field | Value |
|---|---|
| Name | Public Tools Server |
| URL | https://public-mcp-server.com/sse |
| Headers | (none required) |
Available Tools
After connecting, the server’s tools appear in your dashboard. Common tool types:- File operations: Read, write, list files
- Database queries: SQL or natural language queries
- Web scraping: Fetch and parse web content
- API integrations: Pre-built API connectors
- Name and description
- Required parameters
- Return type
Managing MCP Servers
View Connected Servers
Go to Dashboard → Integrations → MCP Servers to see:- Connection status
- Available tools
- Last activity
Disconnect
- Find the server card
- Click the settings icon
- Select Disconnect
Reconnect
If a server disconnects:- Check the server is running
- Verify configuration
- Click Reconnect
Troubleshooting
Server won't connect
Server won't connect
- Verify the server URL is correct and accessible
- Check that the server supports SSE (Server-Sent Events) transport
- Review authentication headers if required
- Ensure the server is running and reachable over HTTPS
Tools not appearing
Tools not appearing
- Wait for server initialization
- Check server logs for errors
- Verify server exposes tools correctly
Connection drops
Connection drops
- Check network stability and HTTPS connectivity
- Verify the server URL is still valid
- Review server health and availability
- Check authentication headers haven’t expired
Security Considerations
- Verify sources: Only use official or audited MCP servers
- Limit access: Configure minimal permissions
- Monitor activity: Review tool usage in logs
- Authentication headers: Store sensitive tokens securely and never expose them in logs
- HTTPS only: Always use HTTPS URLs to protect data in transit
Next Steps
Custom Tools
Build simple API integrations
Integrations Overview
Connect popular platforms