Included with All-Access
Bring the archive into your editor.
Connect Claude Code, Antigravity or Codex to Brand Motion over MCP. Your agent searches the archive, reads the exact prompt behind any design, and pulls a single component straight out of its source — without leaving the editor, and without downloading a whole pack to read one file.
Searching and browsing work without a key.
How it works
- 1
Create a key
On your account page. Shown once, stored hashed — revoke and remake at any time.
- 2
Add the server
One command or one config block. It is remote — nothing to install, nothing to keep running.
- 3
Ask for what you need
“Find a restaurant site with scroll-scrubbed video and show me the prompt behind it.”
Connect your editor
Replace YOUR_KEY with the key from your account page.
Claude Code
Run this once in your terminal
claude mcp add --transport http brandmotion \ https://brandmotion.in/api/mcp \ --header "Authorization: Bearer YOUR_KEY"Claude Code MCP docs ↗
Antigravity
Settings → MCP servers → edit the config JSON
{
"mcpServers": {
"brandmotion": {
"serverUrl": "https://brandmotion.in/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}
}
}Antigravity MCP docs ↗Codex
Add to ~/.codex/config.toml
experimental_use_rmcp_client = true [mcp_servers.brandmotion] url = "https://brandmotion.in/api/mcp" bearer_token_env_var = "BRANDMOTION_API_KEY"Codex MCP docs ↗
Using something else? Any client that speaks MCP over streamable HTTP works — it needs the endpoint https://brandmotion.in/api/mcp and an Authorization: Bearer header. Those two are the parts that matter.
What your agent can do
Search the whole catalogue
By intent or by stack — “hospitality”, “GSAP scroll”, “R3F configurator”.
Read the prompt behind any design
The complete build brief, verbatim, ready to hand to a coding agent.
Read one source file at a time
List the tree, then pull the single component you care about.
Get the asset-generation prompts
The Veo and Flow briefs that produced the footage, so you can make your own.
Pull the design system
design.md where a build has one, plus the colour and type tokens it uses.
Download the full pack
A short-lived signed link when you want everything, assets included.
Questions
What is an MCP server, in one sentence?
A standard way for a coding agent to call tools that live somewhere else — so instead of you pasting a prompt into the editor, the agent asks Brand Motion for it directly and keeps working.
Can I try it before subscribing?
Yes. Searching the catalogue, listing categories and reading a design's details work with no key at all — point your client at the endpoint and start asking. Prompts, source files, design systems and asset briefs are the parts that need an All-Access plan.
Where do I get my key, and what if I lose it?
From your account page, once you have a plan. It is shown exactly once and stored only as a SHA-256 hash, so nobody — including us — can recover it or read it back to you. Losing it costs nothing: revoke it and create another in two clicks.
Does it work with editors other than these three?
Any client that speaks MCP over streamable HTTP and can send an Authorization header. The three above are the ones we give exact config for; everything else needs the same two things — the endpoint URL and a Bearer token.
Does my agent have to download a whole source pack?
No. Your agent lists the file tree first, then reads only the individual files it needs, so studying one component costs one small read rather than an entire archive. When you genuinely want everything, including the video and stills, it hands back a signed download link that expires in fifteen minutes.
What happens when my plan renews, lapses or is cancelled?
Access is checked live on every call against the same record the website reads, so nothing has to be synchronised. Cancelling keeps your access until the end of the period you have already paid for, exactly as it does on the site; when that date passes, the content tools stop and the free discovery tools carry on.
Is there a rate limit?
120 calls a minute per key, which is far above normal use — it exists so a key that leaks into a public repository cannot be used to pull the whole catalogue. Every response tells your client how much headroom is left.
Can I share one key with my team?
A key is tied to the account that made it, so anyone holding it is using your plan. You can create as many keys as you like and revoke them individually, which is the better way to hand access to a machine or a CI job you might want to cut off later.