The AI workspace that's connected to your tools and handles the bills.

179 integrations. 1,784 actions.Browse the catalog
A sentence in. A system out. The Composer is the AI builder inside ModuleX. It turns a description into a workflow graph you can open and edit node by node.
01
Describe
Write the process the way you would brief a teammate. When a detail is missing, the Composer asks before it builds.



02
Watch it build
It wires the graph and lists every change it applied. Open any node, adjust the logic, swap a tool.



03
Publish
One click publishes a version and makes it live. Run it from chat, call it from the API, or put it on a schedule.



A real canvas, not a black box. Every workflow is an editable graph of typed nodes. Inspect what the Composer built, branch it on a condition, and point a Knowledge node at your own documents so answers come from your files, not from model memory.
- Open any node to see its exact tool call, inputs, and outputs.
- Knowledge nodes retrieve from your uploaded documents at run time.
- Every publish snapshots a version; the previous one is one click away.



Your team runs it. You stay in control. Credentials are stored once for the whole organization, so teammates run workflows without ever seeing a key. Every action lands in the logs with the actor who caused it.
- Org credentials: OAuth grants and API keys stored once, masked everywhere.
- A write action from chat waits for an explicit approve before it runs.
- Logs record the category, operation, actor, and time of every change.

Your keys or ours. Your data either way. Start on ModuleX-managed models with zero setup, or connect your own keys. Credits are only consumed when something runs on our keys; anything on your keys costs you nothing here.
- Keys are stored once for the organization and masked everywhere they appear.
- The model sees tool results, never the credential behind them.
- Bring your own keys per integration, not just per model provider.

Your workflows, tools in any MCP client. Publish your organization as an MCP server. Deployed workflows, Files, and Knowledge become tools Claude Code, Cursor, or Codex can call with one key, run on your credentials, metered in credits.




