---
title: "Install AI Content Drop in Claude Code | AI Content Drop"
description: "Connect Claude Code to the AI Content Drop MCP server so your agent can browse {{VIDEO_MODEL_COUNT}} video models, quote credit costs, and generate video and images from the terminal."
canonical: "https://aicontentdrop.com/docs/install/claude-code"
source: "https://aicontentdrop.com/docs/install/claude-code"
---

# AI Content Drop in Claude Code

One MCP connection. Browsing works immediately with no credential; generating
needs an API key.

## Add the server

Claude Code reads MCP servers from its settings file. Add:

```json
{
  "mcpServers": {
    "aicontentdrop": {
      "type": "streamable-http",
      "url": "https://aicontentdrop.com/mcp"
    }
  }
}
```

Claude Code also ships an `mcp` subcommand that writes this for you; if you
prefer it, run `claude mcp --help` and use the HTTP transport form. The JSON
above is the contract either route produces, so if the CLI flags have moved in
your version, writing the file directly always works.

Restart Claude Code, then ask it to list its MCP tools. You should see eight
under `aicontentdrop`.

## Verify without a credential

Ask your agent:

> Using the aicontentdrop tools, list the video models under 20 credits.

That calls `list_models`, which needs no key. If it answers with model ids and
credit costs, the connection is good.

## Authorize

Create a key at [https://aicontentdrop.com/settings/integrations](https://aicontentdrop.com/settings/integrations).
Keys are shown once and look like `acd_live_…`.

Give it to Claude Code as a header on the same server entry:

```json
{
  "mcpServers": {
    "aicontentdrop": {
      "type": "streamable-http",
      "url": "https://aicontentdrop.com/mcp",
      "headers": {
        "Authorization": "Bearer acd_live_YOUR_KEY"
      }
    }
  }
}
```

The four account tools (`generate_video`, `get_generation`, `list_generations`,
`get_account`) start working. The other four never needed the key.

Treat the settings file as a secret once a key is in it. If your Claude Code
version supports an environment-variable reference in that field, prefer it over
the literal key.

## First generation

> Quote me the cost of a 5-second Kling 3.0 video, then generate one of a matcha
> tin on a linen backdrop, and poll it until it is done.

The agent should call `estimate_credit_cost`, then `generate_video`, then
`get_generation` until the job reports `completed`. Credits are charged on
success only — a failed render costs nothing.

## Documentation-only variant

To give an agent the guides without the ability to spend anything, point it at
the documentation server instead:

```json
{
  "mcpServers": {
    "aicontentdrop-docs": {
      "type": "streamable-http",
      "url": "https://aicontentdrop.com/mcp/docs"
    }
  }
}
```

Two tools, no credential, nothing that can bill.

## Troubleshooting

**The server connects but shows no tools.** Confirm the URL is `https://aicontentdrop.com/mcp`
with no trailing slash, and that the transport is the streamable HTTP one rather
than a stdio command.

**Account tools answer "requires authorization".** That is the expected reply
with no key, or with one that has been revoked. Re-check the `Authorization`
header spelling — it is `Bearer ` followed by the whole `acd_live_` string.

**A generation returns a job id and nothing else.** That is correct. Generation
is submit-and-poll; call `get_generation` with the id.

See also: [the plugin overview](https://aicontentdrop.com/plugin) ·
[the MCP reference](https://aicontentdrop.com/docs/mcp) ·
[authorization](https://aicontentdrop.com/auth.md)