MCP Overview
The Aims MCP server lets an AI assistant — Claude, or any MCP-compatible client — work inside your Aims account on your behalf. It can search the competitor inspiration you have already indexed, look at individual ads and posts, and create new on-brand images, videos, and social posts using the same generation pipeline the web app uses. This page explains the model so the rest of the section makes sense.
What MCP is
MCP (Model Context Protocol) is an open standard for connecting AI assistants to external tools and data. The Aims MCP server is a hosted (remote) connector: you mint a personal key in Aims, paste the server URL and key into your AI client, and the assistant gains a set of Aims-specific tools it can call during a conversation. No code, no local install — it is the same kind of connector you would add for any other MCP service.
Every request is authenticated by your key, which resolves to your Aims user. The assistant only ever sees your own brands, products, competitors, and indexed inspiration. There is no shared session and no browser involved.
Who it's for
Founders and marketers who already live in Claude and want to spin up on-brand content without switching tabs.
Agencies running several brand workspaces who want an assistant that can resolve "the skincare client" to the right brand, brief, and competitor set.
Anyone who wants to chain Aims into a larger automation — research a competitor, pick the best ad, and generate a branded version in one prompt.
The discover → inspect → copy model
Every Aims tool falls into one of a few stages, and a good workflow walks through them in order:
| Stage | What happens | Example tools |
|---|---|---|
| Discover | Find candidate inspiration that already lives in your Aims index. Free and instant. | aims_search_inspiration, aims_browse_competitor_content, aims_list_competitors, aims_add_competitor |
| Inspect | Open one asset in full so the assistant can read the copy, see the image, or "watch" the video via its transcript and scene captions. | aims_get_asset, aims_get_brand_voice |
| Copy | Generate a fresh, on-brand image, video, or post from what was inspected. | aims_copy_to_image, aims_copy_to_video, aims_recreate_post |
There is also a separate Acquisition stage for pulling NEW content into your index (discovering competitors, fetching their latest ads, or following a subreddit). Those tools cost money on every call, so they sit behind a daily cap — see "Criteria & Credits."
Read and search are free; pulls and generation are not
Two cost models run side by side, and understanding the split is the single most important thing about the server:
Discovery and inspection (search, browse, list, get-asset, get-brief) read content that is already in Aims. They are free, instant, and never trigger an external fetch.
Acquisition tools (discover competitors, pull content, follow a social source) trigger a billed external fetch on Aims' upstream accounts. They are limited by a per-user DAILY cap, separate from your credit balance.
Create tools (copy to image / video, recreate post) auto-spend credits from your balance, exactly like generating in the web app.
Prefer what you already have
Searching and browsing your existing index is free and fast, so a well-behaved workflow exhausts that first and only reaches for a billed pull when the content genuinely is not there yet. The prompts that ship with the server are written to do exactly this.
Ready to connect? Head to "Connect to Claude." Want the full menu of tools first? See the "Tool Reference."
Can't find what you need?
Our support team is ready to help with any questions.