Skip to main content
The catalog is the directory of everything ModuleX can connect to. Each entry is an integration — a connector to an outside service such as Slack, GitHub, or Salesforce — and each integration exposes one or more tools, the individual actions your workflows and the Assistant can call. ModuleX ships 175 integrations today. Browse them by category, search for the service you need, then open its page to see what it can do before you connect it.
New to integrations? Start with the integrations overview for the bigger picture of how connectors, tools, and credentials fit together. This page is for finding a specific integration once you know you want one.

​
What counts as an integration

An integration packages everything ModuleX needs to talk to one service:

The connection

How ModuleX signs in to the service on your behalf — an API key, an OAuth connection, or a managed key. You set this up once as a credential.

The tools

The individual actions the integration can perform — “send a message”, “create an issue”, “search records”. One integration usually exposes several tools.

The catalog page

A generated reference page that lists every tool, its inputs, how it authenticates, and any limits — so you know what you are connecting before you connect it.

The logo and details

The service’s display name, logo, and link to its own site, so the catalog stays easy to scan.
Once an integration is connected, its tools become available to your workflows through the Tool node and to the Assistant when it works through a task.

​
Browse by category

Each integration is tagged with one or more categories so you can scan the catalog by the kind of work you do rather than by remembering exact product names. The largest groups are:

Productivity & collaboration

Team and document tools — messaging, calendars, docs, and project trackers. The largest group in the catalog.

Developer tools & infrastructure

Source control, cloud platforms, observability, and deployment services.

Marketing

Email, campaigns, analytics, and audience tools.

CRM & sales

Customer records, pipelines, and outreach platforms.

Automation

Connectors that move data between other services and trigger downstream work.

Everything else

Payments, data warehouses, AI services, support desks, and many more specialised connectors.
Categories are a browsing aid, not a fixed taxonomy. Each integration sets its own categories, so the exact labels and counts shift as the catalog grows. Use search when you already know the service you want.
🎬 MEDIA PLACEHOLDER · MX-MEDIA-4040 · [SCREENSHOT] [SCREENSHOT_DESCRIPTION]: The integration catalog in the ModuleX app, showing the category sidebar and a grid of integration cards. [SCREENSHOT_DETAILS]: Capture the catalog/browse view in the live app with the category filter visible on the left and integration logo cards on the right. Show the search box at the top. Light theme, 16:9, no personal data.

​
Find an integration

1

Open the catalog

In the app, go to the integrations area and open Browse. You’ll see every available integration as a card with its logo and a short description.
2

Search or filter

Type the service name in the search box, or pick a category to narrow the grid. Search matches the display name and description, so “email”, “calendar”, or “database” all surface relevant results.
3

Open the integration's page

Click a card to open its catalog page. Review the tools it exposes and how it authenticates before you connect it.
4

Connect it

Add a credential for the integration, then use its tools from a workflow or the Assistant. See connect an integration for the full walkthrough.

​
What’s on a tool’s catalog page

Every integration has its own page, generated directly from the integration’s manifest so it always matches what the service actually exposes. When you open one, you’ll find:
The service’s display name, logo, a short description of what it does, and a link to the service’s own website.
Every tool the integration exposes, each with a plain description, its inputs (name, type, and whether each is required), and the shape of what it returns. This is the menu your workflows and the Assistant choose from.
How the integration signs in — an API key, an OAuth connection, or a ModuleX-managed key — and any setup steps or values you need to provide. See authentication & credentials for how each method works.
Service-specific rate limits, size caps, and other constraints to keep in mind, drawn from the integration’s own notes.
Who maintains the integration. Most are maintained by ModuleX.
Catalog pages are generated from each integration’s manifest, not written by hand. If a page looks out of date, the fix is to update the source integration and regenerate — the page will follow.

​
Browse the catalog from code

You can also list the catalog programmatically — useful for building your own picker or syncing the available integrations into another tool. The browse endpoint returns the integrations available to your organization. GET /integrations/browse is restricted to organization owners and admins, so the API key you use must belong to an owner or admin of the organization. Every request authenticates with Authorization: Bearer mx_live_… plus your X-Organization-ID. See authentication for how to get and use these. 
curl https://api.modulex.dev/integrations/browse \
  -H "Authorization: Bearer mx_live_your_api_key" \
  -H "X-Organization-ID: org_your_org_id"
Browsing the catalog returns the integrations you can connect — it does not connect anything or move data. To work with credentials, see managing credentials.

​
Don’t see what you need

Connect a custom MCP server

Point ModuleX at an external Model Context Protocol server to use its tools alongside the built-in catalog.

Build your own integration

Author a new integration and expose its tools to ModuleX.
Connecting a custom MCP server is a separate path from the built-in catalog above — it is not one of the 175 catalog integrations. Use it when the service you need isn’t listed.

​
Next steps

Integrations overview

How connectors, tools, and credentials work together.

Connect an integration

A step-by-step walkthrough from connecting to calling a tool.

Authentication & credentials

The connection methods every integration uses.