What the Telofy MCP server does
The Telofy MCP server gives compatible AI assistants read access to data held in a Telofy account. Telofy is an AI phone receptionist for small businesses in Germany; its underlying service answers calls, handles conversations, books appointments, takes orders, and records completed interactions in its customer portal. The MCP connection focuses on retrieving that recorded account data rather than controlling the phone service.
The available data covers three areas: calls, outcomes, and appointments. Calls include details such as time, phone number, duration, status, and result. Outcomes represent recorded business processes, including leads, tickets, appointments, and requests for information. Appointment queries return appointments booked or provisionally held by Telofy.
How it works
The Telofy MCP server is hosted remotely at https://api.telofy.app/mcp and uses Streamable HTTP. There is no local package or process to install. An MCP client sends requests to the endpoint with a Telofy API key in the HTTP Authorization header using the Bearer scheme.
The server is read-only. Requests are scoped to the account associated with the supplied key, so the tools retrieve that account’s records rather than providing a general Telofy search across customers. Each tool supports optional pagination through page and limit. Page numbering starts at 1, limits range from 1 to 100, and the default limit is 50. Calls are returned newest first.
Setup and configuration
Create an API key in the Telofy customer portal under Integrations. Telofy keys begin with tlfy_. Add the remote endpoint and the key to the MCP client configuration.
For Claude Code, the setup uses an HTTP transport command:
claude mcp add --transport http telofy https://api.telofy.app/mcp --header "Authorization: Bearer tlfy_IhrSchluessel"
Claude Desktop, Cursor, and clients using an mcpServers configuration can use an entry like this:
{
"mcpServers": {
"telofy": {
"url": "https://api.telofy.app/mcp",
"headers": { "Authorization": "Bearer tlfy_IhrSchluessel" }
}
}
}
Replace the example key with the key created in the Telofy portal. The documented allowance is up to 60 requests per minute per key.
Tools and capabilities
The Telofy MCP server provides these tools:
list_calls: Retrieves account calls, including timing, number, duration, status, and result information.
list_outcomes: Retrieves recorded outcomes such as leads, tickets, appointments, and information requests.
list_appointments: Retrieves appointments booked or provisionally scheduled by Telofy.
All three tools accept the optional page and limit parameters. This makes it possible to request a bounded result set when an account contains more records than one response should return.
Limitations and notes
This connection only reads data; it does not create, edit, cancel, or otherwise mutate calls, outcomes, or appointments. It also only exposes the account associated with the supplied API key.
The service processes data in the EU, and the README states that it does not include audio recordings. Invalid or revoked keys return an error rather than account data. The MCP server itself does not provide Telofy’s broader integrations or phone-reception features; those belong to the Telofy service. Its role is to let supported AI clients query selected records from the Telofy account.