Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
A phone number for your business or your AI agent. Kai answers it and calls businesses for you.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
X-KaiCalls-API-KeyAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.
Führe das in deinem Terminal aus
claude mcp add --transport http kaicalls https://www.kaicalls.com/api/mcp --header 'X-KaiCalls-API-Key: your-value'Trag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"kaicalls": {
"url": "https://www.kaicalls.com/api/mcp",
"headers": {
"X-KaiCalls-API-Key": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"kaicalls": {
"type": "http",
"url": "https://www.kaicalls.com/api/mcp",
"headers": {
"X-KaiCalls-API-Key": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
X-KaiCalls-API-Key geheim HTTP headerDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Die Tool-Liste dieses Servers haben wir noch nicht gelesen; wir prüfen die Endpunkte reihum.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde über die Domain kaicalls.com bestätigt (die Registry prüft, wem die Domain gehört)
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir lesen die Tool-Liste, wenn wir den Endpunkt prüfen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: X-KaiCalls-API-Key
Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (1.1.0) kam vor 8 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
A phone number for your business or your AI agent. Kai answers it and calls businesses for you.
Get a business number (or keep yours) with Kai built in. Your phones ring first; Kai answers misses and after-hours calls, takes the details and texts you. See current plans and pricing. This repository is the public connector definition for the hosted KaiCalls MCP server — it documents the endpoint, authentication, and tool catalog so MCP clients and directories can discover and connect to it.
The KaiCalls platform itself is a hosted SaaS — there is no server to install. You connect to the live endpoint below with your KaiCalls account.
| MCP endpoint | https://www.kaicalls.com/api/mcp |
| Transport | Streamable HTTP (JSON-RPC over HTTP POST) |
| Auth | OAuth 2.1 (PKCE S256 + DCR) or kc_live_ API key as Bearer |
| Setup endpoint | https://www.kaicalls.com/api/mcp/acquisition (setup-only subset for first-time buyers) |
| Tools | 171 on the account endpoint (60 read-only, 111 write/setup); 37 on the setup endpoint |
| Homepage | KaiCalls |
| Provider | KaiCalls · connor@kaicalls.com |
| License | MIT (connector definitions and docs) |
| Status | GA — live in production |
A person can connect ChatGPT, Claude or any MCP client and get a real US number:
make_call places an errand call to a US or Canada business (a shop, clinic, office or restaurant), asks the question, presses keys on phone menus, and check_call_status returns the answer. Kai says up front that it is an assistant calling for you, and it does not place AI calls to personal cell phones.What is the KaiCalls MCP connector? It is the official hosted MCP connector for KaiCalls. Existing customers use https://www.kaicalls.com/api/mcp; a first-time buyer can use the setup-only surface at https://www.kaicalls.com/api/mcp/acquisition.
Who should use it? Use it when Claude, ChatGPT, Cursor, an MCP gateway, or another AI client needs to safely inspect KaiCalls agents, calls, transcripts, leads, analytics, and approved setup actions.
Does it require hosting your own server? No. KaiCalls hosts the MCP server. Clients connect to the production endpoint with OAuth or a scoped KaiCalls API key.
Is this the WordPress plugin? No. The approved KaiCalls AI Intake plugin captures website leads from WordPress. This repo documents the agent/MCP connector.
Is this the n8n integration? No. n8n workflows should use n8n-nodes-kaicalls.
integrations/openclaw is the KaiCalls plugin. It adds 8 call and text tools, plus a kaicalls channel so texts to your agent's number start an agent turn. ClawHub publication is pending.integrations/hermes is a portable Agent Plugins v1 package (the hosted MCP server plus a skill). Install it with hermes plugins install https://github.com/KaiCalls/kaicalls-mcp/tree/main/integrations/hermes.[Add KaiCalls to Claude in one click](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=KaiCalls&connectorUrl=https%3A%2F%2Fwww.kaicalls.com%2Fapi%2Fmcp): Claude opens its *Add custom connector* box with the name and URL already filled in. Press Add, then sign in. Owners of a Team or Enterprise workspace can use the admin link to add it for everyone.
Add a custom connector pointing at https://www.kaicalls.com/api/mcp for an existing account, or the acquisition endpoint for setup. Sign in with your KaiCalls account, pick the business on the consent screen, and Allow. See docs/quickstart.md for screenshots and per-client steps.
Pass a KaiCalls API key directly — no OAuth round-trip needed:
Authorization: Bearer kc_live_xxxxxxxxxxxxxxxxxxxx
(X-KaiCalls-API-Key: kc_live_... is also accepted.) Generate keys in the KaiCalls dashboard under Settings → API Keys. See docs/authentication.md.
KaiCalls is a remote server — there is nothing to clone or install. Add it to your MCP client config as a Streamable HTTP server and authenticate with a kc_live_ key. For Cline, edit cline_mcp_settings.json (or use the Remote Servers tab) and add:
{
"kaicalls": { "url": "https://www.kaicalls.com/api/mcp", "type": "streamableHttp", "headers": { "Authorization": "Bearer kc_live_YOUR_KEY" } } }
Replace kc_live_YOUR_KEY with a key from the KaiCalls dashboard under Settings → API Keys. The transport type must be the camelCase string streamableHttp — using streamable-http or omitting it makes Cline fall back to SSE and the connection fails with a 405. Once saved, Cline lists the KaiCalls tools and is ready to use. See llms-install.md for the full agent-driven setup walkthrough.
gemini extensions install https://github.com/KaiCalls/kaicalls-mcp
agy plugin install https://github.com/KaiCalls/kaicalls-mcp
Both connect to the hosted server at https://www.kaicalls.com/api/mcp and sign you in with OAuth the first time a tool runs.
Most clients should connect to the hosted server at https://www.kaicalls.com/api/mcp. For stdio-only clients, this repo ships a small bridge with no dependencies:
docker build -t kaicalls-mcp .
docker run -i --rm -e KAICALLS_API_KEY=kc_live_... kaicalls-mcp
initialize and tools/list work without a key. tools/call needs KAICALLS_API_KEY, which you create at https://www.kaicalls.com/dashboard/settings/api-keys.
The account endpoint exposes 171 tools: 60 read-only and 111 write/setup. Every tool carries MCP safety annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint). The setup endpoint (/api/mcp/acquisition) exposes the 37 tools marked Yes in the Setup surface column, the subset that takes a new business from signup to a working number. The machine-readable inventory, with full descriptions, scopes and annotations, is in mcp.json and server-card.json. In-depth notes for the core tools are in docs/tools.md. The live tools/list response returns each tool's input schema.
| Tool | Scope | Setup surface | What it does |
|---|---|---|---|
get_lsa_account_report | calls:read | Read the authorized advertiser's live Google Local Services aggregate account report, including actual spend, currency and charged lead totals. | |
get_lsa_setup | calls:read | Inspect Google LSA account selection and sync freshness, with setup steps. | |
list_lsa_leads | calls:read | List synced Google LSA leads, charge and credit states, source IDs and rating details. | |
get_lsa_conversations | calls:read | Read the latest 200 synced Google LSA conversation events for an LSA lead, including customer and advertiser messages. | |
get_lsa_report | calls:read | Report LSA lead counts, types, observed statuses, ratings and credit counts for an explicit UTC window (start inclusive, end exclusive). | |
agency_offer_preview | workspaces:write | Builds the publishable manifest and sales kit for an offer draft and returns its fingerprint and revision for publishing. | |
agency_installation_preview_route_receipt | workspaces:write | Returns the evidence that a real call reached the client's voice line and produced a delivered lead notification, with a fingerprint for acknowledgement. | |
agency_installation_preview_handoff | workspaces:write | Returns the staff handoff for an installation with a fingerprint for approval. | |
agency_installation_owner_preview | workspaces:write | Shows the client owner the exact intake facts and voice script prepared for their business, with the hashes needed to approve each. | |
agency_installation_export | workspaces:write | Returns the installation release, intake facts, approved script, staff sheet and checks for handoff or records. | |
agency_installation_preview_offboard | workspaces:write | Shows what offboarding would stop and what it keeps (phone number, sender, connections, billing plan and history), with a fingerprint for approval. | |
agency_care_preview_review | workspaces:write | Shows the exact review-request text, sender number and recipients for customers with a completed service, with a fingerprint for approval. | |
get_agency_workspace | workspaces:read | Read assigned installations, grouped support incidents, accepted billing evidence (also billing:read), or inventory one authorized client's saved facts and actual channel readiness. | |
get_extra_number_status | numbers:read | Yes | Read an owner-authorized extra-number request. |
get_setup_recovery_status | numbers:read | Yes | Read an owner-authorized setup recovery request by its business and idempotency key. |
check_call_status | calls:read | Check the status of a call by its ID | |
list_recent_calls | calls:read | List recent calls for the authenticated business | |
get_transcript | calls:read | Get the transcript and summary of a completed call | |
get_call_recording | calls:read | Get the real call recording URL for a call so reviewers can listen to the voice/audio instead of relying only on the transcript. | |
list_agents | agents:read | Yes | List the KaiCalls agents on the authenticated account. |
get_business_info | agents:read | Yes | Read back what a business already has: profile details, how many agents are configured, and recent call volume. |
get_operational_settings | agents:read | Yes | Audit the business-level operational setup required before changing a live account: staff alert recipients, SMS/email alert flags, escalation rules, textable send-link entries, and assigned agent voice/model/greeting metadata. |
get_activation_status | agents:read | Yes | Read current call readiness and persisted private-test proof for one accessible business. |
list_leads | calls:read | List leads for the authenticated business, with optional status/source/agent filters. | |
get_lead | calls:read | Get full details for a single lead by ID, including the latest AI lead score and explanation. | |
list_voicemails | calls:read | List recent voicemails for the authenticated business, including transcripts and recording URLs. | |
list_sms_messages | sms:read | Read SMS and WhatsApp message evidence for accessible businesses (sms:read), including provider message ID, carrier status, delivery/failure timestamps and failure code. | |
list_campaigns | calls:read | List outbound call campaigns for the authenticated business. |
| list_workflow_templates | calls:read | | List t
Nur der Anfang wird gezeigt; den Rest findest du im Repo