MCP server

Configure an MCP-capable agent against this URL and it can query the spec, the changelog, announcements, and best-practice guidance directly — no skill-file download, no portal scraping.

Endpoint

Streamable HTTP, stateless, no authentication. Read-only — the underlying tools only surface data that is already public on the portal.

POST https://developer.telavox.com/mcp

Tools

Tools are typed: arguments are validated server-side, responses are bounded in size, and the agent can call them concurrently. The current set:

search_endpoints(api, query, limit?): Substring search across an OpenAPI spec — returns {method, path, summary, tag} tuples.
get_endpoint(api, method, path): Returns the OpenAPI operation fragment for a single endpoint.
lookup_migration(v1_endpoint): Find the CAPI equivalent of a legacy v1 path.
get_best_practice(topic): Markdown excerpt for one of: auth, retries, traffic, schema, identification, policy.
list_announcements(api?, type?, since?): Filtered view of the lifecycle announcements catalog.
list_changes(api, since?, breaking_only?, limit?): Recent spec-changelog rows for an API.
get_changelog_entry(id): Permalink lookup for one changelog row, including the full oasdiff details.
current_versions(api?): Spec versions tracked for each API, with endpoint counts for hosted specs.

Resources

Resources are URIs the agent can read directly without a tool call. Use these for bulk content (the whole OpenAPI spec, the full announcements feed) and the tools for queries.

telavox://specs/capi: Current CAPI OpenAPI spec, cached.
telavox://specs/papi: Current PAPI OpenAPI spec, cached.
telavox://announcements.json: Lifecycle announcements feed.
telavox://skills/capi.md: Self-contained Markdown skill for CAPI — same file served at /skills/.
telavox://skills/papi.md: Self-contained Markdown skill for PAPI.
telavox://skills/v1-to-capi-migration.md: Self-contained Markdown skill for the v1 → CAPI migration.

Configure your agent

Most MCP-capable clients can be configured by URL. Replace the placeholder with this portal’s MCP endpoint shown above.

Claude Code

Use the claude mcp add command and pick the streamable-http transport:

claude mcp add telavox --transport http https://developer.telavox.com/mcp

Claude Desktop

Open Settings → Developer → Edit Config and add the entry below to your mcpServers map.

{
  "mcpServers": {
    "telavox": {
      "transport": {
        "type": "streamable-http",
        "url": "https://developer.telavox.com/mcp"
      }
    }
  }
}

Other MCP-capable agents

Point your client at the endpoint and select the Streamable HTTP transport. The server is stateless and requires no authentication.

Discovery

A small manifest is published at /.well-known/mcp — the same URL pattern emerging across hosted MCP servers — so agents can autodiscover the transport, version, and capabilities.

GET https://developer.telavox.com/.well-known/mcp

Safety

The MCP is read-only by design. It does not proxy your API requests, never sees customer credentials, and surfaces only data that is already public on the portal. Mutating calls still happen on the agent side with the user’s own token.