AI Content Drop in Cursor

Cursor reads MCP servers from an mcp.json file — one at ~/.cursor/mcp.json for every project, or one at .cursor/mcp.json inside a project for just that repo.

Add the server


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

Reload Cursor. The server should appear in the MCP settings pane with 42 tools. If your Cursor version lists MCP servers under a different settings surface, the file above is still what it reads.

Use the project-scoped .cursor/mcp.json when a repo has its own key, and the home-directory one when you want the connection everywhere. Add the project-scoped file to .gitignore before you put a key in it.

Verify without a credential

Ask the agent:

> List the AI Content Drop image models that cost 5 credits or fewer.

That is list_models, which needs no key. Model ids and costs coming back means the connection works.

Authorize

Create a key in Settings → Integrations, then add it as a header:


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

That unlocks generate_video, generate_image, get_generation, list_generations and get_account.

Working in the editor

The useful pattern is to let the agent do the pricing before the spending:

> Read the product copy in this file, write a 9:16 ad prompt from it, quote what > the cheapest capable model would cost, and wait for me to confirm before > generating.

estimate_credit_cost returns the exact number and a quote_id, valid for 15 minutes. The generation call requires that quote_id and is refused if the price or the parameters no longer match it, which is the protection you want when an agent is choosing the model itself. A retry with the same quote_id returns the original job rather than a second charge.

Troubleshooting

Cursor shows the server as failed. Check the JSON parses; a trailing comma is the usual cause. Then confirm the URL has no trailing slash.

Tools are listed but every call returns "requires authorization". Only the five account tools need the key. If the four public ones are also failing, the headers block is likely malformed — remove it and confirm the public tools work before adding it back.

You want the agent to read guides but never spend. Point it at https://aicontentdrop.com/mcp/docs instead: two tools, no credential, nothing that can bill.