Speko

Name: Speko MCP Server
Availability: InStock
Author: Speko

HIPAA CompliantSOC2 ReadyISO 27001 Ready

Developer Tools59 tools

Operate Speko voice AI from your agent: inspect calls and transcripts, manage phone numbers and knowledge bases, and deploy or roll back live phone agents. 59 tools, OAuth sign-in.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 8 September 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Speko via MCP

https://mcp.speko.ai/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect Speko once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Speko Tools & Capabilities (59)

agents.calls.list

agents.create

agents.delete

agents.deploy

agents.evals.create

agents.evals.list

agents.evals.run

agents.get

agents.list

agents.monitoring.results.list

agents.monitors.create

agents.monitors.delete

agents.monitors.events.list

agents.monitors.list

agents.monitors.update

agents.preview_stacks

agents.rollback

agents.test_call

agents.tools.create

agents.tools.delete

agents.tools.get

agents.tools.list

agents.tools.update

agents.update

agents.versions.list

calls.get

calls.recording.get

credits.balance.get

credits.ledger.list

docs.search

evals.get

knowledge_bases.create

knowledge_bases.delete

knowledge_bases.documents.create

knowledge_bases.documents.delete

knowledge_bases.documents.finalize

knowledge_bases.documents.get

knowledge_bases.documents.list

knowledge_bases.get

knowledge_bases.list

migration.briefing.render

migration.external_config.parse

migration.session_config.build

migration.workspace.inspect

organization.get

phone_numbers.available.search

phone_numbers.create

phone_numbers.delete

phone_numbers.get

phone_numbers.list

phone_numbers.update

sessions.create

sessions.get

sessions.list

sessions.phone.create

sessions.recording.get

sessions.transcript.get

share_cards.create

usage.summary.get

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

No live tool schemas or safety annotations on this page. The endpoint requires authentication and we did not authenticate, so every tool name here comes from Anthropic's directory listing (2026-09-08) and every read/write label is derived from Speko's documentation. We did not read a readOnlyHint or destructiveHint from the server, and you should not assume the server sets them.
The directory listing is a subset, and its description is about a different host. Speko documents 101 tools on mcp.speko.ai; the directory lists 59 of them. The description in the same entry describes the 35-tool anthropic.speko.ai host instead, and names audio.transcribe, which is absent from the 59. Both facts were checked 2026-09-08.
replit.speko.ai is documented but did not resolve. Speko's host table lists it at 28 tools; our probe on 2026-09-08 returned HTTP 404 with a Vercel "deployment could not be found" body. The other three sibling hosts answered with a normal 401 challenge.
Speech generation is not on this connector. audio.synthesize appears in neither the directory list nor Speko's description of the directory host. Speko routes text-to-speech through its REST API and SDKs instead.
No API-key lifecycle tools. Speko states MCP does not expose them; keys are created and revoked in the Platform dashboard.
Credit is an organization-level ceiling. Speko bills post-paid, computes a conservative cost ceiling before admitting work, and refuses with 402 insufficient_credit (Router) or 402 credit_exhausted (control plane) when projected cost exceeds remaining credit. An optional monthly spend limit behaves the same way and resets monthly. An API key carries no spending cap of its own.
Concurrency refuses work at three layers. Per-organization slots, per-edge stream slots and batch-audio staging capacity each return retryable 429 concurrency_exhausted. Transcription jobs add a per-organization ceiling of 64 in-flight jobs and 32 GiB of decoded audio. 429 rate_limited is a distinct signal for request-rate pressure.
Payload caps. JSON request bodies and WebSocket frames are capped at 1 MiB, exceeding which returns 413 payload_too_large. Batch transcription has no universal 25 MiB cap — the bound is per provider and per model.
Outbound calling is gated on a business declaration. Before any outbound call, Speko requires the workspace to file a business name, a statement of what calling is for, and an attestation. Speko also injects AI disclosure server-side on every call created from a directory host: the first thing said on the line is that the caller is an AI, and no prompt can override it. Speko documents this for the directory hosts specifically; we did not verify how it applies to mcp.speko.ai.
A deploy is not reversible by undoing a message. agents.rollback restores a previous version, but calls that landed on the wrong version in between already happened.
Deleting is not reversible at all. Six *.delete tools, no inverse for any of them. Deleting an agent also removes its registered tools.
Evals cost real capacity. agents.evals.run queues a worker that places a simulated call.

Frequently asked questions

No. Anthropic's directory description says read access, but the same entry lists agents.create, agents.deploy, agents.rollback, agents.delete and phone_numbers.delete among its 59 tool names. Speko's own docs confirm the endpoint in that entry carries the full operational surface, including writes. Treat this connector as read-write.

It publishes a new agent version that a live phone agent starts using. Speko's workflow docs state that publishing cuts a new agent version and that this is how rollback reaches a previous workflow. A deployed agent then answers inbound calls with no further tool call.

Either works. Speko's MCP quickstart documents OAuth browser sign-in through its guided installer as the default, and a Speko Platform API key sent as a bearer token for automation. Our anonymous handshake returned a 401 bearer challenge naming both read and write scopes.

Each hostname serves a different tool surface, and Speko states the surface is a property of the host — no query parameter, header or account setting widens it. Its docs list mcp.speko.ai at 101 tools, anthropic.speko.ai at 35, chatgpt.speko.ai at 20 and builder-mcp.speko.ai at 12.

Credit and concurrency limits apply per organization, not per key. Speko documents 402 insufficient_credit when projected cost exceeds remaining credit, an optional monthly spend limit, and 429 concurrency_exhausted when organization or edge slots run out. Transcription jobs add a ceiling of 64 in-flight jobs and 32 GiB of audio.