Skip to main content
Connected MCPs let BoundBot call external tool servers through the Model Context Protocol. This is different from files or FAQs because the bot can use live tools, not just read stored content.

​
Common use cases

MCPs shine when the bot needs live data or external actions instead of static knowledge:
  • Calendar and booking — Check availability and create events (e.g. Calendly-style tools). The bot can say “I have Tuesday at 2 p.m. free” and book it.
  • CRM and lead capture — Look up or create contacts, deals, and activities in your CRM so conversations sync with sales pipelines.
  • Databases and APIs — Query internal APIs, inventory, or config so the bot answers with current data (e.g. “Is item X in stock?”).
  • Notifications and workflows — Trigger alerts, tickets, or downstream workflows (Slack, email, help desk) from the conversation.
Use FAQs, Files, Websites, or Products when the bot only needs reference content; use Connected MCPs when it must call tools or fetch live data.

​
Before you connect an MCP

You need:
  • an MCP server URL
  • the correct transport type
  • an optional API key or bearer token if the server requires one
In the current app, supported transports are:
  • SSE
  • Streamable HTTP

​
Choose the right transport

Use SSE when the provider only exposes server-sent events or you are matching an older MCP deployment that has not moved to the newer HTTP transport.
MCP connections are plan-gated. If your current tier does not support MCP integrations, BoundBot opens the upgrade flow before the connect dialog.

​
Connect a server

1

Open Connected MCPs

Go to Knowledge -> Connected MCPs.
2

Enter connection details

Click Connect MCP, then add a name, optional description, transport, server URL, and optional API key.
3

Test the connection

Use Test Connection before saving. The current app reports whether the server responded, how many tools it found, and the measured latency.
4

Save the MCP

Click Connect to add the MCP to the workspace.
Testing latency: Use Test Connection after every change to URL or transport. If latency is high or unstable, the bot may feel slow when calling tools. Prefer MCP servers that are geographically close to BoundBot or run on low-latency infrastructure.

​
Manage existing MCPs

The MCP list supports:
  • search by name, description, or URL
  • enable or disable with a switch
  • retest an existing connection
  • edit connection details
  • disconnect the MCP
If you disconnect an MCP, the bot loses access to the tools from that server immediately.

​
If the test fails

Recheck the API key or bearer token, then confirm the server expects that credential in the format you entered.
Make sure the selected transport matches the server. A working URL still fails if BoundBot expects SSE and the server only supports Streamable HTTP, or the other way around.
Confirm the URL is public, reachable from the BoundBot environment, and not blocked by IP allowlists, reverse proxies, or expired TLS configuration.

​
MCPs vs knowledge sources

Use Connected MCPs when the bot needs to run tools, fetch live data, or trigger actions in external systems. Use FAQs, Files, Websites, or Products when the bot only needs reference content.

Knowledge base

Compare MCPs with the rest of BoundBot knowledge sources.

Integrations

Review the broader integration surface across the app.

Actions

Combine external tools with automation flows.

Plans and limits

Confirm which plans include MCP integrations.