One MCP endpoint. Real Israeli numbers, Hebrew-first voice, call flows written as JSON. No dashboard to click through.
claude mcp add --transport http mitsitik https://api.mitsi.co.il/mcp
The platform is agent-native: strict schemas, self-describing limits, and agent docs at /llms.txt. Add the server, drop in your API key, and your assistant can claim numbers and write call flows.
$ claude mcp add --transport http mitsitik \ https://api.mitsi.co.il/mcp \ --header "Authorization: Bearer YOUR_API_KEY" # then just ask: > what can this telephony platform do, and show me my numbers
{
"mcpServers": {
"mitsitik": {
"url": "https://api.mitsi.co.il/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}
$ curl -X POST https://api.mitsi.co.il/mcp \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Need a key? Early access is invite-only right now — request one.
Named sections of steps — play, gather, forward, schedule, record_call, and more. Validated on write, so an agent can't ship a broken flow. Here's a real Hebrew restaurant IVR:
{
"menu": [{
"verb": "gather",
"say": "שלום, הגעתם למסעדת הגליל.
להזמנת מקום הקישו 1…",
"on": {
"1": [{"verb":"goto","section":"reservation"}],
"3": [{"verb":"forward","to":["+9725…"],
"cli":"caller"}]
}
}]
}
Native Hebrew voice and menus. Vapi, Retell and Bland don't do this.
07x DIDs on a real trunk — not a foreign gateway spoofing a local CLI.
MCP-first. Few verbs, strict schemas. Designed for an AI to drive, not a human to click.
Israeli caller-ID law, fraud rails, and recording-consent enforced in the core.
Call this number. You'll reach a Hebrew restaurant IVR an AI provisioned over this API — greeting, menu, reservations — on a real Israeli line. No slides. Just dial.