One MCP server, one CLI, and a library of skills, so your agent can read and write the 200+ apps your customers already run on. OAuth handled, data normalized, ready to ship.
360+ tools. OAuth, streaming, elicitation. The default for agents.
https://mcp.apideck.dev/mcpFor shell-based agents and CI. ~80 tokens per call.
brew install apideck-libraries/tap/apideck146+ connectors. SDK, meta, and migration skills.
npx skills add apideck/api-skillsMost production agents ship two of the three. Use this matrix to pick the right surface per workload.
| Capability | MCP ServerRecommended | CLI | Skills |
|---|---|---|---|
| Best for | Native MCP clients, OAuth end-users | Shell-based agents, CI, scripts | Onboarding agents to Apideck |
| Token cost | Loads tool defs upfront | ~80 tokens / op | Loads on demand |
| Auth model | Per-consumer OAuth | Static API key | Inherited from CLI/MCP |
| Streaming | Yes | No | - |
| Elicitation | Yes | No | - |
| Works without MCP client | No | Yes | Yes |
| Framework support | MCP-compatible clients | Anything with exec | Anything with CLAUDE.md |
| Deploy | Hosted by Apideck | Local / CI | Local repo |
Each surface is one command away. Use one. Use all three.
# macOS / Linux brew install apideck-libraries/tap/apideck # auth once apideck auth login # query anything apideck accounting invoices list --service quickbooks --limit 5
Whether your agent runs in a terminal, an IDE, an SDK, or on the edge, Apideck plugs in.
Choosing between the MCP server, the CLI and skills
Last updated