# Connect Grok / xAI API to voice tools | APIFleet

> Allow a Grok API application to call APIFleet’s public MCP tools. Copy the APIFleet MCP configuration and understand public tools, authentication and billing.

Canonical URL: https://apifleet.dev/plugins/grok
Markdown Mirror URL: https://apifleet.dev/plugins/grok.md
LLM index: https://apifleet.dev/llms.txt
MCP discovery: https://apifleet.dev/.well-known/mcp.json

Allow a Grok API application to call APIFleet’s public MCP tools.

## Connect in your client

- Use the remote MCP tool configuration below in an xAI Responses request.
- Allow only the public tools your application needs; the example permits cost estimation.
- Your xAI account and model usage are billed separately. This is a developer API configuration, not a claimed Grok web-app plugin.



```
{
  "type": "mcp",
  "server_url": "https://apifleet.dev/mcp",
  "server_label": "apifleet",
  "allowed_tools": [
    "apifleet_estimate_call_cost"
  ]
}
```



Client setup reference: [official documentation](https://docs.x.ai/developers/tools/remote-mcp). Reviewed 22 October 2026. Client versions and account controls may differ; these are connection recipes, not marketplace listings.

## Try one useful request



```
Estimate the cost of 600 connected AI seconds with $0.04/minute providers and $0.01/minute carrier using apifleet_estimate_call_cost.
```



The illustrative ten-minute workload returns $0.30 platform + $0.40 providers + $0.10 carrier = $0.80 estimated total. Provider and carrier rates are example inputs, not vendor quotes.
- apifleet_get_provider_matrix: Public, no key: discover implemented voice and carrier integrations, setup boundaries, platform pricing and documentation. No provider request or call is made.
- apifleet_estimate_call_cost: Public, 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_config: Public, 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.

## Move into your workspace

Create a key in [API keys](https://apifleet.dev/app/api-keys), then configure Authorization: Bearer <key> privately in a compatible client. A key grants full workspace access. Cookies do not authenticate MCP requests.
Without a key, private tools return ERR_API_KEY_REQUIRED with the key and funding paths. Paid calls retain the prepaid billing checks: $0.03 per connected AI minute plus providers and carrier, minimum $10 funding, no subscription or trial credits.
[Read the protocol and authenticated examples](https://apifleet.dev/docs/mcp). Do not auto-approve paid calls, destructive changes or live route changes.

## If the connection fails

Check that the transport is Streamable HTTP and the URL ends in /mcp. A 405 on a browser GET is expected: tools use POST. A 401 with a configured key means the key needs checking; an expired key does not fall back to anonymous access. If your client only supports OAuth or legacy SSE, choose a compatible client or transport.

## Bring your next conversation.

Explore the API, or sign in to your existing workspace. New workspace access is currently limited; contact us to discuss your project.
[Explore the docs ](https://apifleet.dev/docs)[Sign in](https://apifleet.dev/app/assistants)[Ask about access](mailto:mariano@apifleet.dev?subject=APIFleet%20workspace%20access)