Create an MCP tool
An MCP tool connects Chatevo to a Model Context Protocol server. Instead of defining each HTTP endpoint manually, your MCP server exposes tool names, descriptions, and parameter schemas for Chatevo to discover.
Prerequisites
Section titled “Prerequisites”- MCP server reachable from Chatevo (public HTTPS or allowed network path)
- Supported transport (
streamable-httporsse) - Auth on the MCP endpoint if required (often Bearer — store in Credentials)
- Go to Tools → Create → MCP.
- Name — identifier for this connection (e.g.
internal_ops_mcp). - Server URL — MCP endpoint URL.
- Transport —
streamable-httporsse(must match your server). - Attach a credential if the server requires authentication.
- Optional: execution mode, strict params, status notifications.
- Save — Chatevo discovers tools from the server.
- Test individual discovered tools with sample inputs.
MCP vs API Request
Section titled “MCP vs API Request”| MCP | API Request | |
|---|---|---|
| Tool definitions | Server provides many tools | You define one HTTP call per tool |
| Best when | You already run MCP | You have REST endpoints |
See API Request vs MCP.
Attach to assistant
Section titled “Attach to assistant”- Open assistant → Tools.
- Enable MCP connection and select which discovered tools the assistant may call.
- Save and test in assistant preview.
Rich content
Section titled “Rich content”If an MCP tool returns JSON suitable for cards, add result_transform on the tool definition — same rules as API Request tools. Cards render only per the trust policy.