New

MCP server

The Jawbly MCP server exposes your account as tools any Model Context Protocol client can call: Claude Code, Claude Desktop, Cursor and more. Give an agent your API key and it can manage assistants, sync catalog and read conversations on your behalf.

Add to Claude Code

New

terminal

claude mcp add jawbly \
  -e JAWBLY_API_KEY=jwb_live_xxxxxxxxxxxxxxxxxxxxxxxx \
  -- npx -y @jawbly/mcp

Prefer to edit config directly? Add this to your .mcp.json (or Claude Desktop / Cursor MCP config):

.mcp.json

{
  "mcpServers": {
    "jawbly": {
      "command": "npx",
      "args": [
        "-y",
        "@jawbly/mcp"
      ],
      "env": {
        "JAWBLY_API_KEY": "jwb_live_xxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

Available tools

Each API domain is surfaced as an MCP tool. Scopes on your API key decide what the agent can actually do.

jawbly_messages

Read and manage messages for the authenticated business.

jawbly_conversations

Read and manage conversations for the authenticated business.

jawbly_contacts

Read and manage contacts for the authenticated business.

jawbly_assistants

Read and manage assistants for the authenticated business.

jawbly_skills

Read and manage skills for the authenticated business.

jawbly_catalog

Read and manage catalog for the authenticated business.

jawbly_records

Read and manage records for the authenticated business.

jawbly_analytics

Read and manage analytics for the authenticated business.

jawbly_usage

Read and manage usage for the authenticated business.

Run it standalone

The server also runs over stdio for any custom MCP client.

It reads your key from JAWBLY_API_KEY:

terminal

JAWBLY_API_KEY=jwb_live_xxx npx -y @jawbly/mcp

Works with any stdio-based MCP client.