MCP Server

The Meshes MCP server implements the Model Context Protocol to give AI coding agents direct access to the Meshes API. Instead of your agent guessing at endpoints, it gets 31 typed tools that cover event delivery, workspace discovery, routing rules, connection mappings, and embedded sessions.

This works with any MCP-compatible client: Claude Code, Claude Desktop, Cursor, Windsurf, and others.

Installation

The MCP server is available as a standalone repository: mesheshq/meshes-mcp-server.

Quick start (recommended)

Run directly with npx:

npx -y @mesheshq/mcp-server

The published package requires Node.js 20 or later.

Run from source

git clone https://github.com/mesheshq/meshes-mcp-server.git
cd meshes-mcp-server
npm install
npm run build
npm test

Configuration

The server needs your Meshes machine key credentials to authenticate. It automatically mints short-lived JWTs for each API request, so you never need to generate tokens manually.

Create or copy your machine keys from the Meshes dashboard under Profile -> API Keys. See Authentication for the underlying auth model.

You'll need these environment variables:

export MESHES_ACCESS_KEY=your_access_key
export MESHES_SECRET_KEY=your_secret_key
export MESHES_ORG_ID=your_organization_uuid

You can also use MESHES_ORGANIZATION_ID instead of MESHES_ORG_ID. If you are pointing at a non-default environment, set MESHES_API_URL too.

* Set either MESHES_ORG_ID or MESHES_ORGANIZATION_ID.

Cursor

Security note: These config files contain your secret key. They live in your home directory (not your project repo), so they won't be accidentally committed. Never commit access keys or secret keys to version control. Publishable keys are safe to commit.

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "meshes": {
      "command": "npx",
      "args": ["-y", "@mesheshq/mcp-server"],
      "env": {
        "MESHES_ACCESS_KEY": "your_access_key",
        "MESHES_SECRET_KEY": "your_secret_key",
        "MESHES_ORG_ID": "your_organization_uuid"
      }
    }
  }
}

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "meshes": {
      "command": "npx",
      "args": ["-y", "@mesheshq/mcp-server"],
      "env": {
        "MESHES_ACCESS_KEY": "your_access_key",
        "MESHES_SECRET_KEY": "your_secret_key",
        "MESHES_ORG_ID": "your_organization_uuid"
      }
    }
  }
}

Claude Code

claude mcp add meshes \
  -e MESHES_ACCESS_KEY=your_access_key \
  -e MESHES_SECRET_KEY=your_secret_key \
  -e MESHES_ORG_ID=your_organization_uuid \
  -- npx -y @mesheshq/mcp-server

Windsurf

Add to your Windsurf MCP configuration:

{
  "mcpServers": {
    "meshes": {
      "command": "npx",
      "args": ["-y", "@mesheshq/mcp-server"],
      "env": {
        "MESHES_ACCESS_KEY": "your_access_key",
        "MESHES_SECRET_KEY": "your_secret_key",
        "MESHES_ORG_ID": "your_organization_uuid"
      }
    }
  }
}

Available tools

The MCP server exposes 31 tools organized by resource type.

Workspaces

Connections

Rules

Events

Integrations

Sessions

Example workflows

"Set up a signup event that goes to HubSpot"

The agent will:

1. Call meshes_list_workspaces to find the right workspace
2. Call meshes_list_connections to find the HubSpot connection
3. Call meshes_get_connection_actions to discover available actions (e.g., create_or_update_contact)
4. Call meshes_create_rule to bind user.signup → HubSpot → create_or_update_contact

"Why didn't my payment.failed event reach Salesforce?"

The agent will:

1. Call meshes_get_workspace_events with event=payment.failed and status=failed
2. Call meshes_get_event to inspect rule_events for error details
3. Call meshes_get_event_payload to verify the payload was correct
4. Call meshes_retry_event_rule after you fix the underlying issue

"Emit a test event to verify my setup"

The agent will call meshes_emit_event with a test payload and confirm the event was accepted.

"Create an embedded session for a customer workspace"

The agent will:

1. Call meshes_list_workspaces to find the target workspace
2. Call meshes_create_session to mint a session for that workspace
3. Call meshes_list_sessions to confirm the active session inventory
4. Call meshes_refresh_session or meshes_revoke_session later as needed

Testing

You can test the MCP server locally with the MCP Inspector:

npx @modelcontextprotocol/inspector npx -y @mesheshq/mcp-server

Also available

• Cursor Rules: For editors that support project-level rules files — teaches the agent the Meshes API without needing MCP.