Skip to main content
ModuleX MCP turns your organization into a Model Context Protocol (MCP) server. You publish a private endpoint that external AI clients — Claude Code, Cursor, Codex, or any MCP-capable app — connect to, and they can then call your live workflows, read and write your organization’s Files, and search your Knowledge bases, all as MCP tools. You set it up entirely in the app: create a logical MCP server, choose which tools it exposes, and generate a key. The client connects over HTTP with that key and sees your tools alongside its own.

Workflows

Each deployed workflow becomes a callable tool. The client runs it with the workflow’s published inputs and gets the result back.

Files

List, read, write, and append your organization’s Files from the client, subject to your existing quotas.

Knowledge

List your Knowledge bases and run retrieval over them, so the client can ground its answers in your data.

Which MCP page do you want?

ModuleX touches MCP in two opposite directions. They are separate features — do not confuse them.

ModuleX as the MCP server

This page. ModuleX publishes an MCP endpoint; an external client connects to ModuleX and calls your workflows, Files, and Knowledge. The client is the consumer; ModuleX provides the tools.

ModuleX as the MCP client

The reverse: you connect an external MCP server to ModuleX as a credential, and ModuleX calls its tools from a Tool node. ModuleX is the consumer. See Custom MCP servers.
A quick test: if you want Claude Code or Cursor to use ModuleX, you are on the right page. If you want a ModuleX workflow to use some other tool server, you want Custom MCP servers.

How it works

1

Create a server in the app

In Settings → ModuleX MCP, create a private MCP server for your organization. See Publish an MCP server.
2

Choose what it exposes

Select which built-in tools (Files, Knowledge) and which deployed workflows the server publishes.
3

Generate a key

Create a server key. ModuleX shows the key once — copy it then. Clients send it on every request.
4

Connect a client

Paste the endpoint URL and key into your MCP client’s config. Your tools appear in the client. See Connect an MCP client.

What it exposes

A published server exposes tools in two groups:
  • Built-in tools — a fixed set for your organization’s Files and Knowledge: list workflows, list/read/write/append Files, and list/search Knowledge. Enable the ones you want per server.
  • Workflow tools — each deployed workflow you publish, exposed with its published name, description, and input schema. Calling the tool runs the workflow.
The Connect an MCP client page lists every built-in tool and explains how workflow tools are named and called.
ModuleX MCP publishes your workflows, Files, and Knowledge — not the third-party integration catalog. To give a client access to a catalog action (Slack, GitHub, and so on), wrap it in a workflow and publish that workflow.

Requirements

A paid plan

Publishing requires an organization on a paid plan. See Plans & pricing.

Owner or admin

Only an organization owner or admin can create and manage MCP servers and keys.

A private endpoint

Each server is private to your organization and reached only with an active key.

Billing

Connecting a client and listing tools are free. Calling a tool that runs a workflow or searches Knowledge consumes credits, metered exactly as if you ran it in the app — the client is just another way to trigger the same managed usage. If your organization is out of credits or its plan does not permit the usage, the tool call comes back as an error result rather than running. See Usage gating & limits.

Next steps

Publish an MCP server

Create a server in the app, choose its tools, and generate a key.

Connect an MCP client

Endpoint, transport, auth, and ready-to-paste configs for Claude Code, Cursor, Codex, and generic HTTP clients.

Custom MCP servers

The reverse direction: use an external MCP server’s tools inside a ModuleX workflow.

Deploy a workflow

A workflow must be deployed before it can be published as an MCP tool.