[ Layers for agents ]
Marketing infrastructure for your agent
The department that runs on the Layers platform, exposed as a plugin, an MCP server, and a REST API. Install it into Claude Code, Codex, Cursor, or Lovable and the agent that builds your product markets it too.
Your agent asks · Layers executes · the numbers come back
Install it where your agent lives
Four surfaces, one department underneath. Pick the one your agent already works in.
One command in Claude Code
The official Layers plugin bundles the MCP server with a set of marketing skills, and Claude Code activates the right one on its own. Ask it to launch a campaign and it reaches for Layers the way it reaches for your test suite.
Add Layers to Codex
One command registers the Layers MCP server and Codex gets the full toolset: create content, schedule posts, launch campaigns, read performance. Add the skills pack with npx skills add layers/layers-skills and it learns how a marketing department actually operates.
Drop the MCP into Cursor
Paste one block into .cursor/mcp.json and every Layers tool shows up right in the composer. Your marketing lives in the same window as your code, so shipping the feature and announcing it become the same session.
Prompt it into Lovable
Lovable builds your app; Layers markets it. Paste one prompt and Lovable wires your app to the Layers API and stores your key as a secret, so your product ships with a marketing department from day one.
Prompt for Lovable
Add Layers to this app. Store my LAYERS_API_KEY as a secret, then post a launch update to my social accounts whenever I ship.
Ask your agent to…
Once Layers is installed, marketing is just another thing you say to your agent.
Social
“Post the launch video to TikTok and Instagram at the best times this week.”
UGC
“Find 20 creators in the fitness niche and draft outreach for each one.”
Ads
“Pull yesterday's ad performance and pause anything below breakeven.”
Community
“Reply to every comment on my latest post in my brand voice.”
Testing
“Generate 10 hook variations for this ad and schedule an A/B test.”
Strategy
“How are we pacing to 100k views, and what should we change?”
One surface underneath
The plugin, the skills, and the prompts all ride the same MCP server and public API. Build on whichever layer fits.
Model Context Protocol
MCP server
Point Claude, Codex, or any MCP client at Layers and it gets first-class tools for social, paid media, UGC, and measurement. Your agent runs the marketing; Layers is the backend.
REST + webhooks
Public REST API
An HTTP API for everything Layers does: create content, schedule posts, launch campaigns, read performance. Typed, paginated, predictable.
Real-time
Event webhooks
Subscribe to lifecycle events: a post goes live, a campaign shifts budget, a metric crosses a threshold. Drive your own workflows in response.
Give your agent a marketing department
Install the plugin, hand it the goal, and review what ships.
1.0 Goal
One goal, and a department pointed at it
Learn more
2.0 Elle
The strategist who runs the department
Learn more
3.0 Loops
Campaigns end. Loops compound.
Learn more
4.0 Social
Organic reach, run as a loop
Learn more
5.0 Ads
Agentic ads, optimized to installs
Learn more
6.0 Measurement
The source of truth for every loop
Learn more