whoamiLABSCO SUMMARY
An aggregator: one credential and one endpoint instead of a separate server, key and config block per SaaS app.
The trade is the usual one for a hub — you authorize Maton rather than each vendor directly, and in exchange the number of integrations you maintain stops growing with the number of apps. The agent toolkits matter if you are building rather than chatting: the same tool set shows up natively in LangChain, CrewAI, the Vercel AI SDK and the OpenAI Agents SDK.
What it is
Maton's hosted server at https://mcp.maton.ai, which fronts a unified API across 150+ business apps, plus the plugins and agent-framework toolkits that wire it up for you.
What you get
- A single endpoint covering more than 150 connected apps, so one integration replaces a per-app server for each of them
- Two ways in: OAuth, completed in the browser on first use, or an API key sent as a bearer token
- A local proxy for clients that would rather run something on the machine than talk to a remote endpoint
- Ready-made plugins for Claude Code, Cursor, Codex and OpenClaw that register the server for you
- Toolkits that expose the same tools inside agent frameworks: LangChain, the Vercel AI SDK, OpenAI and MCP in TypeScript; OpenAI Agents SDK, LangChain, CrewAI and Strands in Python
- Tool discovery at the endpoint, so the tool list each framework sees reflects what Maton currently supports
Requirements
A Maton account. Point a client at https://mcp.maton.ai over streamable HTTP and finish OAuth in the browser, or run the local proxy from npm with npx -y @maton/mcp --api-key=<YOUR_MATON_API_KEY>. Each connected app also needs to be authorized on the Maton side before its tools do anything.
Setup effort
One command plus a key — npx -y @maton/mcp --api-key=<YOUR_MATON_API_KEY>, then supply credentials
USE CASES
01
Connecting an assistant to the SaaS apps your team runs on
Register one endpoint, authorize the apps you want, and skip the per-app server setup.
02
Automating work that crosses apps
Move something from one connected app to another in a single conversation, through the unified API.
03
Building an agent on a framework rather than in a chat client
Install the TypeScript or Python toolkit and get the same tools in your framework's native shape.
04
Keeping credentials out of a machine you do not control
Use the OAuth flow at the remote endpoint instead of putting an API key in a config file.
10 tools
Listed in project docs. Your client may show a different list.
create_connectiondelete_connectionlist_connectionsget_connectionsearch_appssearch_actionsget_actionrun_actionapiBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
MATON_API_KEY in your environment
INSTALLATION
Connect your client
Server setup
npx
TERMINAL
npx -y @maton/mcp --api-key=<YOUR_MATON_API_KEY>Hosted endpoint
ENDPOINT URL
https://mcp.maton.aiAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Claude Code, Cursor
JSON
{
"mcpServers": {
"maton": {
"type": "http",
"url": "https://mcp.maton.ai"
}
}
}Codex
CODEX · TERMINAL
codex plugin marketplace add maton-ai/agent-toolkitOpenClaw
OPENCLAW · JSON
{
"mcp": {
"servers": {
"maton": {
"url": "https://mcp.maton.ai",
"transport": "streamable-http",
"auth": "oauth"
}
}
}
}
