This server connects MCP agents to Apideck's Unified API, exposing 330 endpoint tools across 10 business APIs plus workflow tools, with dynamic discovery in the default mode.
Discover and inspect tools at runtime: list_tools (filter by domain, search_terms, or scope), describe_tool_input for a tool's JSON Schema, and list_scopes.
Invoke any Apideck endpoint tool via execute_tool, forwarding raw input — e.g. accounting-invoices-list, crm-contacts-all, hris-employees-all, file-storage-files-all.
Work across 10 unified APIs: Accounting (143 tools), CRM (50), File Storage (32), HRIS (25), Vault (23), ATS (15), Issue Tracking (15), Connector (8), Ecommerce (7), Webhook (6), Proxy (6).
Run multi-call workflows in one shot, e.g. apideck-month-end-close-check fans out aged creditors/debtors, balance sheet, and P&L in parallel.
Pick a mode: dynamic (4 meta-tools, ~1.3K tokens), static (all 330 tools), or code (apideck_search + apideck_run for sandboxed JS method calls).
Constrain tools by HTTP method class with scopes: read, write, destructive.
Connect remotely to the hosted endpoint https://mcp.apideck.dev/mcp with API key/consumer/app headers, or locally via npx @apideck/mcp start (stdio).
Scope to a consumer per call with consumer_id, or lock identity with --lock-identity / ?lock_identity=true to prevent per-call switching.
Rely on automatic retries with exponential backoff for transient errors (408, 5xx, network), idempotent methods only.
Receive images/audio from File Storage as native MCP image/audio content blocks.
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.
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.
Learn more aboutDesktop 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 startThe 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"
}
}
}
}Related MCP server: OpsLevel MCP
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 (330 endpoint tools + 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)The bundle is built locally; CI publication to GitHub Releases is deferred. Open the .mcpb with Claude Desktop's plugin installer; Claude Desktop reads manifest.json to wire credentials and spawn the server.
330 tools across 10 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 |
CRM | 50 | Companies, contacts, leads, opportunities, pipelines, notes, activities, users |
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 |
ATS | 15 | Applicants, applications, jobs |
Issue Tracking | 15 | Collections, tickets, users, tags, comments |
Connector | 8 | APIs, connectors, resources, coverage metadata |
Ecommerce | 7 | Customers, orders, products, stores |
Webhook | 6 | Webhook subscriptions, logs |
Proxy | 6 | GET, POST, PUT, PATCH, DELETE, OPTIONS |
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 |
| 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 |
The server is live at:
https://mcp.apideck.dev/mcpPass credentials via headers:
Header | Description |
| Your Apideck API key |
| The end-user / customer ID in your app (optional — see below) |
| Your Apideck application ID |
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: the per-call consumer_id argument wins over the
APIDECK_CONSUMER_ID env var / x-apideck-consumer-id header.
Unscoped calls work for application-scoped endpoints that don't need a
consumer — e.g. webhook logs (webhook-event-logs-all) and
vault-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.
To pin identity to the boot header/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.
Mode | Tools exposed | Initial tokens | Best for |
| 4 meta-tools | ~1,300 | General-purpose agents, token-sensitive contexts |
| All 330 tools | ~35–55K | Focused agents doing a specific API |
|
| ~600 | Agents that call endpoints programmatically via JS |
Agents discover tools progressively — ~85% fewer tokens than loading all 330 schemas upfront:
list_tools({})
→ { total: 330, domains: [{ name: "accounting", count: 143 }, ...],
hint: "Call list_tools(domain=X) or list_tools(search_terms=[...])" }
list_tools({"search_terms": ["invoices"]})
→ accounting-invoices-list, accounting-invoices-create, accounting-invoices-get, ...
describe_tool_input({"name": "accounting-invoices-list"})
→ Full JSON Schema with all parameters
execute_tool({"name": "accounting-invoices-list", "input": {"request": {"limit": 10}}})
→ Invoice data from the connected accounting systemYou 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 exposes two tools instead of 330+. Designed for agents that prefer calling endpoints as methods rather than tool calls:
apideck_search — find endpoints by substring, returns camelCase method names
apideck_run — execute a JS script with apideck.<methodName> bound to live endpoint dispatchers, sandboxed in node: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 systemThe sandbox strips process, require, fs, child_process, and other Node globals — scripts only have access to the apideck object.
Filter tools by HTTP method class:
Scope | HTTP methods | Flag |
| GET, HEAD |
|
| POST, PUT, PATCH |
|
| DELETE |
|
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.
# 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()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 330 tools)
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])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
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.
MIT
Return the JSON-Schema input contract for a tool by name.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Exact tool name to describe (e.g. "accounting-invoices-create"), as returned by list_tools. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, indicating this is a safe read operation. The description adds little behavioral context beyond the purpose itself; it does not mention error cases (e.g., unknown tool name) or the exact format of the returned schema. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence stating the exact operation. No filler or repetition; every word contributes to the meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter introspection tool with strong annotations, the description sufficiently covers its return value. However, it lacks any note about behavior when the tool name is invalid, which might be useful but is not critical given the tool's simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a descriptive parameter entry for 'name' including an example and source ('as returned by list_tools'). The description itself adds no parameter-specific meaning, so it relies on the schema, which is adequate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific verb 'Return' and a well-defined resource: 'the JSON-Schema input contract for a tool by name.' This is unambiguous and distinguishes it from siblings like execute_tool or list_tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. Siblings are listed but not compared, and there is no mention of prerequisites or typical workflows (e.g., 'use before calling execute_tool'). The implied use case is not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Invoke a tool by name. input is forwarded raw to the tool handler.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Exact tool name to invoke (e.g. "accounting-invoices-create"), as returned by list_tools. | |
| input | No | Arguments object forwarded verbatim to the target tool. Its shape matches that tool's input schema (fetch it with describe_tool_input). Omit for tools that take no arguments. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that input is 'forwarded raw,' which is a behavioral detail beyond what annotations alone convey (e.g., openWorldHint, readOnlyHint). This tells agents that arguments are not preprocessed, which is essential for constructing valid input. No contradictions with annotations exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the core purpose and free of redundant information. Every word earns its place, and the structure is clean and scannable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is a dynamic dispatcher with rich schema descriptions and annotations covering side-effect hints, so the description is largely sufficient. It does not describe the return value or error behavior, but those are inherently dependent on the invoked tool and less critical given the schema's thoroughness. A slightly more explicit note about behavior varying by target tool would improve it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% as both parameters have detailed descriptions, so the baseline is 3. The description adds little beyond the schema, as 'forwarded raw' essentially repeats the schema's 'forwarded verbatim' for the input parameter. No additional parameter semantics are provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with a specific verb and resource: 'Invoke a tool by name.' This distinguishes it from sibling tools like list_tools or describe_tool_input, which inspect rather than execute. The additional phrase about forwarding input raw further clarifies the tool's role.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as looking up the tool name with list_tools or fetching the input schema with describe_tool_input. Those details appear only in the schema property descriptions, not in the main description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Return the list of allowed MCP scopes.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds the qualifier 'allowed,' implying scopes may be restricted, but provides no additional behavioral context beyond what annotations already convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence: 'Return the list of allowed MCP scopes.' Every word earns its place, with no redundancy or unnecessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple, parameterless tool, the description sufficiently communicates the return value (a list of scopes). While it lacks details on output format or edge cases, the tool's triviality means this is adequate completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters, and the schema is empty, so there is no parameter meaning to explain. The description is not required to compensate, and the baseline for 0-param tools is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'Return' and identifies the resource as 'list of allowed MCP scopes,' which clearly distinguishes it from sibling tools like list_tools (which lists tools) and execute_tool (which executes tools).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions, leaving the agent to infer usage solely from the tool's name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Discover Apideck tools. Call with no args for domain index; filter with domain/search_terms/scope.
| Name | Required | Description | Default |
|---|---|---|---|
| scope | No | Filter by mutation scope: "read" (no writes), "write" (creates/updates), or "destructive" (deletes/overwrites). Omit to include all scopes. | |
| domain | No | Restrict results to a single tool domain (e.g. "accounting", "hris"). Omit to get the cross-domain index. Use a key returned by a prior no-arg call. | |
| search_terms | No | Case-insensitive substring terms ANDed across a tool name/description (e.g. ["invoice","create"]). Omit to list everything in the domain. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is clear. The description adds the behavioral nuance of the no-args call and the filtering options, providing context beyond the annotations without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the core purpose, and includes essential usage instructions without any redundant words or fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple discovery tool with comprehensive schema and annotations, the description covers the main usage patterns (no-arg and filtered). It doesn't describe the return format, but the purpose and filtering behavior are sufficiently clear for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the schema already explains each parameter in detail. The description merely restates parameter names without adding new semantics, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description starts with 'Discover Apideck tools,' which clearly states the action and resource. It distinguishes itself from siblings by focusing on discovery/listing rather than execution or input description, and the mention of filtering adds specificity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit usage modes: call with no args for a domain index, or filter by domain/search_terms/scope. It doesn't explicitly mention alternatives, but the purpose is clear enough that the agent can infer when to use this tool versus siblings like execute_tool or describe_tool_input.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.11.3describe_tool_input2 fields changedInput schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Input schema / properties / name / descriptionAdded value: +"Exact tool name to describe (e.g. \"accounting-invoices-create\"), as returned by list_tools."execute_tool7 fields changedInput schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Input schema / properties / input / additionalPropertiesAdded value: +{}Input schema / properties / input / descriptionAdded value: +"Arguments object forwarded verbatim to the target tool. Its shape matches that tool's input schema (fetch it with describe_tool_input). Omit for tools that take no arguments."Input schema / properties / input / propertyNamesAdded value: +{
+ "type": "string"
+}Input schema / properties / input / typeAdded value: +"object"Input schema / properties / name / descriptionAdded value: +"Exact tool name to invoke (e.g. \"accounting-invoices-create\"), as returned by list_tools."Input schema / requiredPrevious value: -[
- "name",
- "input"
-]New value: +[
+ "name"
+]list_scopes2 fields changedInput schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Input schema / requiredAdded value: +[]list_tools5 fields changedInput schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Input schema / properties / domain / descriptionAdded value: +"Restrict results to a single tool domain (e.g. \"accounting\", \"hris\"). Omit to get the cross-domain index. Use a key returned by a prior no-arg call."Input schema / properties / scope / descriptionAdded value: +"Filter by mutation scope: \"read\" (no writes), \"write\" (creates/updates), or \"destructive\" (deletes/overwrites). Omit to include all scopes."Input schema / properties / search_terms / descriptionAdded value: +"Case-insensitive substring terms ANDed across a tool name/description (e.g. [\"invoice\",\"create\"]). Omit to list everything in the domain."Input schema / requiredAdded value: +[]v0.2.8describe_tool_inputexecute_toollist_scopeslist_toolsv0.2.7describe_tool_inputexecute_toollist_scopeslist_toolsv0.2.4describe_tool_input3 fields changedInput schema / properties / nameAdded value: +{
+ "type": "string"
+}Input schema / properties / tool_namesRemoved value: -{
- "description": "The names of the tools to describe",
- "items": {
- "type": "string"
- },
- "type": "array"
-}Input schema / requiredPrevious value: -[
- "tool_names"
-]New value: +[
+ "name"
+]execute_tool4 fields changedInput schema / properties / argumentsRemoved value: -{
- "additionalProperties": {},
- "description": "Arguments for the target tool as a JSON object, matching the schema returned by describe_tool_input.",
- "properties": {},
- "type": "object"
-}Input schema / properties / inputAdded value: +{}Input schema / properties / name / descriptionRemoved value: -"The name of the tool to execute"Input schema / requiredPrevious value: -[
- "name"
-]New value: +[
+ "name",
+ "input"
+]list_scopes1 field changedInput schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"list_tools3 fields changedInput schema / properties / domainAdded value: +{
+ "type": "string"
+}Input schema / properties / scopeAdded value: +{
+ "enum": [
+ "read",
+ "write",
+ "destructive"
+ ],
+ "type": "string"
+}Input schema / properties / search_terms / descriptionRemoved value: -"Filter the list of tools.\nEach term is matched case-insensitively as a substring against tool name, description, and scopes.\nMultiple terms are combined with a logical OR: a tool is included if ANY term matches ANY field.\nIf not provided, all tools are returned."v0.1.3accounting-aged-creditors-getaccounting-aged-debtors-getaccounting-attachments-deleteaccounting-attachments-downloadaccounting-attachments-getaccounting-attachments-listaccounting-attachments-uploadaccounting-balance-sheet-getaccounting-bank-accounts-createaccounting-bank-accounts-deleteaccounting-bank-accounts-getaccounting-bank-accounts-listaccounting-bank-accounts-updateaccounting-bank-feed-accounts-createaccounting-bank-feed-accounts-deleteaccounting-bank-feed-accounts-getaccounting-bank-feed-accounts-listaccounting-bank-feed-accounts-updateaccounting-bank-feed-statements-createaccounting-bank-feed-statements-deleteaccounting-bank-feed-statements-getaccounting-bank-feed-statements-listaccounting-bank-feed-statements-updateaccounting-bill-payments-createaccounting-bill-payments-deleteaccounting-bill-payments-getaccounting-bill-payments-listaccounting-bill-payments-updateaccounting-bills-createaccounting-bills-deleteaccounting-bills-getaccounting-bills-listaccounting-bills-updateaccounting-categories-getaccounting-categories-listaccounting-companies-listaccounting-company-info-getaccounting-credit-notes-createaccounting-credit-notes-deleteaccounting-credit-notes-getaccounting-credit-notes-listaccounting-credit-notes-updateaccounting-customers-createaccounting-customers-deleteaccounting-customers-getaccounting-customers-listaccounting-customers-updateaccounting-departments-createaccounting-departments-deleteaccounting-departments-getaccounting-departments-listaccounting-departments-updateaccounting-employees-createaccounting-employees-deleteaccounting-employees-getaccounting-employees-listaccounting-employees-updateaccounting-expense-categories-createaccounting-expense-categories-deleteaccounting-expense-categories-getaccounting-expense-categories-listaccounting-expense-categories-updateaccounting-expense-reports-createaccounting-expense-reports-deleteaccounting-expense-reports-getaccounting-expense-reports-listaccounting-expense-reports-updateaccounting-expenses-createaccounting-expenses-deleteaccounting-expenses-getaccounting-expenses-listaccounting-expenses-updateaccounting-invoice-items-createaccounting-invoice-items-deleteaccounting-invoice-items-getaccounting-invoice-items-listaccounting-invoice-items-updateaccounting-invoices-createaccounting-invoices-deleteaccounting-invoices-getaccounting-invoices-listaccounting-invoices-updateaccounting-journal-entries-createaccounting-journal-entries-deleteaccounting-journal-entries-getaccounting-journal-entries-listaccounting-journal-entries-updateaccounting-ledger-accounts-createaccounting-ledger-accounts-deleteaccounting-ledger-accounts-getaccounting-ledger-accounts-listaccounting-ledger-accounts-updateaccounting-locations-createaccounting-locations-deleteaccounting-locations-getaccounting-locations-listaccounting-locations-updateaccounting-payments-createaccounting-payments-deleteaccounting-payments-getaccounting-payments-listaccounting-payments-updateaccounting-profit-and-loss-getaccounting-projects-createaccounting-projects-deleteaccounting-projects-getaccounting-projects-listaccounting-projects-updateaccounting-purchase-orders-createaccounting-purchase-orders-deleteaccounting-purchase-orders-getaccounting-purchase-orders-listaccounting-purchase-orders-updateaccounting-quotes-createaccounting-quotes-deleteaccounting-quotes-getaccounting-quotes-listaccounting-quotes-updateaccounting-refunds-createaccounting-refunds-deleteaccounting-refunds-getaccounting-refunds-listaccounting-refunds-updateaccounting-subsidiaries-createaccounting-subsidiaries-deleteaccounting-subsidiaries-getaccounting-subsidiaries-listaccounting-subsidiaries-updateaccounting-suppliers-createaccounting-suppliers-deleteaccounting-suppliers-getaccounting-suppliers-listaccounting-suppliers-updateaccounting-tax-rates-createaccounting-tax-rates-deleteaccounting-tax-rates-getaccounting-tax-rates-listaccounting-tax-rates-updateaccounting-tracking-categories-createaccounting-tracking-categories-deleteaccounting-tracking-categories-getaccounting-tracking-categories-listaccounting-tracking-categories-updatedescribe_tool_inputexecute_toolfile-storage-drive-groups-createfile-storage-drive-groups-deletefile-storage-drive-groups-getfile-storage-drive-groups-listfile-storage-drive-groups-updatefile-storage-drives-createfile-storage-drives-deletefile-storage-drives-getfile-storage-drives-listfile-storage-drives-updatefile-storage-files-deletefile-storage-files-downloadfile-storage-files-exportfile-storage-files-getfile-storage-files-listfile-storage-files-searchfile-storage-files-updatefile-storage-folders-copyfile-storage-folders-createfile-storage-folders-deletefile-storage-folders-getfile-storage-folders-updatefile-storage-shared-links-createfile-storage-shared-links-deletefile-storage-shared-links-getfile-storage-shared-links-listfile-storage-shared-links-updatefile-storage-upload-sessions-createfile-storage-upload-sessions-deletefile-storage-upload-sessions-finishfile-storage-upload-sessions-getfile-storage-upload-sessions-uploadhris-companies-createhris-companies-deletehris-companies-gethris-companies-listhris-companies-updatehris-departments-createhris-departments-deletehris-departments-gethris-departments-listhris-departments-updatehris-employee-payrolls-gethris-employee-payrolls-listhris-employee-schedules-listhris-employees-createhris-employees-deletehris-employees-gethris-employees-listhris-employees-updatehris-payrolls-gethris-payrolls-listhris-time-off-requests-createhris-time-off-requests-deletehris-time-off-requests-gethris-time-off-requests-listhris-time-off-requests-updatelist_scopeslist_toolsproxy-deleteproxy-getproxy-optionsproxy-patchproxy-postproxy-putvault-connection-consent-updatevault-connection-consents-listvault-connection-custom-mappings-listvault-connection-settings-listvault-connection-settings-updatevault-connections-deletevault-connections-getvault-connections-importsvault-connections-listvault-connections-tokenvault-connections-updatevault-consumer-request-counts-listvault-consumers-createvault-consumers-deletevault-consumers-getvault-consumers-listvault-consumers-updatevault-create-callback-statevault-custom-fields-listvault-custom-mappings-listvault-logs-listvault-sessions-createvault-validate-connection-statev0.1.0accounting-aged-creditors-getaccounting-aged-debtors-getaccounting-attachments-deleteaccounting-attachments-downloadaccounting-attachments-getaccounting-attachments-listaccounting-attachments-uploadaccounting-balance-sheet-getaccounting-bank-accounts-createaccounting-bank-accounts-deleteaccounting-bank-accounts-getaccounting-bank-accounts-listaccounting-bank-accounts-updateaccounting-bank-feed-accounts-createaccounting-bank-feed-accounts-deleteaccounting-bank-feed-accounts-getaccounting-bank-feed-accounts-listaccounting-bank-feed-accounts-updateaccounting-bank-feed-statements-createaccounting-bank-feed-statements-deleteaccounting-bank-feed-statements-getaccounting-bank-feed-statements-listaccounting-bank-feed-statements-updateaccounting-bill-payments-createaccounting-bill-payments-deleteaccounting-bill-payments-getaccounting-bill-payments-listaccounting-bill-payments-updateaccounting-bills-createaccounting-bills-deleteaccounting-bills-getaccounting-bills-listaccounting-bills-updateaccounting-categories-getaccounting-categories-listaccounting-companies-listaccounting-company-info-getaccounting-credit-notes-createaccounting-credit-notes-deleteaccounting-credit-notes-getaccounting-credit-notes-listaccounting-credit-notes-updateaccounting-customers-createaccounting-customers-deleteaccounting-customers-getaccounting-customers-listaccounting-customers-updateaccounting-departments-createaccounting-departments-deleteaccounting-departments-getaccounting-departments-listaccounting-departments-updateaccounting-employees-createaccounting-employees-deleteaccounting-employees-getaccounting-employees-listaccounting-employees-updateaccounting-expense-categories-createaccounting-expense-categories-deleteaccounting-expense-categories-getaccounting-expense-categories-listaccounting-expense-categories-updateaccounting-expense-reports-createaccounting-expense-reports-deleteaccounting-expense-reports-getaccounting-expense-reports-listaccounting-expense-reports-updateaccounting-expenses-createaccounting-expenses-deleteaccounting-expenses-getaccounting-expenses-listaccounting-expenses-updateaccounting-invoice-items-createaccounting-invoice-items-deleteaccounting-invoice-items-getaccounting-invoice-items-listaccounting-invoice-items-updateaccounting-invoices-createaccounting-invoices-deleteaccounting-invoices-getaccounting-invoices-listaccounting-invoices-updateaccounting-journal-entries-createaccounting-journal-entries-deleteaccounting-journal-entries-getaccounting-journal-entries-listaccounting-journal-entries-updateaccounting-ledger-accounts-createaccounting-ledger-accounts-deleteaccounting-ledger-accounts-getaccounting-ledger-accounts-listaccounting-ledger-accounts-updateaccounting-locations-createaccounting-locations-deleteaccounting-locations-getaccounting-locations-listaccounting-locations-updateaccounting-payments-createaccounting-payments-deleteaccounting-payments-getaccounting-payments-listaccounting-payments-updateaccounting-profit-and-loss-getaccounting-projects-createaccounting-projects-deleteaccounting-projects-getaccounting-projects-listaccounting-projects-updateaccounting-purchase-orders-createaccounting-purchase-orders-deleteaccounting-purchase-orders-getaccounting-purchase-orders-listaccounting-purchase-orders-updateaccounting-quotes-createaccounting-quotes-deleteaccounting-quotes-getaccounting-quotes-listaccounting-quotes-updateaccounting-refunds-createaccounting-refunds-deleteaccounting-refunds-getaccounting-refunds-listaccounting-refunds-updateaccounting-subsidiaries-createaccounting-subsidiaries-deleteaccounting-subsidiaries-getaccounting-subsidiaries-listaccounting-subsidiaries-updateaccounting-suppliers-createaccounting-suppliers-deleteaccounting-suppliers-getaccounting-suppliers-listaccounting-suppliers-updateaccounting-tax-rates-createaccounting-tax-rates-deleteaccounting-tax-rates-getaccounting-tax-rates-listaccounting-tax-rates-updateaccounting-tracking-categories-createaccounting-tracking-categories-deleteaccounting-tracking-categories-getaccounting-tracking-categories-listaccounting-tracking-categories-updatefile-storage-drive-groups-createfile-storage-drive-groups-deletefile-storage-drive-groups-getfile-storage-drive-groups-listfile-storage-drive-groups-updatefile-storage-drives-createfile-storage-drives-deletefile-storage-drives-getfile-storage-drives-listfile-storage-drives-updatefile-storage-files-deletefile-storage-files-downloadfile-storage-files-exportfile-storage-files-getfile-storage-files-listfile-storage-files-searchfile-storage-files-updatefile-storage-folders-copyfile-storage-folders-createfile-storage-folders-deletefile-storage-folders-getfile-storage-folders-updatefile-storage-shared-links-createfile-storage-shared-links-deletefile-storage-shared-links-getfile-storage-shared-links-listfile-storage-shared-links-updatefile-storage-upload-sessions-createfile-storage-upload-sessions-deletefile-storage-upload-sessions-finishfile-storage-upload-sessions-getfile-storage-upload-sessions-uploadhris-companies-createhris-companies-deletehris-companies-gethris-companies-listhris-companies-updatehris-departments-createhris-departments-deletehris-departments-gethris-departments-listhris-departments-updatehris-employee-payrolls-gethris-employee-payrolls-listhris-employee-schedules-listhris-employees-createhris-employees-deletehris-employees-gethris-employees-listhris-employees-updatehris-payrolls-gethris-payrolls-listhris-time-off-requests-createhris-time-off-requests-deletehris-time-off-requests-gethris-time-off-requests-listhris-time-off-requests-updateproxy-deleteproxy-getproxy-optionsproxy-patchproxy-postproxy-putvault-connection-consent-updatevault-connection-consents-listvault-connection-custom-mappings-listvault-connection-settings-listvault-connection-settings-updatevault-connections-deletevault-connections-getvault-connections-importsvault-connections-listvault-connections-tokenvault-connections-updatevault-consumer-request-counts-listvault-consumers-createvault-consumers-deletevault-consumers-getvault-consumers-listvault-consumers-updatevault-create-callback-statevault-custom-fields-listvault-custom-mappings-listvault-logs-listvault-sessions-createvault-validate-connection-stateScored across 4 tools
Each tool has a distinct purpose: listing tools, describing input schemas, executing tools, and listing scopes. No overlap.
All tool names follow a consistent verb_noun pattern with snake_case (list_tools, describe_tool_input, execute_tool, list_scopes).
4 tools are well-scoped for a tool management server—covering discovery, schema inspection, execution, and scope listing without excess.
Covers all core operations for tool management, though output schema or detailed tool metadata beyond input schema is missing.
MCP server for Codat — companies, connections, invoices, bills and financial statements.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
