Integrations

Integration catalog

The integration catalog is the project-specific list of providers Mobius can use for actions, event triggers, reference pickers, and agent model credentials.

The catalog is runtime data, not a hand-maintained list. Mobius builds it from the provider registry, the action registry, the event registry, and the project's connection state.

provider registry
  -> provider metadata, auth kind, connect mode
action registry
  -> action names, schemas, readiness, usage
event registry
  -> provider event names and payload schemas
project integrations
  -> connection readiness and credential source

Read the live catalog before assuming a provider is ready. A deployment can enable or hide a provider, and a project can use either Mobius-managed platform credentials or its own connected credentials.

Provider types

Type	How it works	Use when
Connected provider	The project stores OAuth tokens, an API key, an app install, a bot token, or service credentials.	You need provider actions or events to run with your account.
Built-in provider	Mobius supplies the credential and marks the provider `ready` without a project-local row.	The provider is read-only or platform-funded and your own quota is not required.
Action-only provider	Actions exist, but the provider does not implement the managed connect flow yet.	Create an integration row directly until the provider gets a first-class connect screen.
Model provider	The integration stores a model API key for agents, not an action catalog.	You want agents to use your model account instead of the default model route.
MCP server	The integration points to a remote Model Context Protocol (MCP) server and exposes its tools to agents.	You already operate an MCP server and want its tools available inside Mobius.

When in doubt, use the provider catalog in the app. It shows the exact readiness and credential source for the current project.

Current providers

Provider	Provider ID	Auth kind	Actions	Events
Anthropic	`anthropic`	`api_key`	No	No
Apollo.io	`apollo`	`api_key`	Yes	No
Discord	`discord`	`api_key`	Yes	No
Firecrawl	`firecrawl`	`api_key`	Yes	No
Gmail	`gmail`	`oauth2_user`	Yes	Yes
GitHub	`github`	`github_app_install`	Yes	Yes
Google Gemini	`gemini`	`api_key`	No	No
Google Places	`google-places`	`api_key`	Yes	No
Google Sheets	`google_sheets`	`oauth2_user`	Yes	No
Jira	`jira`	`api_key`	Yes	Yes
Linear	`linear`	`api_key`	Yes	Yes
MCP server	`mcp`	`api_key`	Dynamic	No
Notion	`notion`	`api_key`	Yes	Yes
OpenAI	`openai`	`api_key`	No	No
Polymarket	`polymarket`	`none`	Yes	No
ScrapeCreators	`scrapecreators`	`api_key`	Yes	No
SendGrid	`sendgrid`	`api_key`	Yes	No
Slack	`slack`	`oauth2_user`	Yes	Yes
Telegram	`telegram`	`api_key`	Yes	Yes
Twilio SMS	`twilio`	`api_key`	Yes	No
X	`x`	`api_key`	Yes	No
xAI Grok	`xai`	`api_key`	No	No

Some providers appear only when the deployment has the backing service configured. The catalog endpoint is the final source of truth for the project you are using.

Inspect the catalog

From the app

Open Govern > Integrations to see provider readiness, connection state, available actions, source events, webhook endpoints, and recent provider events.

Open Library > Actions when you need input schemas, output schemas, action annotations, or direct invocation.

From the CLI

The mobius CLI can inspect the action and event catalogs:

mobius catalog list-actions --project platform
mobius catalog get-action slack.message.post --project platform
mobius catalog list-events --project platform

The CLI does not connect integrations yet. Use the app or HTTP API for connection setup.

From the API

Use the provider catalog to read the project-specific provider list:

curl "$MOBIUS_API_URL/v1/projects/platform/integrations/providers" \
  -H "Authorization: Bearer $MOBIUS_API_KEY"

Use the action and event catalogs when a loop authoring surface needs the exact names and schemas:

curl "$MOBIUS_API_URL/v1/projects/platform/catalog/actions" \
  -H "Authorization: Bearer $MOBIUS_API_KEY"
 
curl "$MOBIUS_API_URL/v1/projects/platform/catalog/events" \
  -H "Authorization: Bearer $MOBIUS_API_KEY"

Connect a provider

Most providers use the generic connect endpoint:

curl -X POST \
  "$MOBIUS_API_URL/v1/projects/platform/integrations/providers/<provider>/connect" \
  -H "Authorization: Bearer $MOBIUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"default"}'

Redirect providers return a redirect_url; inline providers return an integration row. Provider pages list the body shape and endpoint to use.

Action-only providers use POST /v1/projects/{project}/integrations until they have a managed connect endpoint.

Actions and events

Provider actions run inside Mobius and use the resolved credential source for the project. A ready project-owned integration wins over a platform credential. If an action posts, deletes, merges, sends, or mutates upstream state, retries can repeat that side effect. Use idempotency fields where the provider supports them, or add an interaction before irreversible steps.

Provider events enter Mobius as integration events, then become source events that event triggers and wait_for_event steps can match. Use exact event names for narrow loops. Use a trailing wildcard only when every event under a prefix should start or resume the run.

triggers:
  - kind: event
    config:
      event_type: github.pull_request.opened

Use provider credentials from integrations.
Call provider actions from steps.
Match provider events with triggers.
Check wire-format names in the event catalog.