SDKs and tools

MCP server

Let an AI coding agent send SMS, run phone verification, buy Canadian numbers and check CASL consent for you, from our hosted endpoint or a local copy.

AI agents (MCP)

HonkIO ships a Model Context Protocol server, so an AI coding agent can send SMS, run phone verification, buy Canadian numbers and check CASL consent on your behalf, in plain language and with no SDK to wire up. It talks to this same REST API with your API key, from our hosted endpoint or from a copy on your machine.

The hosted endpoint needs nothing installed. Point your client at it and send your key in a header. In Claude Code:

bash
claude mcp add --transport http honkio https://mcp.honkio.ca/mcp \
  --header "Authorization: Bearer mk_test_YOUR_KEY"

Or in a shared .mcp.json, reading the key from your shell so it never lands in git. Cursor, VS Code, claude.ai connectors and the Claude Messages API connect the same way, by URL.

json
{
  "mcpServers": {
    "honkio": {
      "type": "http",
      "url": "https://mcp.honkio.ca/mcp",
      "headers": { "Authorization": "Bearer ${HONKIO_API_KEY}" }
    }
  }
}

VS Code asks for your key the first time the server starts and keeps it. Cursor installs with a placeholder: replace mk_test_YOUR_KEY in ~/.cursor/mcp.json before use.

You can also sign in instead of pasting a key. In Claude Code, add the endpoint without a header and run /mcp: a page on honkio.ca asks you to approve the connection and choose live or test mode. A live connection also asks for your account password. Clients that support OAuth, such as claude.ai connectors, do the same on their own. Each connection appears on your API keys page and can be revoked there.

Prefer to run it locally? The same server is on npm. Nothing to install: npx fetches it on first use.

json
{
  "mcpServers": {
    "honkio": {
      "command": "npx",
      "args": ["-y", "@honkio/mcp"],
      "env": { "HONKIO_API_KEY": "mk_test_YOUR_KEY" }
    }
  }
}

Use a test key while you explore: it works before your first top-up, and sends and verifications are simulated for free, nothing is sent or charged. Tools that buy or release phone numbers, change webhooks, or run erasure need a live key.

64 tools are available, covering the list below plus email. The 17 email tools appear only when email is enabled on your account.

  • Sending SMS, listing messages and reading delivery status
  • Starting a verification code, checking it and listing attempts
  • Searching, buying and releasing Canadian numbers
  • Recording and checking CASL consent, and handling opt-outs
  • Managing webhooks, and replaying failed deliveries
  • Account details, usage and API key management
  • Checking usage against the daily cap, requesting a higher volume and seeing the top-up allowance
  • Email: sending, scheduled sends, domains, suppressions and templates (email accounts only)

Then just ask

"Find an available 416 number, tell me what it costs, and don't buy anything yet."

On a live key, buying a number and sending messages spend real money. Agents act on instructions that can be vaguer than you intended, so explore with a test key first.
Full tool reference on npm →