withoneai/mcp

Website
 · 
Docs
 · 
Dashboard
 · 
Changelog
 · 
X
 · 
LinkedIn
Connect your AI agents to 700+ apps through a single MCP server. Find the actions a task needs with their documentation, and execute API calls across platforms, without having to manage OAuth tokens or API keys.
That's it. The One CLI will prompt you for your API key (get one from the One dashboard) and configure the MCP server for your environment: Claude Desktop, Cursor, Claude Code, Windsurf, or any MCP-compatible agent.
Capabilities
- **700+ platforms.** Gmail, Slack, Shopify, HubSpot, Stripe, Linear, QuickBooks, and more.
- **Natural language execution.** "read my last gmail email", "send a message to #general on Slack"
- **Code generation.** "build a form to send emails using Gmail", "create a dashboard that lists my Linear projects"
- **No tool bloat.** Only 3 tools exposed regardless of how many platforms or actions you connect. One call finds every action a task needs, across platforms, with its documentation, so your agent's context window stays clean.
- **Fine-grained access control.** Restrict which actions, connections, and permission levels (read, write, admin) your agent has access to.
- **Secure by default.** All requests proxied through One, secrets automatically redacted, no platform API keys to manage.
Examples
**Execute actions directly:**
> "Get my last 5 emails from Gmail"
> "Send a Slack message to #general: 'Meeting in 10 minutes'"
> "Get all products from my Shopify store"
**Generate integration code:**
> "Create a React form component that sends emails using Gmail"
> "Build a dashboard that displays Linear users and their assigned projects with filtering"
> "Create a paginatable table that fetches and displays QuickBooks invoices with search and sort"
Tools
The server exposes three MCP tools:
| Tool | Description |
|------|-------------|
| list_one_integrations | List available platforms and active connections, each with the access it confers (full, methods, or specific actions) |
| find_one_actions | Find the action for every operation a task needs, across platforms, with its documentation, in one call; load fetches more of a document or an alternative's |
| execute_one_action | Execute an API action on a connected platform |
Finding actions
find_one_actions takes one requests entry per operation, each a kebab-case platform and a short intent naming the operation alone ("send a message to a channel", not the message). A task describes the whole job in general terms, and an ai_model names the model asking; agents are asked to send both with every find, since the task helps tell similar actions apart. For each intent, One's decision model picks the action to use; the answer documents it, sets apart a substitute when the model was unsure, and lists a few alternatives. Large documents come back as a digest; call find_one_actions again with load: [{ action_id, section }] for a section it left out, full: true for the whole document, or toc: true for its table of contents. ONE_ACTION_IDS, ONE_PERMISSIONS and ONE_CONNECTION_KEYS apply to every answer: an action they refuse is never offered, and when they refuse the model's pick, the next allowed candidate takes its place.
Upgrading from 1.x: search_one_platform_actions and get_one_action_knowledge are removed. find_one_actions replaces both.
Remote MCP Server
Prefer not to run anything locally? One hosts a remote MCP server at **https://mcp.withone.ai/mcp**. Point any MCP client that supports remote (HTTP) servers at that URL and authenticate with One via OAuth. There's no npm install and no ONE_SECRET to manage. You approve access in One's consent screen, where you can scope exactly which connections, actions, and permission levels the agent gets. Those choices are surfaced back to the agent through each connection's access field, so it knows what it can run without searching.