Apideck MCP Server
One MCP server for 200+ SaaS apps across seven unified APIs, with token-lean tool discovery.
- Skill Road
- Apideck MCP Server
Categories
Description
The Apideck MCP Server is the official Model Context Protocol server from unified-API provider Apideck. According to the official product page at apideck.com/mcp-server and the technical documentation at developers.apideck.com/mcp, it connects an MCP-capable AI client not to a single third-party system but to seven unified API categories — accounting, CRM, HRIS, ATS, file storage, ecommerce, and issue tracking — and through them to more than 200 concrete SaaS applications such as accounting, HR, or ticketing systems. Instead of running a separate MCP server for every individual third-party app, an agent talks to a single endpoint while Apideck handles the actual translation to each underlying third-party API. The repository lives at github.com/apideck-libraries/mcp, is MIT licensed, and is maintained directly by the Apideck team rather than an independent community project. For Skill Road this is a distinct catalog entry because it solves a different problem than the single-integration servers already listed, such as HubSpot- or Zendesk-adjacent servers: it bundles many back-office systems behind one normalized interface instead of deeply covering a single application.
Unified APIs and tool coverage
According to the vendor, the server exposes more than 360 tools in total, spread across the seven categories: roughly 170 for accounting, 50 for CRM, 30 for HRIS, 30 for file storage, 25 for issue tracking, 20 for ecommerce, and 15 for ATS (applicant tracking). Each category normalizes the data models of different third-party providers into one shared schema, so an agent can, for example, query invoices, contacts, or job applications in the same structure regardless of which accounting, CRM, or applicant-tracking system is actually connected. The server also ships workflow tools that, per the documentation, chain several individual calls into one operation — for example a month-end close in accounting — plus native support for binary content such as images or audio files as MCP blocks.
Operating modes: Dynamic, Static, and Code
To avoid overloading a context window with hundreds of tool definitions, the README describes three operating modes. The default "Dynamic" mode initially exposes only four meta-tools and loads further tool definitions progressively as a specific category is actually needed — around 1,300 initial tokens per the vendor. "Static" mode loads all roughly 360 tools upfront (35,000 to 55,000 tokens) and suits strongly API-focused agents. "Code" mode narrows the surface to two tools (apideck_search and apideck_run) for programmatic control via JavaScript and needs only around 600 initial tokens per the vendor. This staged disclosure is the central technical difference from a classic single integration and the main reason Apideck advertises up to a 63x context saving compared with loading every tool individually.
Authentication and Vault
Access runs through an Apideck API key and an app ID passed as headers to the server; an optional consumer ID can be set per call to distinguish between multiple connected end customers. The connection to the actual third-party systems — a specific accounting or HR tool, for example — goes through Apideck's "Vault" component with managed OAuth: a user authorizes an integration once, and Apideck then handles token storage and refresh. For production-grade permission separation, the documentation describes an additional scope filter for read, write, and destructive operations, so an agent can, for instance, be limited to read-only access.
Installation and setup
The fastest path is Apideck's own hosted remote endpoint, https://mcp.apideck.dev/mcp, which plugs directly into clients such as Claude Desktop, Cursor, Windsurf, or Codex. Alternatively, npx -y @apideck/mcp start runs the server locally via the @apideck/mcp npm package; for Claude Desktop, the repository also offers a prebuilt .mcpb bundle in its GitHub releases that can be dragged in directly. Either way, an Apideck account plus an API key and app ID from the Apideck dashboard are required.
Security, data path, and fit
Tool calls leave the local or hosted MCP server, pass through the Apideck platform, and reach the connected third-party systems from there; responses travel the same path back to the MCP client. Because several of the covered categories allow write and destructive operations — creating invoices or deleting files, for example — scope filtering should be set as narrowly as possible, and an API key should never be placed in prompts or repositories. Values coming back from connected third-party systems should generally be treated as data rather than trusted instructions, since they could in principle carry a prompt injection. The connector code itself is MIT licensed and open source; the underlying Apideck platform is a paid product per its official pricing page (plans "Launch," "Scale," and "Enterprise" with a 30-day free trial requiring no credit card), so this entry does not label it as free and points to the official pricing page instead of quoting amounts.
Who benefits from the Apideck MCP Server?
The server is particularly useful for teams that want to connect an AI agent to several back-office systems at once — accounting, HR, and file storage inside a single SaaS product serving multiple end customers — without maintaining a separate integration for every individual third-party app. It is less suited for teams that only need to connect a single application in depth; a specialized single-purpose integration from the catalog often fits that case better.
Requirements
An Apideck account with an API key and app ID; the local variant additionally needs Node.js/npm, the hosted variant just an MCP-capable client.
Installation instructions
The Apideck MCP Server connects an AI client, through seven unified APIs, to more than 200 SaaS applications across accounting, CRM, HRIS, ATS, file storage, ecommerce, and issue tracking. Because several of these categories allow write and destructive operations, a deliberate setup pays off before connecting production third-party accounts.
Step 1: Create credentials in the Apideck dashboard
An Apideck account provides an API key and an app ID; both are required as headers on every call to the MCP server. Teams serving multiple end customers through their own application can additionally set a consumer ID per call to attribute requests to a specific customer.
Step 2: Choose between the hosted endpoint and a local server
For a quick start, it's enough to configure the hosted endpoint https://mcp.apideck.dev/mcp directly in the MCP client. To run the server yourself instead, start it locally with npx -y @apideck/mcp start; a prebuilt bundle for Claude Desktop is also available in the repository's GitHub releases.
npx -y @apideck/mcp start
Pick the right operating mode
For most agents, the default "Dynamic" mode fits best, since it initially loads only a few meta-tools and pulls in more only when actually needed. Only agents working very narrowly and exclusively with the Apideck API benefit from "Static" mode with all roughly 360 tools loaded upfront; for lean, programmatic control, "Code" mode is the better fit instead.
Authorize third-party integrations and scope access narrowly
Each connected third-party application is authorized once via OAuth through Apideck Vault; Apideck then handles token storage and refresh. Set the available scope filter as narrowly as possible, for example read-only access for exploratory tasks, and enable write or destructive operations only once a concrete, reviewed use case requires it. The API key and app ID belong only in protected environment variables or the MCP client's secure configuration, never in prompts or repositories.
npx -y @apideck/mcp start
Authentication
Apideck API key and app ID as headers (optional consumer ID); connections to third-party systems run through managed OAuth in Apideck Vault.
Required access permissions
Vendor-described scope filtering for read, write, and destructive operations; permissions in each third-party system additionally depend on the OAuth authorization granted there.
Transmitted or stored data
Tool calls pass through the Apideck platform to the connected third-party systems; results return to the MCP client and can enter model context or logging there.
Security risks
Overly broad scopes, exposed API keys, or unchecked destructive operations can expose, alter, or delete data in connected third-party systems.
License and costs
- License
- MIT
- Cost
- paid
The connector code is MIT licensed and free. The underlying Apideck platform is a paid product (Launch, Scale, Enterprise plans) with a 30-day free trial requiring no credit card; see apideck.com/pricing for current terms.
Alternatives
Not recorded yet.
At a glance
- Provider
- Apideck
- Status
- Official server
- Deployment
- Local and remote
- Current version
- 0.19.0
- GitHub stars
- 17
- Last reviewed
- 18.09.2026
Repository and documentation
Categories
Supported clients
Related guides
Guides and background related to this entry.