Skip to content
Cursor· the AI code editor

Your ModuleX workflows, one tab away. Publish once; Cursor’s agent calls them while you code.

api.modulex.dev/mcp/servestreamable HTTPmx_mcp_key via X-API-Key

Publish your MCP serverView the MCP docs
cursor · agent · modulex mcpconnected

Triage this morning’s support tickets and post the urgent ones.

support_ticket_triage · run started · credits

Done. 14 tickets triaged; 2 urgent ones are in #support.

Message Cursor…

Four steps, one key. Publish once in ModuleX, paste one block into Cursor, and the tools are live.

  1. 01Publish a serverIn Settings › ModuleX MCP, choose what it exposes: workflows, Files, Knowledge. Paid plan; owner or admin.
  2. 02Copy the keyOne mx_mcp_ key, shown once. Rotation issues a replacement.
  3. 03Add the configPoint the client at your private endpoint. The exact snippet is below.
  4. 04Ask from the clientTools appear on the next list. Calls are metered in credits; listing is free.
cursor · mcp config · json
{
  "mcpServers": {
    "modulex": {
      "url": "https://api.modulex.dev/mcp/serve/{server_id}",
      "headers": { "X-API-Key": "mx_mcp_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" }
    }
  }
}

Replace the endpoint placeholder with your server URL from the Overview tab, and do not add an X-Organization-ID header; the MCP endpoint does not use one. Full client guide in the docs

Workflows, Files, Knowledge. That is what Cursor sees; each with a name, description, and input schema.

Workflow toolsEvery deployed workflow you publish becomes a tool with its name, description, and input schema.
FilesList, read, write, and append organization Files.
KnowledgeList your Knowledge bases and run retrieval over them.

The 179-integration catalog is not published directly: Cursor calls one tool, the workflow does the cross-tool work. Browse the integrations

ModuleX MCP at a glance. Straight from the docs.

Endpointhttps://api.modulex.dev/mcp/serve/{server_id}
TransportStreamable HTTP (stateless JSON-RPC over POST)
AuthenticationX-API-Key (or Authorization: Bearer)
Key prefixmx_mcp_
Publish fromSettings › ModuleX MCP
RequiresPaid plan; owner or admin publishes
Servers per organization20
Keys per server / org10 / 50
Published tools per server100
Concurrent tool calls10
Key lifetimeup to 365 days
BillingTool calls consume credits like in-app runs; listing tools is free

Workflows teams expose first. Build one from a sentence, deploy it, and it becomes a tool Cursor can call.

Daily Inbox DigestEvery morning your team gets a clean digest of overnight email in Notion, without opening the inbox. A ModuleX agent reads the unread threads, summarizes them, and files a dated page in your Notion database.5 steps · weekdays 8amInbound Lead RoutingNew leads get scored the moment they arrive and the hot ones land in #sales while your reps are still at their desks. A ModuleX agent rates buying intent, posts the strong leads to Slack, and files every contact in HubSpot.5 steps · on every new leadFailed Payment Follow-upA failed invoice stops being a silent number on a dashboard and becomes a tracked case your team can act on. When Stripe reports a payment failure, a ModuleX agent pulls the details, re-sends the invoice, and posts the case to Slack.6 steps · on payment failure

Also connects toClaude CodeCodexHermesOpenClaw

ModuleX MCP and Cursor.

  • Not directly. ModuleX MCP publishes your deployed workflows, Files, and Knowledge as tools, not the third-party integration catalog. The workflows themselves are what act across the tools your organization has connected.

Cursor writes code. ModuleX runs the rest.

Publish your MCP serverRead the MCP docs

Workflows to build firstThe tools they act across

Cursor is Anysphere’s product. ModuleX is an independent MCP server and is not affiliated with or endorsed by Anysphere.