New

KrosAI, now available
as an MCP server.

Connect your AI voice agents directly to real telecom infrastructure — phone numbers, carrier connectivity, KYC compliance, and fraud detection — from inside your MCP client.

Connect via Smithery Read the docs

Server endpoint

https://api.krosai.com/mcp

Transport: Streamable HTTP · Auth: OAuth 2.1 (dynamic client registration)

Why this exists

AI voice agents are only as useful as the phone line they can reach. Getting a working number in most emerging markets means months of carrier back-and-forth, KYC paperwork, and compliance approvals before a single call goes through — we know, because that's exactly the wall we hit building our own AI voice product.

KrosAI solves that problem as infrastructure: one API for identity, carrier connectivity, compliance, and fraud detection. The MCP server puts that infrastructure directly into your development workflow — no dashboard required.

What you can do

Provision & manage phone numbers

Claim, search, and configure numbers across Nigeria, Kenya, Ghana, the US, and the UK.

Attach AI endpoints

Connect ElevenLabs, Vapi, Retell, or your own AI voice agent to a live number in seconds.

Query call data

Pull call history, transcripts, recordings, and lifecycle events.

Run diagnostics

Check SIP status, porting progress, and number health.

Manage your org

API keys, integrations, and billing, all from your MCP client.

How it works

1
Connect
Add the KrosAI MCP server to Claude or your MCP client of choice.
2
Authenticate
Link your KrosAI account (or create one).
3
Build
Provision numbers and wire up your AI agent, right from your workflow.

Add KrosAI to an MCP client

{
  "mcpServers": {
    "krosai": {
      "url": "https://api.krosai.com/mcp"
    }
  }
}

For voice agent builders

Built for developers building voice agents

KrosAI isn't a voice model — we're the telecom layer underneath the ones you're already using. Whether you're building on Pipecat, Vapi, Retell, or ElevenLabs, the MCP server means the compliance and carrier work happens without leaving your development environment.