Speko AI

ai.spekoPublished by speko.aiOfficial publisherv1.0.12Updated Oct 24, 2026

Manage Speko voice-AI agents, sessions, calls, phone numbers, knowledge bases, evals, and docs.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryCommunication & CollaborationAI & ML

Overview

AI-generated overview

Remote MCP endpoint for Speko's voice-AI platform, letting an assistant inspect agents, calls, transcripts, phone numbers, knowledge bases and docs.

What you can do
  • Read account details, credit balance, ledger and usage summaries
  • List, inspect and preview voice agents, their versions, tools and monitoring results
  • Review sessions and calls, including transcripts and recordings, and transcribe audio
  • Look up phone numbers, search available numbers and read compliance diagnostics
  • Browse knowledge bases and their documents, evals and documentation search
  • On some hosts, place a single outbound call or end a session
When to use it
Useful when you work with Speko voice agents and want an assistant to review call transcripts, check usage and credits, look up phone numbers or search Speko documentation without leaving the chat. The available tools depend on which host you connect to.
Requirements
A remote MCP endpoint over streamable HTTP; no local package needed. Authentication is required: OAuth through the client, or a Speko Platform API key sent as an Authorization bearer token. The tool set is fixed per hostname, so pick the host matching your client.
Before you install
The endpoint can place outbound phone calls and end live sessions, which may incur charges; calls on directory hosts inject an AI disclosure. Some hosts also allow agent configuration, knowledge-base writes and irreversible deletes. API keys are forwarded to the Speko platform API, and call recordings and transcripts are exposed to the assistant.

Installation

In SourceWeft

  1. Open Speko AI in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.speko%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "speko-ai": {
      "type": "http",
      "url": "https://mcp.speko.ai/mcp"
    }
  }
}

README

spekoai-mcp

FastMCP v4 server for SpekoAI. The hosted endpoint is:

text
https://mcp.speko.ai/mcp

It accepts authenticated POST requests using either OAuth or a Speko Platform API key. Configure the URL and let the client negotiate the protocol; do not add protocol headers by hand:

text
Authorization: Bearer <OAuth access token or sk_live_xxx>Content-Type: application/json

The transport is stateless and JSON-only. Modern clients use MCP 2026-07-28 directly; handshake-era clients such as Cursor negotiate MCP 2025-11-25 through initialize. Both paths remain sessionless: there is no Mcp-Session-Id, SSE response, local OAuth transaction store, or stdio transport. Better Auth owns authorization, consent, refresh tokens, and client registration; the MCP service only validates signed access tokens per request.

Client setup

Use the direct-HTTP installer and select OAuth (the default interactive choice):

bash
npx @spekoai/mcp@latest init

Or configure an OAuth-capable client directly. For example, Codex reads:

toml
[mcp_servers.speko]url = "https://mcp.speko.ai/mcp"

For automation, export a Platform API key and add the bearer setting:

toml
[mcp_servers.speko]url = "https://mcp.speko.ai/mcp"bearer_token_env_var = "SPEKO_API_KEY"

Tool surfaces

Hosted tool surfaces are bound to hostnames; a profile query parameter is ignored. The primary endpoint exposes operational tools using domain/action names:

  • account: organization.get, credits.balance.get, credits.ledger.list, usage.summary.get;
  • agents: agents.list, agents.preview_stacks, agents.create, agents.get, agents.update, agents.delete, deployment/version/tool and monitor operations;
  • sessions and calls: create, list, inspect, transcript, recording, and test call operations;
  • phone numbers, including bringing your own carrier: phone_numbers.sip_connections.create connects a customer SIP trunk and phone_numbers.import attaches a number that rides it, with no SIP gateway or support ticket;
  • custom voices: voice_clones.create clones a voice from a recording link onto ElevenLabs, Cartesia, MiniMax or CSM, and its provider voice id works with audio.synthesize; voice_clones.list, .provision and .delete;
  • knowledge bases, evals, migration helpers, audio helpers, and docs.search.

Builder profile

App builders use the curated host at:

text
https://builder-mcp.speko.ai/mcp

It contains docs search, catalogs, agent reads, stack preview, integration code snippets, the test-call review path, and the limited agents.create and agents.test_call writes. Generated applications use Speko SDKs at runtime; they do not call MCP tools.

Replit profile

Replit uses its own host:

text
https://replit.speko.ai/mcp

It serves 28 tools in build-time order — code_snippets.get, the voice and model catalogs, docs search and stack preview come first, then agent, number and transcript reads, then the writes. It adds the two paths the builder profile omits: knowledge bases, so a voice FAQ has somewhere to keep the FAQ, and phone numbers, which is the next ask after a working in-app assistant. Gateway operations, evals, monitors, scenarios, billing, API keys, migrations and every destructive delete stay out.

Assistant directory hosts

Assistant directories are published on their own hosts, each shaped by that directory's policy. The surface is a property of the host: there is no query parameter, header, or account setting that widens it.

Anthropic MCP Directory
text
https://anthropic.speko.ai/mcp

