mcp

# spekoai-mcp

[![smithery badge](https://smithery.ai/badge/abat/speko)](https://smithery.ai/servers/abat/speko)

Model Context Protocol server for [SpekoAI](https://speko.ai). The hosted
server exposes one authenticated endpoint:

```txt
https://mcp.speko.ai/mcp
```

It supports OAuth for interactive MCP clients and Speko API keys for clients
that can send custom request headers.

## Install in an MCP client

OAuth-capable clients:

```json
{
  "mcpServers": {
    "spekoai": {
      "url": "https://mcp.speko.ai/mcp"
    }
  }
}
```

API-key clients:

```json
{
  "mcpServers": {
    "spekoai": {
      "url": "https://mcp.speko.ai/mcp",
      "headers": {
        "Authorization": "Bearer sk_live_xxx"
      }
    }
  }
}
```

## Surfaces

The hosted server exposes the operational tools below plus a docs self-serve
surface: the `docs.search` tool (full-text search over bundled Speko docs)
and the `spekoai://docs/index` + `spekoai://docs/{slug}` resources. MCP
prompts, components, and scaffolding tools are not advertised.

Tool names use domain/action dot notation for client grouping.

### Account

- `organization.get`
- `credits.balance.get`
- `credits.ledger.list`
- `usage.summary.get`

### Agents and Tools

- `agents.list`
- `agents.create`
- `agents.get`
- `agents.update`
- `agents.delete`
- `agents.tools.list`
- `agents.tools.create`
- `agents.tools.get`
- `agents.tools.update`
- `agents.tools.delete`

### Versions, Sessions, and Calls

- `agents.deploy`
- `agents.rollback`
- `agents.versions.list`
- `sessions.create`
- `sessions.phone.create`
- `sessions.list`
- `sessions.get`
- `sessions.transcript.get`
- `sessions.recording.get`
- `agents.calls.list`
- `calls.get`
- `calls.recording.get`

### Phone Numbers, Knowledge Bases, and Evals

- `phone_numbers.list`
- `phone_numbers.available.search`
- `phone_numbers.create`
- `phone_numbers.get`
- `phone_numbers.update`
- `phone_numbers.delete`
- `knowledge_bases.create`
- `knowledge_bases.list`
- `knowledge_bases.get`
- `knowledge_bases.delete`
- `knowledge_bases.documents.list`
- `knowledge_bases.documents.create`
- `knowledge_bases.documents.get`
- `knowledge_bases.documents.delete`
- `knowledge_bases.documents.finalize`
- `agents.evals.list`
- `agents.evals.create`
- `agents.evals.run`
- `evals.get`

### Build and Migration Helpers

- `migration.workspace.inspect`
- `migration.session_config.build`
- `migration.external_config.parse`
- `migration.briefing.render`
- `share_cards.create`

### Docs

- `docs.search` - full-text search over the bundled Speko docs (SDK/adapter
  READMEs, hosted llms.txt exports, migration guides). Hits link to
  `spekoai://docs/{slug}` resources; `spekoai://docs/index` lists every doc.

## Auth model

The server has no long-lived SpekoAI credential of its own. Tools forward the
caller credential to the Speko API. The credential can be an OAuth access token
minted by the platform or a Speko API key supplied by the MCP client as
`Authorization: Bearer ...`.

If OAuth env vars are configured, `/mcp` accepts OAuth or Speko API keys. If
OAuth env vars are absent, `/mcp` still requires a valid Speko API key. Partial
OAuth configuration fails closed at startup.