Put an external MCP server to work
A tool that was not in the catalog, usable in the same place as the 175+ that are. Built for teams with internal tools that no catalog will ever cover.
Slack
Notion
4 steps2 integrationsRuns on demand
Your internal tools will never be in a catalog. What it costs while the work is still done by hand.
- 01An internal service matters but is not a mainstream product.
- 02Exposing it usually means writing and maintaining a connector.
- 03The team already runs an MCP server, outside the tools everyone uses.
- Add serverinventory-mcp · authorized
- Discover tools11 tools · no connector code
- Run in graphlist_channels · #ops
- File to Notioncreate_page · result filed
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Add the external MCP server as a credential.ModuleX
- 02Its tools are discovered automatically, with no connector code to write.ModuleX
- 03Use those tools in a workflow beside your existing integrations.Slack
- 04File the result where your team already works.Notion
The workflow is an editable graph. Reading runs freely; file the result where your team already works waits for your opt-in approval until you loosen it. The graph is the receipt.
Your own tools, connected. Paste this into ModuleX chat, or hit Use this workflow.
put an external MCP server to work: add the external MCP server as a credential; its tools are discovered automatically, with no connector code to write; use those tools in a workflow beside your existing integrations; file the result where your team already works. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
Put an external MCP server to work. A tool that was not in the catalog, usable in the same place as the 175+ that are.
- slack · list_channels
- notion · create_page
A tool that was not in the catalog, usable in the same place as the 175+ that are.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
Check database health without opening the dashboardA short, regular status that tells you when something moved out of range, and stays quiet otherwise. Built for a small team with no dedicated operations engineer.
Start the day knowing what moved in the repoA short brief showing what shipped and what is waiting on a person. Built for an engineering manager reconstructing yesterday from notifications.- Get a first-pass review onto the pull requestA first-pass review on the pull request while the author still has the change in their head. Built for a team where pull requests wait a day for anyone to look at them.
About this use case.
No: the other way round. ModuleX is the MCP client: it connects to external MCP servers and calls the tools they expose.