Skip to main content
You publish an MCP server from the app, not from code. A server is a named, private endpoint for your organization that exposes a chosen set of tools; a key authenticates a client that connects to it. This page covers creating a server, choosing its tools, and managing its keys.
Prerequisites. Publishing requires an organization on a paid plan, and only an owner or admin can create or manage servers and keys. To publish a workflow, it must first be deployed.

​
Open ModuleX MCP

Go to Settings → ModuleX MCP. The list shows your organization’s MCP servers, each with its status, the tools it publishes, and its endpoint URL. This is where you create a new server and open an existing one to manage its tools and keys.

​
Create a server

Select New MCP server and complete the two-step wizard.
1

Basics

Name the server so you can recognize it later (for example, Support workflows or Docs assistant). The server is created as a private endpoint scoped to the current organization.
2

Setup — choose the tools

Pick what the server publishes:
  • Built-in tools — toggle the Files and Knowledge tools you want (see The published tools). Enabled tools are available to every active key on the server.
  • Workflow tools — publish specific deployed workflows, or publish your deployed workflows as a set so newly deployed ones are included automatically. Each published workflow becomes one tool, using its published name, description, and input schema.
Start from the recommended defaults, or switch to the advanced options to set the initial key’s name, expiry, and rate limit while you create the server.
3

Create and save the first key

On create, ModuleX generates the server’s first key and shows it once. Copy it before you leave the screen — see Server keys.
Only workflows that ModuleX has deployed are eligible to be published, and a workflow tool runs that deployed workflow with its published inputs. Publishing does not let a client execute arbitrary workflows by ID — it can call only the tools the server exposes.

​
Server keys

A server key is a static, server-scoped secret with the prefix mx_mcp_. A client sends it on every request to authenticate. Keys are independent of your mx_live_ API keys — an MCP key works only against its own server and carries no other API access.
A key is shown once, at creation or rotation. Copy it immediately — ModuleX does not show it again. If you lose a key, rotate it to issue a new one and invalidate the old.
From a server’s Keys tab you can:
  • Create additional keys — for example, one per client or per teammate, so you can revoke one without disrupting the others.
  • Rotate a key — issue a replacement and retire the current one. Update the client with the new key.
  • Set an expiry — keys expire after a chosen period (up to a year; a shorter default applies if you do not set one). An expired key stops working and the client must be updated with a current key.
Give each client its own key. If a key is exposed or a client is decommissioned, rotate or remove just that key and leave the rest working.

​
Manage a published server

Open a server to see four tabs: Changing a server’s published tools takes effect for new tool listings; connected clients pick up the change when they next list tools.

​
Limits

Servers and keys are bounded per organization and per server: If you reach a limit, remove an unused server or key, or narrow a server’s published tools, before adding more.

​
Billing

Creating a server, listing tools, and connecting a client do not consume credits. A tool call that runs a workflow or searches Knowledge consumes credits the same as running it in the app, and File writes count against your organization’s existing Files quotas. When a call cannot be billed — the organization is out of credits, or its plan does not permit the usage — the tool returns an error result instead of running. See Usage gating & limits.

​
Next steps

Connect an MCP client

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

Deploy a workflow

Deploy a workflow so you can publish it as an MCP tool.

ModuleX MCP overview

What ModuleX MCP is and how it differs from custom MCP servers.

Roles & permissions

Who can create and manage MCP servers and keys.