
APIFleet MCP server
Which MCP servers are APIFleet's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-29
- Registry namedev.apifleet/apifleetverified in the MCP registry
The registry name sits under apifleet.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-29
- Tools67
- Server calls itselfapifleet
- Server version1.2.0
- Protocol version2025-06-18
On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 602 ms.
- Its tools do every use case we checked: configure voice assistants in a dashboard or via REST API; bind phone numbers from carriers to voice agents; estimate call cost before placing conversations.
- Checked on 4 of the 7 days it takes to judge reliability.
Once connected
- For "configure voice assistants in a dashboard or via REST API", the likely first call is create_assistant.
- For "estimate call cost before placing conversations", the likely first call is apifleet_estimate_call_cost.
- create_assistant, update_assistant, delete_assistant, set_assistant_tools, set_assistant_knowledge change data without a sign-in: anyone with the address can call them.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
- What an agent can do with it3 of 3 use cases
- Answeredmeasuring4 of the 7 daily checks it takes to print a share
- Median first answer523 ms
- Space in an agent's context≈ 8,880 tokensthe definitions of all its tools (67), which an agent carries on every turn
- Tool definitionsA · 99 of 100
- Typed results0 of 67 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 4 of 67
What an agent can do with it
- can do · configure voice assistants in a dashboard or via REST API
- can do · bind phone numbers from carriers to voice agents
- can do · estimate call cost before placing conversations
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that change data, on a server that answers without a sign-in: create_assistant, update_assistant, delete_assistant, set_assistant_tools, set_assistant_knowledge
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
apifleet_get_provider_matrixPublic, no key: discover implemented voice and carrier integrations, setup boundaries, platform pricing and documentation. No provider request or call is made.
apifleet_estimate_call_costPublic, no key: calculate USD platform fees plus caller-supplied blended provider/carrier rates. An estimate, not a provider quote or invoice. Does not place a call.
apifleet_check_assistant_configPublic, no key: seven static configuration checks. Send a redacted configuration without secrets or customer data. No save, credential verification, full API validation or call-quality certification occurs.
check_entitlementsRead the workspace prepaid balance and funding path. Does not start a checkout or call.
list_assistantsList assistants in the authenticated workspace.
get_assistantGet one assistant belonging to this workspace.
create_assistantCreate a assistant. Saving configuration does not place a call. The REST response includes revision, configuration and attached resource identifiers.
update_assistantUpdate selected assistant fields. Omitted fields retain their values.
delete_assistantDelete this assistant. Review the identifier before deleting; the change cannot be undone.
set_assistant_toolsReplace all attached HTTP tools with existing tools owned by this workspace. Empty tool_ids detaches every tool.
set_assistant_knowledgeReplace all attached knowledge documents. Each document must belong to this workspace.
create_browser_test_tokenIssue a short-lived browser voice-test URL. Opening its WebSocket can incur usage. Never publish the returned token.
list_numbersList number bindings. This does not buy phone numbers from a carrier.
bind_numberBind an existing carrier number to a workspace assistant. This changes incoming call routing; configure the carrier webhook separately.
unbind_numberRemove the routing binding. This does not release or cancel the carrier number.
list_callsRead call logs, summary statistics and pagination. Each row may contain transcript, analysis, costs and recording links; recordings require separate authentication.
create_outbound_callPlace a real telephone call. Ask the user to approve recipient, caller number and expected usage first. Billing/provider/carrier checks are the same as REST. No automatic retry or universal idempotency guarantee.
get_waveformRead recording waveform metadata and available audio channels.
delete_recordingPermanently remove a call recording. The call log remains. Confirm the identifier before deleting.
list_toolsList http tools in the authenticated workspace.
get_toolGet one tool belonging to this workspace.
create_toolCreate a tool. Creating a tool returns its signing secret once. Configuring a tool does not invoke its URL; attached tools can call it during conversations.
update_toolUpdate selected tool fields. Omitted fields retain their values.
delete_toolDelete this tool. Review the identifier before deleting; the change cannot be undone.
list_knowledge_documentsList knowledge in the authenticated workspace.
get_knowledge_documentGet one knowledge document belonging to this workspace.
create_knowledge_documentCreate a knowledge document. Attach documents separately to use them in an assistant. Total injected knowledge has a 200 KiB limit.
update_knowledge_documentUpdate selected knowledge document fields. Omitted fields retain their values.
delete_knowledge_documentDelete this knowledge document. Review the identifier before deleting; the change cannot be undone.
list_webhooksList webhooks in the authenticated workspace.
create_webhookCreate a webhook. Creation returns a signing secret once; verify delivery signatures against the raw body. Events may be retried.
update_webhookUpdate selected webhook fields. Omitted fields retain their values.
delete_webhookDelete this webhook. Review the identifier before deleting; the change cannot be undone.
list_simulation_personasList simulation personas in the authenticated workspace.
get_simulation_personaGet one simulation persona belonging to this workspace.
create_simulation_personaCreate a simulation persona.
update_simulation_personaUpdate selected simulation persona fields. Omitted fields retain their values.
delete_simulation_personaDelete this simulation persona. Review the identifier before deleting; the change cannot be undone.
list_simulation_scenariosList simulation scenarios in the authenticated workspace.
get_simulation_scenarioGet one simulation scenario belonging to this workspace.
create_simulation_scenarioCreate a simulation scenario.
update_simulation_scenarioUpdate selected simulation scenario fields. Omitted fields retain their values.
delete_simulation_scenarioDelete this simulation scenario. Review the identifier before deleting; the change cannot be undone.
list_simulationsList simulations in the authenticated workspace.
get_simulationGet one simulation belonging to this workspace.
create_simulationCreate a simulation.
update_simulationUpdate selected simulation fields. Omitted fields retain their values.
delete_simulationDelete this simulation. Review the identifier before deleting; the change cannot be undone.
list_simulation_runsList simulation runs and pagination; inspect status before starting another run.
get_simulation_runRead a run, its evaluations and linked call when available.
delete_simulation_runDelete a completed simulation result. Running runs may reject deletion.
start_simulation_runQueue an asynchronous test. Models and speech can incur usage. Approve the run first and poll the returned identifier; do not enqueue again while it is running.
start_simulation_batchQueue every simulation for one assistant. This can incur multiple test runs; approve the batch first.
list_tts_ratesRead configured voice-cost reference rates. These are not an invoice or a complete call price.
list_tts_voicesRead a provider voice catalog using configured server-side credentials. Catalog failure may return an empty list and error; it is not evidence the provider has no voices.
list_voice_presetsRead configured runnable voice presets. Provider catalog requests may reach a vendor.
get_assistant_voice_presetsRead voices compatible with this assistant configuration.
get_tts_settingsRead supported provider voice settings and validation ranges.
list_provider_credentialsList which provider credentials are configured. Returns metadata only, never provider secret values.
list_api_keysList this workspace API-key metadata. Full key values cannot be retrieved.
The first 60 of 67, as the server listed them.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"apifleet": {
"type": "http",
"url": "https://apifleet.dev/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http apifleet https://apifleet.dev/mcpclaude.ai, ChatGPT and other clients: add https://apifleet.dev/mcp as a custom connector in the settings.
OpenAPI spec
44 paths, read 2026-10-29. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.