MCP Servers Overview
MCP (Model Context Protocol) servers extend your chatbot's capabilities by connecting to external tools and services.
What is MCP?
MCP is a standard protocol that allows AI models to:
- Access external data sources
- Execute actions in other systems
- Retrieve real-time information
- Perform calculations and operations
How It Works
- User asks a question
- Chatbot determines if external data is needed
- If yes, calls the appropriate MCP server
- Server retrieves/processes data
- Response is generated with the data
Available Integrations
Built-in Servers
Pre-configured integrations ready to use:
| Server | Description |
|---|---|
| Calculator | Mathematical operations |
| Weather | Current weather data |
| Salesforce | CRM data access |
| Atlassian | Jira/Confluence access |
| PostgreSQL | Database queries |
See Built-in Servers for details.
Custom Servers
Add your own MCP servers:
- HTTP-based servers
- stdio-based servers
- Custom implementations
See Custom Servers for details.
Enabling MCP Servers
- Open your chatbot
- Go to "Settings" > "Integrations"
- Find the MCP server
- Toggle "Enable"
- Configure any required settings
- Click "Save"
Editing MCP Servers
You can update the configuration of any MCP server after it's been added:
- Open your chatbot
- Go to the "MCP" tab
- Click the edit icon next to the server you want to change
- Update connection details, name, or other settings
- Click "Save"
This lets you update credentials, change endpoints, or adjust settings without removing and re-adding the server.
Authentication
Some MCP servers require authentication:
| Type | Description |
|---|---|
| OAuth | User authorizes access |
| API Key | Single key for all users |
| Centralized | Admin credentials for all |
See OAuth Configuration for details.
Restricting a server to specific embedding sites
If the same chatbot is embedded on more than one website, you can restrict an individual MCP server to only the sites you trust. Pin the server to a list of allowed embedding domains and it is exposed only when the chatbot is embedded on one of those hosts — on any other page, the server and its tools are hidden.
- Open by default. A server with no allowed-domains list stays available everywhere, so existing servers are unaffected.
- Fail-closed when set. Once a list is configured, a request from an unknown or unverified host never matches, so the server is withheld rather than exposed by accident.
This lets a chatbot expose sensitive tools — for example a management copilot's
actions — only on your trusted internal pages, while hiding them on a public site
such as your documentation. Domain matching supports wildcards (for example
*.example.com), matched against the host page's verified domain.
Use Cases
Customer Support
Connect to:
- CRM (Salesforce) for customer data
- Ticketing system for issue history
- Knowledge bases
Internal Tools
Connect to:
- Databases for live data
- Project management (Jira, Confluence)
- Internal APIs
Data Analysis
Connect to:
- PostgreSQL for database queries
- Calculator for computations
- External APIs for data
Best Practices
- Only enable servers you need
- Configure appropriate access controls
- Test thoroughly before deploying
- Monitor usage and performance
Security Considerations
- MCP servers can access external systems
- Review permissions carefully
- Use least-privilege access
- Audit integrations regularly