The Model Context Protocol server is hosted at https://mcp.maton.ai. It exposes a small set of tools for discovering apps and pre-built actions, running them, and calling any external API through the gateway.
Authentication
The server supports two authentication methods:
- OAuth: complete the OAuth flow in the browser on first use.
- API key: pass your Maton API key in the
Authorization: Bearerheader.
Remote
Point any MCP client that supports remote HTTP servers at https://mcp.maton.ai. On first use, you'll complete the OAuth flow in your browser.
{
"mcpServers": {
"maton": {
"type": "http",
"url": "https://mcp.maton.ai"
}
}
}Local
Run the Maton MCP server locally with npx. The local CLI is a thin proxy: it speaks stdio to your MCP client and forwards requests to https://mcp.maton.ai with your API key in the authorization header.
# Basic usage
npx -y @maton/mcp --api-key=YOUR_MATON_API_KEY
# Route all calls through a specific connection
npx -y @maton/mcp --api-key=YOUR_MATON_API_KEY --connection=CONNECTION_IDYou can set the MATON_API_KEY environment variable instead of passing --api-key.
Available tools
The Maton MCP server exposes a compact set of tools to discover and run automations:
| Tool | Description |
|---|---|
whoami | Show the authenticated Maton user. |
search_apps | Discover the 150+ supported apps with grep-style search. |
search_actions | Find pre-built actions across apps, scoped by app or resource. |
get_action | Retrieve an action's full input/output schema before running it. |
run_action | Run a pre-built action with the given arguments. |
api | Call any external API endpoint through the Maton gateway. |
create_connection | Create a new app connection (returns an authorize URL). |
get_connection | Show details for an app connection by ID. |
list_connections | List app connections, filterable by app, status, and method. |
delete_connection | Delete an app connection by ID. |
Discovery workflow
The tools are designed to be used together. A typical flow:
Find the app
Use search_apps to confirm the target app is supported and get its slug (e.g. slack, google-mail).
Find an action
Use search_actions (scoped by app and optionally resource) to find a pre-built action. Prefer pre-built actions over the raw api tool.
Inspect the schema
Call get_action to learn the required arguments and output shape.
Run it
Call run_action with the arguments. If no pre-built action fits, fall back to the generic api tool to call the native endpoint directly.