Inkbox

Name: Inkbox MCP Server
Availability: InStock
Author: Inkbox

Communication59 tools

Give an AI agent its own email address, phone number and iMessage line. Fifty-nine tools that send mail, send texts and read call transcripts — and a Claude-only endpoint that deliberately withholds the power to place a call.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 19 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Inkbox via MCP

https://inkbox.ai/mcp/anthropic

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Inkbox Tools & Capabilities (59)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

One OAuth scope, inkbox.full_service, over all 59 tools. Consent cannot be narrowed to reads. Inkbox's own documentation describes it as full-service access until revoked.
Anthropic's directory record carries no permissions field at all — not read-only, not read-and-write. The seventeenth instance of this pattern in the catalogue.
Six tools transmit to third parties, and email sends reach any address the model supplies.
inkbox_email_forward moves a message whose contents are not visible in the tool call.
Six delete tools, including inkbox_email_thread_delete, which removes a whole correspondence.
Contact deletion has no documented restore. Inkbox documents grace periods for domains and their absence for tunnels; for contacts it documents neither. We did not verify recoverability.
Call transcripts are verbatim third-party speech. Segments are tagged by speaking party, and the remote segments are the other person.
No documented call-recording notice or consent guidance. SMS consent is documented in detail; we found no call-recording equivalent in the published docs. This is an observed documentation gap and not a legal conclusion — this page gives no legal advice.
The vCard export is capped at 25 contacts per call and returns inline, but the import accepts
The voice exclusion is a property of the /anthropic path, not of Inkbox. The generic and OpenAI endpoints are documented as serving what Inkbox calls the same catalog. Register the Claude path.
Prompts are contested. Inkbox's docs describe prompts; Anthropic's snapshot lists none. Unverified.
SMS consent writes are gated to organisations on their own active, customer-managed 10DLC campaign; others receive 409 customer_campaign_required. Only the consent *reads* appear in the tool list.
Free-plan mail carries a footer. Inkbox documents a "Sent via Inkbox" footer on outbound mail, removable on paid plans, and states that signed or encrypted mail cannot be sent while it applies.
We could not confirm a plan floor for MCP itself. Inkbox gates individual features by plan; we found no statement that MCP access requires a specific tier.
We did not read the live schemas. The endpoint returned 401 to an anonymous handshake, so tool names come from Anthropic's directory snapshot and their behaviour from Inkbox's published API reference and OpenAPI spec — not from a wire response, and with no safety annotations available at all. No tool on this page can be described as annotated read-only or annotated destructive, because we could not read the annotations. Treat every write-shaped name as acting.

Frequently asked questions

Can the Inkbox MCP server send emails and text messages on its own?

It can send both, but only when you ask it to. Four tools transmit to outside parties: email send, reply, reply-all and forward, plus SMS and iMessage sends. Anthropic's directory record states plainly that Inkbox does not watch your inbox in the background or send anything on its own. Every send is a tool call your client can hold for approval.

Can the Inkbox connector place a phone call?

No, and that is a deliberate cap. Inkbox's REST API documents a place-call operation that dials a number and can run a hosted voice agent on the line. Inkbox's own MCP documentation states the Claude endpoint excludes hosted voice tools — placing and ending calls, call settings and voice-agent configuration. Call history and transcripts stay readable. No tool in the 59 dials anyone.

What do the Inkbox call transcript tools actually reach?

Verbatim text of phone conversations. Inkbox documents transcripts as generated automatically during calls, returned as ordered segments tagged with the speaking party — local, remote or system — and a millisecond offset. The remote segments are the other person's words. Access is scoped to the connected identity; Inkbox states transcripts for any other identity's calls return a masked 404.

Does Inkbox document a recording notice or consent requirement for calls?

Not in the documentation we read. Inkbox documents SMS consent in detail — a per-recipient opt-in registry updated automatically from STOP and START keywords — but we found no equivalent guidance on call-recording notice or announcement anywhere in its published docs. We state that as an observed gap. This page gives no legal advice and asserts nothing about what any law requires.

How much contact data can the Inkbox vCard export tool pull out at once?

Twenty-five contacts per call, returned inline. Inkbox's OpenAPI spec caps the export request at 25 contact identifiers, minimum one, and the response carries the vCard text directly in the JSON body alongside a contact count. There is no download URL and no signed link. The vCard payload is capped at one million characters.

Does the Inkbox connector let you grant read-only access?

No. The OAuth metadata advertises exactly one scope, inkbox.full_service, and it does not divide by verb. The same grant that reaches call transcripts also reaches the sends, the deletes and the contact export. Inkbox's own documentation describes the grant as full-service access to the selected identity until you revoke it. Per-call approval in your client is the only remaining control.

What do you need to enable the Inkbox MCP connector?

An Inkbox account and an identity to connect. Inkbox operates a free plan alongside paid tiers, and its documentation gates specific features rather than API access as a whole — outbound mail carries a footer on the free plan, and SMS consent writes require your own registered 10DLC campaign. We could not verify from public docs whether any plan floor applies to MCP itself.

Sources

