# Building with LLMs

Apideck ships several agent-friendly primitives so that LLM-based coding assistants, MCP clients, and autonomous agents can build with the Unified APIs without hand-written glue code.

## MCP server

The [Apideck MCP Server](https://developers.apideck.com/mcp.md) exposes 229 tools across 5 Unified APIs to any MCP-compatible client (Claude Desktop, Cursor, Goose, etc.).

## CLI

The [Apideck CLI](https://developers.apideck.com/cli.md) is OpenAPI-native — every operation is a subcommand — which makes it reliable for agents that prefer shelling out to making HTTP calls directly.

## Agent skills

The [api-skills repository](https://github.com/apideck-libraries/api-skills) contains per-SDK skills that teach an agent how to use each SDK: installation, authentication, method naming, and common patterns.

```bash
npx skills add apideck/api-skills --skill apideck-node
npx skills add apideck/api-skills --skill apideck-python
npx skills add apideck/api-skills --skill apideck-dotnet
```

## Plain-text documentation

Every documentation page is available as markdown at `<page>.md` or by sending the `Accept: text/markdown` header. Machine-readable indexes live at:

- [https://developers.apideck.com/llms.txt](https://developers.apideck.com/llms.txt) — curated overview
- [https://developers.apideck.com/llms-full.txt](https://developers.apideck.com/llms-full.txt) — enumerated index of every API operation and guide
- [https://developers.apideck.com/md/index.json](https://developers.apideck.com/md/index.json) — JSON index of all markdown paths

## Steer your coding agent

Drop this into your project's `AGENTS.md` or `CLAUDE.md` so Claude Code, Cursor, and other coding
agents default to Apideck's own docs and conventions instead of guessing:

```markdown
## Apideck

Always consult https://developers.apideck.com/llms.txt before writing Apideck
integration code, or use the Apideck MCP server if it's configured. Use the
current unified SDKs, never the legacy @apideck/node package. Check
connector coverage (/apis/<api>/coverage) before assuming an operation is
supported. Use Vault for consumer-facing auth, never raw downstream credentials.
```

## OpenAPI specs

Every Unified API publishes an OpenAPI 3.1 spec at https://github.com/apideck-libraries/openapi-specs. The CLI and SDKs are generated from these specs.

## IDE plugins

Cursor, Continue, and other IDE-integrated assistants can consume the OpenAPI specs and skills directly; follow the installation instructions in the [api-skills README](https://github.com/apideck-libraries/api-skills) to wire them up.