# Apideck MCP Server

The Apideck Model Context Protocol (MCP) server exposes 229 tools across 5 Unified APIs (CRM, Accounting, HRIS, ATS, File Storage) through a single endpoint. AI agents can call any connected integration through the MCP without writing code per-connector.

## Features

- **229 tools** covering the most-used operations across 5 Unified APIs
- **Managed OAuth via Vault**: end users authorize integrations once; the MCP handles token refresh and storage
- **Progressive discovery**: the server advertises tools lazily so large tool catalogs don't blow the agent's context budget
- **Works with any MCP-compatible client**: Claude Desktop, Cursor, Goose, and other agents that speak the MCP protocol

## Connect

- MCP endpoint: `https://mcp.apideck.com`
- Marketing page with supported clients and connected services: https://www.apideck.com/mcp-server
- Configuration guide: https://developers.apideck.com/building-with-llms.md

## Docs MCP

A separate, read-only MCP server also answers this same `/mcp` URL: no auth, no write access, and
no connector data. It indexes this documentation site — the same content behind
[llms.txt](https://developers.apideck.com/llms.txt) — so a coding agent can search and fetch it at query time instead of
relying on training data. Which server responds depends on how the client talks to the endpoint,
not on a different address.

```bash
claude mcp add --transport http apideck-docs https://developers.apideck.com/mcp
```

Tools: `search_docs(query, limit?, path_prefix?)`, `get_doc(path, section?)`,
`list_docs(path_prefix?, limit?)`. Every page is also an MCP resource at `docs://<path>`.

## Related

- [CLI for humans and AI agents](https://developers.apideck.com/cli.md)
- [Agent skills for the SDKs](https://github.com/apideck-libraries/api-skills)
- [OpenAPI specs](https://github.com/apideck-libraries/openapi-specs)