Connects an AI client to Apideck's Unified API to read and write accounting, CRM, HRIS, ATS, file storage, and ecommerce data across 200+ connectors.
Also known as apideck-libraries/mcp, @apideck/mcp
- Stars
- 21
- Tools
- 4
- Downloads, 30 days
- 2,078
- Latest version
- 0.1.13
- Last commit
- Nov 10, 2026
- License
- MIT
What is Apideck MCP?
Apideck connects an AI client to Apideck's Unified API to read and write accounting, CRM, HRIS, ATS, file storage, and ecommerce data across 200+ connectors. It exposes 4 tools, such as apideck-month-end-close-check, apideck-pay-bill, apideck-receive-customer-payment.
Summary generated from the project's README
About Apideck MCP server
Connecting AI agents to hundreds of business applications through a single integration is what this server enables. It acts as a bridge between MCP-compatible clients and the Apideck Unified API, providing access to data across accounting, CRM, HRIS, ATS, ecommerce, and file storage systems. Developers can use it locally via npx or connect to a hosted version using HTTP headers for authentication.
Users can choose between different operational modes to manage how tools are exposed to the model. The dynamic mode allows agents to discover tools progressively, which reduces the initial token load, while the static mode provides access to over 380 tools including specialized workflow tools. To get started, you will need an Apideck API key, a consumer ID, and an app ID provided by the Apideck platform.
What you can do with it
- 1Automate financial month-end tasksAn agent can perform a comprehensive check of aged creditors, debtors, and balance sheets in a single step.
- 2Streamline employee onboardingYou can instruct an AI to move a candidate from an applicant tracking system into an HRIS platform.
- 3Process vendor and customer paymentsAn AI client can look up specific invoices or bills and apply payments to them automatically.
- 4Manage multi-platform business dataDevelopers can use a single set of tools to interact with over 200 different software connectors.
Written from the project's README. Every use case is checked against a quote from it.
How to install Apideck MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Apideck MCP in Claude Code
$ claude mcp add --env 'APIDECK_API_KEY=<YOUR_APIDECK_API_KEY>' --env 'APIDECK_APP_ID=<APIDECK_APP_ID>' --env 'APIDECK_CONSUMER_ID=<APIDECK_CONSUMER_ID>' mcp -- npx -y @apideck/mcpInstall Apideck MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@apideck/mcp"
],
"env": {
"APIDECK_API_KEY": "<YOUR_APIDECK_API_KEY>",
"APIDECK_APP_ID": "<APIDECK_APP_ID>",
"APIDECK_CONSUMER_ID": "<APIDECK_CONSUMER_ID>"
}
}
}
}Install Apideck MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@apideck/mcp"
],
"env": {
"APIDECK_API_KEY": "<YOUR_APIDECK_API_KEY>",
"APIDECK_APP_ID": "<APIDECK_APP_ID>",
"APIDECK_CONSUMER_ID": "<APIDECK_CONSUMER_ID>"
}
}
}
}Install Apideck MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@apideck/mcp"],"env":{"APIDECK_API_KEY":"<YOUR_APIDECK_API_KEY>","APIDECK_APP_ID":"<APIDECK_APP_ID>","APIDECK_CONSUMER_ID":"<APIDECK_CONSUMER_ID>"}}'Install Apideck MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@apideck/mcp"
],
"env": {
"APIDECK_API_KEY": "<YOUR_APIDECK_API_KEY>",
"APIDECK_APP_ID": "<APIDECK_APP_ID>",
"APIDECK_CONSUMER_ID": "<APIDECK_CONSUMER_ID>"
}
}
}
}Install Apideck MCP in Codex
$ codex mcp add mcp --env 'APIDECK_API_KEY=<YOUR_APIDECK_API_KEY>' --env 'APIDECK_APP_ID=<APIDECK_APP_ID>' --env 'APIDECK_CONSUMER_ID=<APIDECK_CONSUMER_ID>' -- npx -y @apideck/mcpInstall Apideck MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@apideck/mcp"] [mcp_servers.mcp.env] APIDECK_API_KEY = "<YOUR_APIDECK_API_KEY>" APIDECK_APP_ID = "<APIDECK_APP_ID>" APIDECK_CONSUMER_ID = "<APIDECK_CONSUMER_ID>"
Install Apideck MCP in Gemini CLI
$ gemini mcp add -s user -e 'APIDECK_API_KEY=<YOUR_APIDECK_API_KEY>' -e 'APIDECK_APP_ID=<APIDECK_APP_ID>' -e 'APIDECK_CONSUMER_ID=<APIDECK_CONSUMER_ID>' mcp npx -- -y @apideck/mcpInstall Apideck MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@apideck/mcp"
],
"env": {
"APIDECK_API_KEY": "<YOUR_APIDECK_API_KEY>",
"APIDECK_APP_ID": "<APIDECK_APP_ID>",
"APIDECK_CONSUMER_ID": "<APIDECK_CONSUMER_ID>"
}
}
}
}Apideck MCP tools 4
Detected from the READMEapideck-month-end-close-checkapideck-pay-billapideck-receive-customer-paymentapideck-onboard-employee
| apideck-month-end-close-check | — | |
| apideck-pay-bill | — | |
| apideck-receive-customer-payment | — | |
| apideck-onboard-employee | — |
Configuration
APIDECK_API_KEYRequiredSecretYour Apideck API key (from https://platform.apideck.com/configuration/api-keys).
APIDECK_APP_IDRequiredYour Apideck application ID (from https://platform.apideck.com/configuration/api-keys).
APIDECK_CONSUMER_IDRequiredThe end-user/customer ID whose Vault connections should be used.
| Name | Description | |
|---|---|---|
| APIDECK_API_KEY | Your Apideck API key (from https://platform.apideck.com/configuration/api-keys). | RequiredSecret |
| APIDECK_APP_ID | Your Apideck application ID (from https://platform.apideck.com/configuration/api-keys). | Required |
| APIDECK_CONSUMER_ID | The end-user/customer ID whose Vault connections should be used. | Required |
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSPass
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubApideck MCP Server
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent to 200+ connectors — accounting systems, HRIS platforms, CRM, file storage, and more — through one integration.
Quick Connect
Recommended — prebuilt bundle:
Drag and drop the prebuilt mcp-server.mcpb onto Claude Desktop. Claude reads manifest.json to prompt for credentials and spawn the server — no manual config needed.
[!NOTE] Learn more about Desktop Extensions.
Local stdio (npx) alternative:
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"apideck": {
"command": "npx",
"args": ["-y", "@apideck/mcp", "start"],
"env": {
"APIDECK_API_KEY": "YOUR_API_KEY",
"APIDECK_CONSUMER_ID": "YOUR_CONSUMER_ID",
"APIDECK_APP_ID": "YOUR_APP_ID"
}
}
}
}
Restart Claude Desktop after saving. Pin a specific version by replacing @apideck/mcp with @apideck/mcp@0.1.15.
Set credentials in your shell:
export APIDECK_API_KEY="..."
export APIDECK_CONSUMER_ID="..."
export APIDECK_APP_ID="..."
Hosted (recommended):
claude mcp add --transport http apideck https://mcp.apideck.dev/mcp \
--header "Authorization: Bearer $APIDECK_API_KEY" \
--header "x-apideck-consumer-id: $APIDECK_CONSUMER_ID" \
--header "x-apideck-app-id: $APIDECK_APP_ID"
Local stdio (npx):
claude mcp add apideck \
-e APIDECK_API_KEY="$APIDECK_API_KEY" \
-e APIDECK_CONSUMER_ID="$APIDECK_CONSUMER_ID" \
-e APIDECK_APP_ID="$APIDECK_APP_ID" \
-- npx -y @apideck/mcp start
The start command reads credentials from environment variables only — it does not accept --api-key / --consumer-id / --app-id flags.
Settings → Cascade → Manage MCPs → View raw config, then paste:
{
"mcpServers": {
"apideck": {
"url": "https://mcp.apideck.dev/mcp",
"headers": {
"x-apideck-api-key": "YOUR_API_KEY",
"x-apideck-consumer-id": "YOUR_CONSUMER_ID",
"x-apideck-app-id": "YOUR_APP_ID"
}
}
}
}
{
"mcpServers": {
"apideck": {
"url": "https://mcp.apideck.dev/mcp",
"headers": {
"x-apideck-api-key": "YOUR_API_KEY",
"x-apideck-consumer-id": "YOUR_CONSUMER_ID",
"x-apideck-app-id": "YOUR_APP_ID"
}
}
}
}
Claude Desktop (.mcpb plugin bundle)
Apideck ships a Claude plugin bundle (.mcpb — Anthropic's Model Context Protocol Bundle format). Drop it into Claude Desktop and you get the full server (380+ tools: every endpoint tool plus 4 workflow tools) with API key / consumer ID / app ID prompted via the standard plugin UI.
pnpm mcpb:build # → dist/mcp-server.mcpb (~590 KB)
Each release attaches mcp-server.mcpb to the latest release. To build it yourself: pnpm mcpb:build → dist/mcp-server.mcpb. Open the .mcpb with Claude Desktop's plugin installer; Claude Desktop reads manifest.json to wire credentials and spawn the server.
Tools
380+ tools across 10 unified APIs (run list_tools({}) for live per-domain counts):
| API | Coverage |
|---|---|
| Accounting | Invoices, bills, payments, suppliers, customers, journal entries, ledger accounts, purchase orders, tax rates, P&L, balance sheet, and more |
| CRM | Companies, contacts, leads, opportunities, pipelines, notes, activities, users |
| File Storage | Files, folders, drives, shared links, upload sessions |
| HRIS | Employees, companies, departments, payrolls, time-off requests |
| Vault | Connections, consumers, sessions, custom mappings, logs |
| ATS | Applicants, applications, jobs |
| Issue Tracking | Collections, tickets, users, tags, comments |
| Connector | APIs, connectors, resources, coverage metadata |
| Ecommerce | Customers, orders, products, stores |
| Webhook | Webhook subscriptions, logs |
| Proxy | GET, POST, PUT, PATCH, DELETE |
Workflow tools
Intent-grouped workflows orchestrate multiple calls behind a single MCP tool — saving agents the round-trips and field-plumbing they routinely get wrong.
| Tool | What it does | Calls |
|---|---|---|
apideck-month-end-close-check |
Fans out aged-creditors, aged-debtors, balance-sheet, and P&L in parallel. Returns a partial result when some reports aren't supported by the connector. | 4 |
apideck-pay-bill |
Looks up a vendor bill and creates a bill payment allocated against it, so the accounting system marks the bill (partially) paid. | 2 |
apideck-receive-customer-payment |
Looks up an invoice and creates a customer payment allocated against it, so the accounting system marks the invoice (partially) paid. | 2 |
apideck-onboard-employee |
Converts a hired ATS applicant into an HRIS employee, and optionally moves the applicant to a "hired" stage. | 2–3 |
Hosted
The server is live at:
https://mcp.apideck.dev/mcp
Pass credentials via headers:
| Header | Description |
|---|---|
x-apideck-api-key |
Your Apideck API key |
x-apideck-consumer-id |
The end-user / customer ID in your app (optional — see below) |
x-apideck-app-id |
Your Apideck application ID |
x-apideck-auth-type |
Optional. Set to JWT to authenticate with a Vault session token instead of an API key |
Query parameters (single-credential clients)
Some clients can send only one credential, such as a bearer token. Put the API
key in Authorization and the ids in the URL:
https://mcp.apideck.dev/mcp?app_id=<your app ID>&consumer_id=<consumer ID>
Authorization: Bearer <your API key>
service_id works the same way. Precedence: header > query param > env var.
Empty values are ignored. The API key is never accepted in the URL, because
URLs end up in logs.
Vault session tokens (JWT)
To let an end user's browser or agent call tools without your API key, create a
Vault session
on your backend and pass its session_token instead:
Authorization: Bearer <session_token>
x-apideck-auth-type: JWT
x-apideck-app-id: <your app ID>
x-apideck-consumer-id: <the session's consumer ID>
The server forwards x-apideck-auth-type: JWT on every Apideck API call, the
same way the API Explorer authenticates sessions. Any other value keeps API-key
auth. A few limits:
- The header only takes effect alongside a bearer token in the request. The
server's own
APIDECK_API_KEYis never sent as a JWT. - A session token can't create a new Vault session. If a connection needs re-authorizing, the tool returns the plain error message instead of a re-auth link.
- JWT auth works over HTTP only. The stdio CLI always uses an API key.
Consumer scoping (optional)
The consumer ID is optional at connect time. Leave APIDECK_CONSUMER_ID /
x-apideck-consumer-id unset to start the server unscoped, then supply or
override the consumer per call by passing a consumer_id argument to any tool:
execute_tool({ name: "crm-contacts-all", input: { consumer_id: "acme-inc" } })
Precedence: per-call consumer_id argument > x-apideck-consumer-id header >
?consumer_id= query param > APIDECK_CONSUMER_ID env var.
- Unscoped calls work for application-scoped endpoints that don't need a
consumer — e.g. webhook logs (
webhook-event-logs-all) andvault-connections-all. - Consumer-scoped endpoints called without a consumer return Apideck's
"consumer required" error, so set
consumer_id(or the env/header) for those.
Locking identity (opt-in)
To pin identity to the boot header/query/env and stop agents from switching consumer
or connection per call, start with --lock-identity (CLI) or append
?lock_identity=true (hosted). Locked calls ignore per-call consumer_id /
service_id arguments. Off by default. Vault consumer tools that take
consumer_id as a path parameter (e.g. vault-consumers-one) only accept the
locked consumer; any other value, or no locked consumer, is refused.
service_id path parameters (e.g. vault-connections-one) are unaffected.
Three Modes
| Mode | Tools exposed | Initial tokens | Best for |
|---|---|---|---|
dynamic (default) |
4 meta-tools | ~1,300 | General-purpose agents, token-sensitive contexts |
static |
All endpoint tools + workflows | ~35–55K | Focused agents doing a specific API |
code |
apideck_search + apideck_run |
~600 | Agents that call endpoints programmatically via JS |
Dynamic mode
Agents discover tools progressively — ~85% fewer tokens than loading all 380+ schemas upfront:
list_tools({})
→ { total: <n>, domains: [{ name: "accounting", count: <n> }, ...],
hint: "Call list_tools(domain=X) or list_tools(search_terms=[...])" }
list_tools({"search_terms": ["invoices"]})
→ accounting-invoices-all, accounting-invoices-add, accounting-invoices-one, ...
describe_tool_input({"name": "accounting-invoices-all"})
→ Full JSON Schema with all parameters
execute_tool({"name": "accounting-invoices-all", "input": {"limit": 10}})
→ Invoice data from the connected accounting system
Put operation fields directly in input, using the contract returned by
describe_tool_input. Dynamic execution validates the arguments before dispatch;
malformed wrappers and schema violations return isError: true with
code: "invalid_tool_input", a field path or issue paths, and no downstream call.
Write tools also reject unknown top-level fields, so nothing undeclared reaches
the API. Validation errors do not echo submitted values. Per-call consumer_id and
service_id overrides remain supported; identity-lock rules still apply.
When a service_id is set, list_tools only lists tools the connector
supports, and calls to an unsupported resource return
code: "unsupported_resource", which means the connector can't serve it, not
that the result is empty.
Request schemas omit read-only response fields, while retaining writable linked
IDs and required path IDs. This does not add idempotency or make write retries safe.
You can combine dynamic mode with a scope filter:
{
"mcpServers": {
"apideck": {
"command": "node",
"args": ["dist/bin/mcp.js", "--mode", "dynamic", "--scope", "read"],
"env": { "APIDECK_API_KEY": "...", "APIDECK_CONSUMER_ID": "...", "APIDECK_APP_ID": "..." }
}
}
}
Code mode
Code mode exposes two tools instead of 380+. Designed for agents that prefer calling endpoints as methods rather than tool calls:
apideck_search— find endpoints by substring, returns camelCase method namesapideck_run— execute a JS script withapideck.<methodName>bound to live endpoint dispatchers, sandboxed innode:vm
apideck_search("invoices")
→ {
count: 4,
endpoints: [
{ name: "accounting-invoices-list", method: "accountingInvoicesList" },
{ name: "accounting-invoices-create", method: "accountingInvoicesCreate" },
{ name: "accounting-invoices-get", method: "accountingInvoicesGet" },
{ name: "accounting-invoices-delete", method: "accountingInvoicesDelete" }
]
}
apideck_run({
script: "return await apideck.accountingInvoicesList({ request: { limit: 5 } })"
})
→ Invoice data from the connected accounting system
If an endpoint call fails with an HTTP error, apideck_run returns the status and the Apideck error body next to the message, matching execute_tool:
{"error":"HTTP 401: Unauthorized Request - Application: invalid-test-app not found.","status":401,"body":{"type_name":"UnauthorizedError","detail":"Application: invalid-test-app not found.","...":"..."},"logs":[]}
Scripts can handle it themselves: catch (e) exposes e.message, e.status and e.body.
The sandbox strips process, require, fs, child_process, and other Node globals — scripts only have access to the apideck object.
Scopes
Filter tools by HTTP method class:
| Scope | HTTP methods | Flag |
|---|---|---|
read |
GET, HEAD | --scope read |
write |
POST, PUT, PATCH | --scope write |
destructive |
DELETE | --scope destructive |
Repeat the flag to combine scopes (--scope read --scope write). On the hosted
endpoint use a comma-separated query param: ?scopes=read,write. Invalid or
empty values are rejected (CLI parse error / HTTP 400). Scopes apply in every
mode, including code. When the scopes leave out destructive, execute_tool
is also marked non-destructive (destructiveHint: false).
Connect from Any Agent Framework
Remote (hosted — no local install)
# OpenAI Agents SDK
from agents import Agent
from agents.mcp import MCPServerHTTP
agent = Agent(
name="Apideck Agent",
mcp_servers=[MCPServerHTTP(
url="https://mcp.apideck.dev/mcp",
headers={
"x-apideck-api-key": "...",
"x-apideck-consumer-id": "...",
"x-apideck-app-id": "..."
}
)]
)
# Pydantic AI
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerHTTP
agent = Agent("anthropic:claude-sonnet-4-5", mcp_servers=[
MCPServerHTTP(
url="https://mcp.apideck.dev/mcp",
headers={
"x-apideck-api-key": "...",
"x-apideck-consumer-id": "...",
"x-apideck-app-id": "..."
}
)
])
# LangChain / LangGraph
from langchain_mcp_adapters.client import MultiServerMCPClient
client = MultiServerMCPClient({
"apideck": {
"url": "https://mcp.apideck.dev/mcp",
"transport": "streamable_http",
"headers": {
"x-apideck-api-key": "...",
"x-apideck-consumer-id": "...",
"x-apideck-app-id": "..."
}
}
})
tools = await client.get_tools()
Local stdio (for development)
pnpm install
pnpm build
# Dynamic mode (default)
APIDECK_API_KEY=... APIDECK_CONSUMER_ID=... APIDECK_APP_ID=... node dist/bin/mcp.js start
# Static mode (all endpoint tools + workflows)
APIDECK_API_KEY=... node dist/bin/mcp.js start --mode static
# Code mode
APIDECK_API_KEY=... node dist/bin/mcp.js start --mode code
# Read-only
APIDECK_API_KEY=... node dist/bin/mcp.js start --scope read
# OpenAI Agents SDK (local stdio)
from agents import Agent
from agents.mcp import MCPServerStdio
mcp = MCPServerStdio(name="apideck", params={
"command": "node",
"args": ["dist/bin/mcp.js", "start", "--mode", "dynamic"],
"env": {
"APIDECK_API_KEY": "...",
"APIDECK_CONSUMER_ID": "...",
"APIDECK_APP_ID": "..."
}
})
agent = Agent(name="Apideck Agent", mcp_servers=[mcp])
Reliability
The runtime automatically retries failed requests so transient errors don't surface to your agent:
- Retried status codes: 408, 500, 502, 503, 504
- Retried network errors:
ECONNRESET,ECONNREFUSED,ETIMEDOUT, and similar - Strategy: exponential backoff, up to 4 attempts, capped at 30 s
- Idempotency: retries only fire on GET, HEAD, PUT, DELETE, OPTIONS, TRACE — POST/PATCH are not retried automatically
Binary Content
File Storage endpoints that return images or audio send them as native MCP content blocks rather than base64 strings in JSON:
{ "type": "image", "data": "<base64>", "mimeType": "image/png" }
{ "type": "audio", "data": "<base64>", "mimeType": "audio/mpeg" }
Agents that support multi-modal MCP content (Claude, GPT-4o) receive the raw bytes — no extra decoding step needed.
License
MIT
Apideck MCP questions
How do I add Apideck MCP to Claude Code?
Run claude mcp add --env 'APIDECK_API_KEY=<YOUR_APIDECK_API_KEY>' --env 'APIDECK_APP_ID=<APIDECK_APP_ID>' --env 'APIDECK_CONSUMER_ID=<APIDECK_CONSUMER_ID>' mcp -- npx -y @apideck/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Apideck MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Apideck MCP provide?
It exposes 4 tools, including apideck-month-end-close-check, apideck-pay-bill, apideck-receive-customer-payment, apideck-onboard-employee.
How do I authenticate with the Apideck MCP server?
Pass your Apideck API key plus app ID and optional consumer ID as headers, a bearer token, or environment variables. Vault session JWTs are also supported over HTTP.
Which SaaS systems can I access through Apideck MCP?
It exposes 380+ tools across 10 unified APIs covering accounting, CRM, HRIS, ATS, file storage, issue tracking, ecommerce and more.
What is dynamic mode?
Dynamic mode is the default: it exposes 4 meta-tools that let agents discover and run endpoint tools progressively, using far fewer tokens than loading all schemas.
Is the consumer ID required to connect?
No, it is optional at connect time; you can start unscoped and pass consumer_id per call, though consumer-scoped endpoints need one.