Inkbox documentation index — https://inkbox.ai/docs (fetched 2026-08-19; the documentation URL in Anthropic's directory) · retrieved 2026-08-19
Inkbox llms.txt — https://inkbox.ai/llms.txt (fetched 2026-08-19; identity-layer positioning, capability list covering email, phone, iMessage and vault, and the pointers to the single-file docs export, sitemap and OpenAPI spec used throughout this page) · retrieved 2026-08-19
Inkbox MCP server documentation — https://inkbox.ai/docs/mcp.md (fetched 2026-08-19; the three-endpoint table for generic, ChatGPT and Claude clients; the statement that each endpoint has its own OAuth resource identifier; the Claude-endpoint voice exclusion covering placing and ending calls, call settings, hosted voice-agent configuration, incoming-call handling and phone-readiness checks; full-service grant description; X-API-Key alternative; the prompt list that conflicts with the directory snapshot) · retrieved 2026-08-19
Inkbox Calls API reference — https://inkbox.ai/docs/api/phone/calls.md (fetched 2026-08-19; the place-call operation, client_websocket and hosted_agent modes, the voice-agent reason brief, and voicemail detection — all absent from this connector) · retrieved 2026-08-19
Inkbox Transcripts API reference — https://inkbox.ai/docs/api/phone/transcripts.md (fetched 2026-08-19; automatic generation during calls, ordered segments with party of local/remote/system and millisecond offsets, identity-scoped access masked as 404, and the deprecated number-scoped route) · retrieved 2026-08-19
Inkbox Manage Contacts API reference — https://inkbox.ai/docs/api/contacts/manage.md (fetched 2026-08-19; contact object fields and per-field caps, and the delete operation returning 204 with no documented restore) · retrieved 2026-08-19
Inkbox vCards API reference — https://inkbox.ai/docs/api/contacts/vcards.md (fetched 2026-08-19; import accepts up to 5 MB and 1000 cards with per-card isolation; the single-contact .vcf download route) · retrieved 2026-08-19
Inkbox SMS Opt-Ins API reference — https://inkbox.ai/docs/api/phone/sms-opt-ins.md (fetched 2026-08-19; per-recipient consent keyed to org and number, automatic STOP/START updates, opted_in/opted_out states, and the customer_campaign_required 409 gating consent writes to customer-managed 10DLC campaigns) · retrieved 2026-08-19
Inkbox OpenAPI specification — https://inkbox.ai/api/openapi.json (fetched 2026-08-19; version 0.1.0. Counted mechanically: 216 paths, 307 operations, 45 tag groups. Source for the vcard-export request cap of 25 contact identifiers, the inline vcard response field capped at 1,000,000 characters, and the absence of any contact-restore operation) · retrieved 2026-08-19
Inkbox complete documentation export — https://inkbox.ai/docs/all.md (fetched 2026-08-19; searched in full for recording, consent, notice and disclosure language. SMS consent is documented; no call-recording notice guidance was found. Also the source for the domain 24-hour restore window, the tunnel no-restore statement, the free-plan mail footer, and the vault exclusion from the platform assistant) · retrieved 2026-08-19
Inkbox robots.txt — https://inkbox.ai/robots.txt (fetched 2026-08-19; User-agent: * with Allow: / and Disallow: /api/ and /rpc/, plus per-crawler blocks repeating the same rules. No Content-Signal directives were present in the file or the response headers) · retrieved 2026-08-19
Live RFC 9728 protected-resource descriptor — https://inkbox.ai/.well-known/oauth-protected-resource/mcp/anthropic (fetched 2026-08-19; the path-append form named by the www-authenticate header. HTTP 200, application/json, 194 bytes, resource https://inkbox.ai/mcp/anthropic, authorization server https://inkbox.ai/mcp/oauth. The root form returns HTTP 200 JSON of 184 bytes echoing resource https://inkbox.ai/mcp — a genuinely distinct document, confirming a real per-client family. The path-insert form returns HTTP 404 with a zero-byte body and no content type) · retrieved 2026-08-19
Live RFC 8414 authorization-server metadata — https://inkbox.ai/.well-known/oauth-authorization-server (fetched 2026-08-19; issuer https://inkbox.ai/mcp/oauth, authorization_code and refresh_token grants, PKCE S256, a registration_endpoint, resource_indicators_supported true, client_id_metadata_document_supported true, and scopes_supported of exactly ["inkbox.full_service"]) · retrieved 2026-08-19
Live anonymous probe — 2026-08-19: an anonymous initialize POST to https://inkbox.ai/mcp/anthropic returned HTTP 401 with body {"error":"authorization_required"} and header www-authenticate: Bearer resource_metadata="https://inkbox.ai/.well-known/oauth-protected-resource/mcp/anthropic". No tool was ever called and no authentication was attempted · retrieved 2026-08-19
Anthropic connector directory — https://claude.ai/directory/39b95a4e-4c4a-4291-9755-dc8fd38ad7be (snapshot 2026-08-16; 59 tool names all prefixed inkbox_, prompt_names an empty list, no permissions field on the record, author Inkbox, partner tier, added 2026-08-05. Source for the identity-scoping statement, the no-background-watching statement, and the explicit denial that the connector can place, answer or end calls or generate audio) · retrieved 2026-08-16