API Request vs MCP
Chatevo supports two tool types: API Request (REST) and MCP (Model Context Protocol). Both let your assistant call external systems with stored credentials — choose based on how your backend is already exposed.
Comparison
Section titled “Comparison”| API Request | MCP | |
|---|---|---|
| Best for | REST APIs you control (orders, bookings, CRM) | Existing MCP servers with discoverable tools |
| Configuration | You define URL, method, params, body schema | Chatevo connects to your MCP server URL |
| Transport | HTTP to your API | streamable-http or sse |
| Tool discovery | One tool per API Request definition | Server exposes multiple tools automatically |
| Credentials | Bearer, API key, OAuth 2.0, HMAC | Server-specific (often Bearer on MCP endpoint) |
| Rich content | result_transform on JSON response | Depends on tool output; transforms apply when JSON matches |
When to use API Request
Section titled “When to use API Request”- You have a REST API with documented endpoints.
- You want full control over URL, headers, path/query/body parameters.
- You need to map responses to product or media cards via result_transform.
Start with Create an API Request tool.
When to use MCP
Section titled “When to use MCP”- You already run an MCP-compatible server (internal platform, vendor SDK, or custom gateway).
- You prefer the server to register tool names, descriptions, and parameter schemas.
- You want multiple related tools without creating each REST definition manually.
Start with Create an MCP tool and MCP transport.
Shared behavior
Section titled “Shared behavior”Both tool types support:
- Strict parameters — reject malformed calls before hitting your backend
- Execution mode — sync vs async
- Status notifications — progress text in chat
- Credentials — encrypted, never shown to visitors
- Testing and execution logs