Reads across the account, speech-to-text, outbound calling, and read-only phone compliance diagnostics:

  • account: organization.get, credits.balance.get, credits.ledger.list, usage.summary.get;
  • agents: agents.list, agents.get, agents.preview_stacks, agents.versions.list, agents.tools.list, agents.tools.get, agents.calls.list, agents.test_call.get;
  • sessions and calls: sessions.list, sessions.get, sessions.transcript.get, sessions.recording.get, calls.get, calls.recording.get;
  • phone numbers: phone_numbers.list, phone_numbers.get, phone_numbers.available.search;
  • knowledge bases: knowledge_bases.list, knowledge_bases.get, knowledge_bases.documents.list, knowledge_bases.documents.get;
  • evals and monitoring: evals.get, agents.monitoring.results.list;
  • audio: audio.transcribe;
  • calling: sessions.phone.create — one outbound call per tool call, with AI disclosure injected server side. ChatGPT and connector calls default to a hard five-minute limit; set body.maxDurationSeconds explicitly for a different limit (30–3600 seconds for S2S, up to 14400 for cascade);
  • hang-up: sessions.end — immediately request hang-up using session_id. It is safe to repeat. An ending response confirms the request; use sessions.get to confirm the session ended;
  • compliance: phone_numbers.kyb.get — OAuth connector consent and declaration submission happen automatically in the backend;
  • migration helpers: migration.workspace.inspect, migration.external_config.parse, migration.session_config.build, migration.briefing.render;
  • other: docs.search.

Deliberately not on this host, because each one either produces synthetic speech on demand or arms something that will:

groupabsent
audio generationaudio.synthesize
live session / call creationsessions.create, agents.test_call
agent configuration and deploymentagents.create, agents.update, agents.deploy, agents.rollback, agents.tools.create, agents.tools.update, agents.tools.delete
knowledge-base writesknowledge_bases.create, knowledge_bases.documents.create, knowledge_bases.documents.delete, knowledge_bases.documents.finalize
phone number provisioningphone_numbers.create, phone_numbers.update
bulk or scheduled evaluationagents.evals.*, agents.monitors.*
irreversible and outward-facing writesagents.delete, phone_numbers.delete, knowledge_bases.delete, share_cards.create

Configuring an agent is equivalent to arming it: a deployed agent speaks on inbound traffic with no further tool call. Agent create, update, deploy and rollback are therefore withheld alongside the generation tool itself. audio.transcribe stays because speech-to-text produces no audio and returns only text.

sessions.phone.create is on this host on purpose. It places one call, to one number, per explicit tool call, using an agent the customer deployed elsewhere — there is no bulk, scheduled or unattended path to it, and the caller cannot configure the agent that speaks. Every call created on a directory host has AI disclosure injected server side: the first thing said is that the caller is an AI, and the agent cannot be prompted out of admitting it. A surface that can read the transcript of a call it cannot place is a viewer, not a connector. sessions.create (a browser session token, useless in a chat client) and agents.test_call (two synthesized agents talking to each other) stay out.

The last row is cut for a different reason. Deleting removes capability rather than arming anything, so those tools are not covered by the rule above — but a published surface has to be describable in one honest clause, and three irreversible deletes plus a creator of public pages meant this one could not be called a read surface. phone_numbers.delete also releases a billed number. Reads of all four resources stay. Calling a withheld tool on this host returns Unknown tool: '<name>', identical to a name that was never registered.

OpenAI Plugin Directory
text
https://chatgpt.speko.ai/mcp

21 tools. A separate list, not a reuse of the Anthropic one, because the two directories forbid different things: OpenAI has no restriction on generated audio, so audio.synthesize and outbound calling stay, while its rules on selling digital goods remove phone-number provisioning and the credits and usage reads. Three of the reads are there to keep agents.test_call from being a dead end: reviewing a test call needs agents.test_call.get for the run's session id, agents.calls.list to recover that id if the run's result is overwritten, and calls.recording.get for the audio.

Authentication and downstream calls

OAuth clients discover Better Auth from the MCP protected-resource metadata. Better Auth issues JWT access tokens bound to the exact MCP resource URL. The MCP server verifies their signature, issuer, audience, expiry, and scopes on every request without retaining OAuth or protocol state.

Product-wide Platform API keys are independently verified with GET /v1/auth/api-key-context on every request. Speko API tools forward API keys unchanged. For OAuth callers, the MCP service mints a separate 60-second JWT bound to the Platform API; it never forwards the client-presented MCP token.

Configuration:

  • SPEKOAI_API_URL — Platform API origin, default https://api.speko.dev;
  • SPEKOAI_ROUTER_URL — Speko Router origin, default https://router.speko.dev. audio.transcribe and audio.synthesize prefer the Router and fall back to the Platform endpoint when the Router cannot serve the request. Both fall back for a session with no Speko API key, because the Router authenticates those and not the OAuth delegation token. audio.transcribe also falls back for any container but WAV/PCM, which the Router does not decode. audio.synthesize falls back when the body names something the Router's speech body cannot say: speed, instructions, spokenForm, a bare model, an intent.region, or more than one allowed provider;
  • SPEKOAI_OAUTH_ISSUER — Better Auth issuer, for example https://platform.speko.ai/api/auth;
  • SPEKOAI_MCP_BASE_URL — public MCP origin used to derive the exact resource audience;
  • SPEKOAI_MCP_DELEGATION_SECRET — 32+ character secret shared only with Platform for stateless API delegation;
  • SPEKOAI_MCP_DEFAULT_PROFILE — deployment-only tool surface served at bare /mcp (builder | connector | chatgpt | customer). Hosted services set it explicitly; public query parameters never select or override it. Unset preserves the legacy full surface for local and self-hosted use.

See docs/fastmcp-v4.md for deployment order, smoke tests, and failure diagnosis.

Source: README.md at commit 88f3712

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.12LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts