Server data from the Official MCP Registry
Apideck Unified API MCP — 229 tools across 200+ SaaS connectors (accounting, HRIS, file storage).
Apideck Unified API MCP — 229 tools across 200+ SaaS connectors (accounting, HRIS, file storage).
Remote endpoints: streamable-http: https://mcp.apideck.dev/mcp
Valid MCP server (1 strong, 1 medium validity signals). 1 known CVE in dependencies Package registry verified. Imported from the Official MCP Registry.
3 files analyzed · 2 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: APIDECK_API_KEY
Environment variable: APIDECK_APP_ID
Environment variable: APIDECK_CONSUMER_ID
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
From the project's GitHub README.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 200+ connectors — accounting systems, HRIS platforms, file storage providers, and more — through one integration.
Generated from Apideck's OpenAPI spec using Speakeasy.
229 tools across 5 unified APIs:
| API | Tools | Coverage |
|---|---|---|
| Accounting | 143 | Invoices, bills, payments, suppliers, customers, journal entries, ledger accounts, purchase orders, tax rates, P&L, balance sheet, and more |
| File Storage | 32 | Files, folders, drives, shared links, upload sessions |
| HRIS | 25 | Employees, companies, departments, payrolls, time-off requests |
| Vault | 23 | Connections, consumers, sessions, custom mappings, logs |
| Proxy | 6 | GET, POST, PUT, PATCH, DELETE, OPTIONS |
The MCP server is live at:
https://mcp.apideck.dev/mcp
Pass Apideck 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 |
x-apideck-app-id | Your Apideck application ID |
# OpenAI Agents SDK (remote)
from agents import Agent
from agents.mcp import MCPServerHTTP
agent = Agent(
name="AP 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 (remote)
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 (remote)
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()
Add to your MCP client config:
{
"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"
}
}
}
}
npm install
# Dynamic mode (default — progressive discovery, 4 meta-tools, ~1,300 tokens)
node bin/mcp-server.js start --api-key "$APIDECK_API_KEY" --consumer-id "$APIDECK_CONSUMER_ID" --app-id "$APIDECK_APP_ID"
# Static mode (all 229 tools)
node bin/mcp-server.js start --api-key "$APIDECK_API_KEY" --consumer-id "$APIDECK_CONSUMER_ID" --app-id "$APIDECK_APP_ID" --mode static
# Read-only tools only
node bin/mcp-server.js start --api-key "$APIDECK_API_KEY" --consumer-id "$APIDECK_CONSUMER_ID" --app-id "$APIDECK_APP_ID" --scope read
# OpenAI Agents SDK (local stdio)
from agents import Agent
from agents.mcp import MCPServerStdio
mcp = MCPServerStdio(name="apideck", params={
"command": "node",
"args": ["bin/mcp-server.js", "start", "--mode", "dynamic"],
"env": {
"APIDECK_API_KEY": "...",
"APIDECK_CONSUMER_ID": "...",
"APIDECK_APP_ID": "..."
}
})
agent = Agent(name="AP Agent", mcp_servers=[mcp])
# Pydantic AI (local stdio)
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStdio
agent = Agent("anthropic:claude-sonnet-4-5", mcp_servers=[
MCPServerStdio("node", [
"bin/mcp-server.js", "start", "--mode", "dynamic",
"--api-key", "...", "--consumer-id", "...", "--app-id", "..."
])
])
| Mode | Tools exposed | Initial tokens | Best for |
|---|---|---|---|
dynamic (default) | 4 meta-tools: list_tools, describe_tool_input, execute_tool, list_scopes | ~1,300 | General-purpose agents, token-sensitive contexts |
static | All 229 tools | ~25-40K | Focused agents doing specific operations |
In dynamic mode, agents discover tools progressively:
list_tools({"search_terms": ["invoices"]})
→ accounting-invoices-list, accounting-invoices-create, accounting-invoices-get, ...
describe_tool_input({"tool_names": ["accounting-invoices-list"]})
→ Full JSON Schema with all parameters
execute_tool({"tool_name": "accounting-invoices-list", "input": {"request": {"limit": 10}}})
→ Invoice data from the connected accounting system
The generate-overlay.py script controls which Apideck APIs are included:
# Default: accounting, fileStorage, hris, vault, proxy (229 tools)
python generate-overlay.py
# Accounting only (143 tools)
python generate-overlay.py accounting
# Custom selection
python generate-overlay.py accounting,hris,vault
# All APIs (336 tools — exceeds Speakeasy free tier of 250)
python generate-overlay.py all
# Then regenerate + apply fixes:
speakeasy run
./post-generate.sh
The MCP server is generated from Apideck's Speakeasy-optimized OpenAPI spec. To regenerate after spec changes:
# 1. Optionally reconfigure APIs
python generate-overlay.py accounting,fileStorage,hris,vault,proxy
# 2. Regenerate
speakeasy run
# 3. Apply post-generation fixes (Zod transforms fix + wrangler.toml)
./post-generate.sh
# 4. Run tests
node bin/mcp-server.js serve --port 4567 --mode dynamic --log-level error &
npx tsx test/mcp-server.test.ts
Tools are annotated with scopes for fine-grained control:
| Scope | HTTP methods | Flag |
|---|---|---|
read | GET, HEAD | --scope read |
write | POST, PUT, PATCH | --scope write |
destructive | DELETE | --scope destructive |
# Local
node bin/mcp-server.js serve --port 4567 --mode dynamic --log-level error &
npx tsx test/mcp-server.test.ts
# Remote
MCP_URL=https://mcp.apideck.dev/mcp npx tsx test/mcp-server.test.ts
MIT
Apideck: The Apideck OpenAPI Spec: SDK Optimized
For more information about the API: Apideck Developer Docs
[!TIP] To finish publishing your MCP Server to npm and others you must run your first generation action.
Install the MCP server as a Desktop Extension using the pre-built mcp-server.mcpb file:
Simply drag and drop the mcp-server.mcpb file onto Claude Desktop to install the extension.
The MCP bundle package includes the MCP server and all necessary configuration. Once installed, the server will be available without additional setup.
[!NOTE] MCP bundles provide a streamlined way to package and distribute MCP servers. Learn more about Desktop Extensions.
Or manually:
{
"command": "npx",
"args": [
"@apideck/mcp",
"start",
"--api-key",
"",
"--consumer-id",
"",
"--app-id",
""
]
}
claude mcp add ApideckMcp -- npx -y @apideck/mcp start --api-key --consumer-id --app-id
gemini mcp add ApideckMcp -- npx -y @apideck/mcp start --api-key --consumer-id --app-id
Refer to Official Windsurf documentation for latest information
Manage MCPs. (To Manage MCPs you should be signed in with a Windsurf Account)View raw config to open up the mcp configuration file.{
"command": "npx",
"args": [
"@apideck/mcp",
"start",
"--api-key",
"",
"--consumer-id",
"",
"--app-id",
""
]
}
Or manually:
Refer to Official VS Code documentation for latest information
MCP: Open User Configuration. This should open mcp.json file{
"command": "npx",
"args": [
"@apideck/mcp",
"start",
"--api-key",
"",
"--consumer-id",
"",
"--app-id",
""
]
}
npx @apideck/mcp start --api-key --consumer-id --app-id
For a full list of server arguments, run:
npx @apideck/mcp --help
MCP servers with many tools can bloat LLM context windows, leading to increased token usage and tool confusion. Dynamic mode solves this by exposing only a small set of meta-tools that let agents progressively discover and invoke tools on demand.
To enable dynamic mode, pass the --mode dynamic flag when starting your server:
{
"mcpServers": {
"ApideckMcp": {
"command": "npx",
"args": ["@apideck/mcp", "start", "--mode", "dynamic"],
// ... other server arguments
}
}
}
In dynamic mode, the server registers only the following meta-tools instead of every individual tool:
list_tools: Lists all available tools with their names and descriptions.describe_tool: Returns the input schema for one or more tools by name.execute_tool: Executes a tool by name with the provided input parameters.list_scopes: Lists the scopes available on the server.This approach significantly reduces the number of tokens sent to the LLM on each request, which is especially useful for servers with a large number of tools.
You can combine dynamic mode with scope and tool filters:
{
"mcpServers": {
"ApideckMcp": {
"command": "npx",
"args": ["@apideck/mcp", "start", "--mode", "dynamic", "--scope", "destructive"],
// ... other server arguments
}
}
}
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.