# How to connect the Apideck MCP server

To connect the official Apideck MCP server, add https://mcp.apideck.dev/mcp to your MCP client as a Streamable HTTP server, then send your API key in the documented header. Apideck documents setup for Claude, Claude Code, Windsurf, Cursor and VS Code.

- Endpoint: https://mcp.apideck.dev/mcp
- Transport: Streamable HTTP
- Registry: com.apideck/mcp 0.1.13
- Publisher documentation reviewed: 2026-11-05 (connection tested)
- Guide page: https://apitracker.io/mcp-guides/apideck-mcp

## Before you start

- An Apideck account with an application. The application gives you the API key and application ID.
- Connect the SaaS apps you want the agent to use (for example QuickBooks, Xero or BambooHR) in Vault for the consumer ID you send.

## Steps

1. **Open Apideck's MCP server setup instructions** <https://github.com/apideck-libraries/mcp>
2. **Add the Apideck MCP server to your client** Add https://mcp.apideck.dev/mcp as a remote MCP server that uses the Streamable HTTP transport (often labelled "http"). Apideck also publishes a Claude Desktop bundle, one-click installs for Cursor and VS Code, and a local stdio package.
3. **Required: your Apideck API key (x-apideck-api-key header)**
4. **Required: your Apideck application ID (x-apideck-app-id header)**
5. **Your consumer ID, whose Vault connections the server uses (x-apideck-consumer-id header)**
6. **If your client accepts only one credential, use a bearer token** Send your API key as a bearer token in the Authorization header, and pass the application ID, consumer ID and service ID as the app_id, consumer_id and service_id query parameters on the server URL. The API key is never accepted in the URL.
7. **Optional: authenticate with a Vault session token instead of your API key** Create a Vault session on your backend and send its session token as the bearer token, with the x-apideck-auth-type header set to JWT plus the x-apideck-app-id and x-apideck-consumer-id headers for that session's consumer. A session token can't create another Vault session, and if a connection needs re-authorizing the tool returns an error instead of a re-auth link. This works over HTTP only.
8. **List the server's tools**

## Questions

### What is the Apideck MCP server URL?

The official Apideck MCP server is at https://mcp.apideck.dev/mcp and uses the Streamable HTTP transport.

### How do I authenticate with the Apideck MCP server?

Send your API key in the documented header. If your client accepts only one credential, use a bearer token: Send your API key as a bearer token in the Authorization header, and pass the application ID, consumer ID and service ID as the app_id, consumer_id and service_id query parameters on the server URL. The API key is never accepted in the URL. Optional: authenticate with a Vault session token instead of your API key: Create a Vault session on your backend and send its session token as the bearer token, with the x-apideck-auth-type header set to JWT plus the x-apideck-app-id and x-apideck-consumer-id headers for that session's consumer. A session token can't create another Vault session, and if a connection needs re-authorizing the tool returns an error instead of a re-auth link. This works over HTTP only.

### Which AI clients can use the Apideck MCP server?

Apideck's documentation covers Claude, Claude Code, Windsurf, Cursor and VS Code. Other clients that support remote Streamable HTTP MCP servers may also work.

### What do I need before connecting Apideck MCP?

An Apideck account with an application. The application gives you the API key and application ID. Connect the SaaS apps you want the agent to use (for example QuickBooks, Xero or BambooHR) in Vault for the consumer ID you send.

### Has this Apideck MCP guide been tested?

Apideck's documentation was reviewed on 2026-11-05. The connection was tested.

## Sources

- https://www.apideck.com/mcp-server (checked 2026-11-05)
- https://github.com/apideck-libraries/mcp (checked 2026-11-05)
- https://developers.apideck.com/apis/vault/reference/sessions (checked 2026-11-05)
- https://registry.modelcontextprotocol.io/v0.1/servers/com.apideck%2Fmcp/versions/0.1.13 (checked 2026-11-05)

Guide JSON: https://github.com/apideck-libraries/mcp-connect/blob/626f6a146170ded34891b30dca3af26f09e07466/proposals/connection-guide/0.1/reviewed/guides/apideck-mcp.json