Connect your AI agent to Furcata with MCP

Furcata speaks MCP, the Model Context Protocol. That means your favorite AI assistant can work inside your Furcata account for you: look up contacts, queue a message, check how a campaign performed. Ask in plain language, and your agent takes care of the rest.

What your agent can do

Browse your accounts, services and users.
List, add and update contacts, and keep contact counts fresh.
Read recent conversations and archive the ones you are done with.
Send SMS, MMS and WhatsApp messages to your existing contacts.
Search for phone numbers available in your area.
Manage webhook subscriptions.
Pull usage and cost reports for one account or all of them.

Your agent only sees what your Furcata role allows. Buying numbers stays in the app on purpose, so nothing gets purchased by accident.

Connect in two minutes

Add Furcata as an MCP server in any client that supports remote servers, such as Claude, GitHub Copilot or VS Code. Use this address:

mcp.json

{
  "mcpServers": {
    "furcata": {
      "type": "http",
      "url": "https://api.furcata.com/v0/mcp"
    }
  }
}

Some clients call the root key "servers".

When your client asks, sign in with your Furcata account. Treat access tokens like passwords: keep them out of shared files and repositories.

Good to know

Messages sent by your agent are real messages, billed at your usual rates. Ask it to confirm before sending to a big list.
Add a new phone number as a contact before messaging it.
Fair-use limits keep everyone fast. If your agent goes too quickly, it will be asked to slow down.

Prefer to code it yourself? The same capabilities are available through the Furcata REST API.

How the connection works

The MCP server lives at https://api.furcata.com/v0/mcp. It accepts POST requests only and answers with a single JSON body, so it works with any client that supports remote MCP servers over HTTP.

Every request carries your access token in an Authorization header.
The connection is stateless. There is no session to keep alive between calls.
Your agent acts as you. It can only reach the accounts and actions your Furcata role allows.

Signing in

Clients that support OAuth can register themselves and sign you in without any manual setup. Furcata publishes its OAuth metadata so the client can discover everything it needs:

https://api.furcata.com/v0/.well-known/oauth-authorization-server
https://api.furcata.com/v0/.well-known/oauth-protected-resource/mcp

The client registers itself, opens the Furcata sign-in page, and exchanges the returned code for an access token. Proof keys (PKCE) are required, so the code cannot be replayed by anyone else.

If your client asks for a token instead, you can paste a Furcata access token directly. See Authentication and OAuth 2.0 for the full flow.

curl -X POST https://api.furcata.com/v0/auth/register \
  -H "Content-Type: application/json" \
  -d '{
    "client_name": "My MCP client",
    "redirect_uris": ["http://localhost:8765/callback"]
  }'

mcp.json with a token

{
  "mcpServers": {
    "furcata": {
      "type": "http",
      "url": "https://api.furcata.com/v0/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ACCESS_TOKEN"
      }
    }
  }
}

Access and safety

Reading tools need an account administrator. Removing a webhook subscription needs the account owner.
Sending a message and deleting a webhook are marked as destructive, so well-behaved clients ask you first.
Every tool call is recorded with who ran it, what it did and how long it took. Arguments are redacted in the log.
Buying a number is deliberately not available to agents. Do that in the Furcata app.

If your agent calls tools too quickly it receives a rate limit error and should wait before retrying.

Connect your AI agent with MCP

Share article