# Apideck
ID: 07-apideck
Page: https://gtmmcps.com/tools/07-apideck
JSON: https://gtmmcps.com/data/tools/07-apideck.json
Documentation references: https://gtmmcps.com/docs/07-apideck/
Category: MCP Layer
MCP support: official
Testing: RESEARCHED
API access: free
Last checked: 2026-08-25
Endpoint check: repo-local; date: 2026-09-04

A unified API that normalises 200+ SaaS connectors into single data models, exposed as one MCP endpoint covering CRM, accounting, HRIS, ATS, file storage and issue tracking.

## MCP links
- https://github.com/apideck-libraries/mcp
- https://developers.apideck.com/mcp

## Sources
- https://developers.apideck.com/mcp
- https://www.apideck.com/mcp-server
- https://github.com/apideck-libraries/mcp

## Research notes
Added 2026-08-25 in the coverage sweep. CAVEAT ON THE ENDPOINT: two different hosted endpoints appear in the vendor's own material, mcp.apideck.com in the developer docs and mcp.apideck.dev on the marketing page. Confirm which is current before wiring it up; the GitHub repo is cited as mcp_url because it is the one unambiguous vendor-owned artifact. Signup is self-serve and free to start, but the paid tier thresholds are not published, so "free" here means free-to-start, not free-at-volume. The four-meta-tool dynamic mode is the same design problem the Salesforce Hosted MCP entry (06) solves with Discover/Describe/Dispatch, and the two make a natural pair for a segment on how not to dump 3,000 tools on an agent.

## Named capabilities
Tool names below are reported by sources. Their presence is not a successful call.
- API: Tools; evidence: readme; party: first-party
- ATS: 15; evidence: readme; party: first-party
- Accounting: 143; evidence: readme; party: first-party
- CRM: 50; evidence: readme; party: first-party
- Connector: 8; evidence: readme; party: first-party
- Ecommerce: 7; evidence: readme; party: first-party
- HRIS: 25; evidence: readme; party: first-party
- Header: Description; evidence: readme; party: first-party
- Mode: Tools exposed; evidence: readme; party: first-party
- Proxy: 6; evidence: readme; party: first-party
- Scope: HTTP methods; evidence: readme; party: first-party
- Vault: 23; evidence: readme; party: first-party
- Webhook: 6; evidence: readme; party: first-party
- 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.; evidence: readme; party: first-party
- code: `apideck_search` + `apideck_run`; evidence: readme; party: first-party
- destructive: DELETE; evidence: readme; party: first-party
- get_doc: Return the full markdown of a documentation page by path, or a single section of it. Use search_docs or list_docs to find paths.; evidence: live-list; party: 
- list_docs: List documentation pages with their path, title, description and last-modified date. Useful to browse the structure before searching or to find pages under a prefix.; evidence: live-list; party: 
- read: GET, HEAD; evidence: readme; party: first-party
- search_docs: Full-text search over the documentation. Returns matching sections with a snippet, the page path and heading anchor. Call get_doc with a returned path to read the full page or a single section.; evidence: live-list; party: 
- static: All 330 tools; evidence: readme; party: first-party
- write: POST, PUT, PATCH; evidence: readme; party: first-party
- x-apideck-api-key: Your Apideck API key; evidence: readme; party: first-party
- x-apideck-app-id: Your Apideck application ID; evidence: readme; party: first-party
- x-apideck-consumer-id: The end-user / customer ID in your app (**optional** — see below); evidence: readme; party: first-party

## CLI evidence
Status: official
- Reported install command: brew install apideck-libraries/tap/apideck; source: https://www.apideck.com/cli
- Reported install command: go install github.com/apideck-libraries/cli/cmd/apideck@latest; source: https://developers.apideck.com/cli
- Reported install command: docker run apideck/cli; source: https://developers.apideck.com/cli

Read current vendor documentation before configuring or running commands.