Modality MCP

Your event CRM,
as an MCP server

Connect Claude, Cursor, or any MCP client to Modality. Tickets, contacts, campaigns, automations, and documents, exposed as tools, scoped to your workspace, on every call.

Get an API key Read the API docs

Streamable HTTP · JSON-RPC 2.0Protocol 2025-06-1830+ tools

POST /api/mcp

# tools/call → create an event
POST https://modalitystudio.com/api/mcp
Authorization: Bearer mk_live_••••••••••••
Content-Type: application/json

{
  "jsonrpc": "2.0",  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create_event",
    "arguments": {
      "title": "AFTERGLOW",
      "startsAt": "2026-08-29T20:00:00Z"
    }
  }
}

What it is

One endpoint. Any AI client.

Modality speaks the Model Context Protocol, so agents treat your workspace as a native set of tools.

Any MCP client

Claude, Cursor, or your own agents connect over standard Streamable HTTP, no SDK lock-in, no custom glue.

Workspace-scoped

The key is the tenant. Every call is bound to your workspace, there is no path to cross-workspace access.

Audited & rate-limited

Every tool call is written to an audit log, requests are rate-limited, and keys are revocable in one click.

Capabilities

The whole platform, as tools

Your agent can run the same operations your team does in the app.30+ tools and growing.

Events & ticketing

Spin up events, ticket types, and promo codes.

create_eventcreate_ticket_typecreate_promo_codelist_eventsget_event

CRM & audience

Contacts, lists, tags, notes, and tasks.

create_contactget_contactcreate_listadd_contact_to_listcreate_tagcreate_notecreate_tasklist_contacts

Campaigns & automation

Email, sequences, automations, and social.

create_campaigncampaign_statscreate_sequencecreate_automationcreate_social_postlist_campaigns

Custom objects

Model anything and link records together.

create_object_typecreate_recordget_recordlink_recordslist_object_types

Documents & e-sign

Send documents and track signatures.

bulk_send_documentlist_envelopesget_envelopelist_document_templates

Invoices & analytics

Bill customers and read your numbers.

create_invoiceinvoice_statsanalytics_overviewlist_invoices

How it works

Connected in four steps

Create a Workspace API key

In Modality, open Settings → API keys and generate a key. It looks like mk_live_… and is bound to that one workspace.

Point your MCP client at Modality

Add the server URL https://modalitystudio.com/api/mcp and pass the key as an Authorization: Bearer header.

The client discovers your tools

On connect, the client calls tools/list and Modality returns the full, typed tool catalog it can invoke.

Every call runs scoped & audited

Requests execute against your workspace only, the tenant comes from the key, never the request body, and each call is logged.

mcp client config

{
  "mcpServers": {
    "modality": {
      "url": "https://modalitystudio.com/api/mcp",
      "headers": {
        "Authorization": "Bearer mk_live_••••••••"
      }
    }
  }
}

tools/list → discover the catalog

# the client asks Modality what it can do
{ "jsonrpc": "2.0", "id": 2, "method": "tools/list" }

# server: modality v0.1.0 · protocol 2025-06-18

Security

Safe to hand to an agent

Access is bounded by the key, observable end to end, and reversible in an instant.

Workspace-scoped by key

The tenant is bound to the key. No argument can reach another workspace.

Full audit log

Every tool call is recorded for review: who, what, and when.

Rate-limited

Per-key limits keep automated clients predictable and safe.

Revocable anytime

Roll or revoke a key from Settings and access stops immediately.

No raw PII in logs

Sensitive fields are redacted before anything is written down.