Connect your dedicated Flocksy team to Claude or any MCP-capable assistant. Your agent files the project, answers questions and pulls the final files. Real designers do the work.
Your AI assistant writes the brief, watches the project and sends feedback. Your dedicated Flocksy designers, video editors and motion editors make the work.
It is the same team, the same flat monthly price and the same hours. Now you can reach them from the assistant you already talk to all day.
Email has an API. Ads have an API. Creative production never had one. Until now.
The moment your workflow needed a real design, you had to leave the chat, open a browser and type the brief yourself. The People API lets your agent finish the job instead of stopping short of it.
In your Flocksy account, go to Settings, API Keys. Choose view-only or allow-changes and an optional expiry. The key is shown once, so copy it somewhere safe.
In Claude, go to Settings, Connectors, Add custom connector, or use any MCP-capable assistant. Paste your connection URL and put the key in the Authorization header.
"Brief Flocksy on three LinkedIn ads for our spring launch, main brand." Your agent files the project and your dedicated team takes it.
"mcpServers": {
"flocksy": {
"url": "<CONNECTION URL from Settings → API Keys>",
"headers": {
"Authorization": "Bearer flk_live_..."
}
}
}Your key belongs in connector settings or server code. A chat is not a safe home for a credential, and a key in a URL is rejected outright.
whoamiSee your organization, plan, Daily Hours and what this key is allowed to do.list_brand_bucketsSee the brands your team already knows, with colors and fonts, so every brief stays on brand.list_projectsSee every request and where it stands, newest first, filtered by status.get_projectRead the brief, the status, the latest 20 comments with names, and the delivered file list.get_delivery_linksGrab signed download links for delivered files. Each link expires in 15 minutes.create_projectBrief the team: title, type, brief, deliverables, sizes, brand, references and a needed-by date.add_commentAnswer the designer's question in the project thread. The assigned team is notified.request_revisionSend precise feedback and move the project to revision requested.approve_projectApprove the delivered work and mark it complete."Brief Flocksy on three LinkedIn ads for our spring launch. Use the main brand, 1200x1200, needed by Friday."
"What's in progress with Flocksy right now, and is anyone waiting on an answer from us?"
"On the spring LinkedIn ads, ask the designer to make the headline larger and swap the photo for the product shot."
"The spring ads look right. Approve them and give me the download links."
Claude. Add Flocksy as a custom connector and brief from the chat you already use.
Any MCP-capable assistant. MCP is the open standard for connecting AI tools, so the same URL and key work anywhere custom connectors are supported.
Your own website or app. Call the same nine tools from your server with a Bearer token, so your forms post briefs straight to the team.
Keys are random, 40 characters, and stored only as a SHA-256 hash. Nobody, including Flocksy, can read a stored key back.
A key is locked to exactly one organization. Organization ids are never taken from the request, so an agent cannot ask for anyone else's work.
A view-only key that tries to write is refused with "This API key is read-only."
Only owners and admins create or revoke keys, up to 20 active keys per organization.
Set an optional expiry from 1 to 730 days. Revoke instantly. Owners and admins get an email on every create and revoke.
A key stops working if the teammate who created it is deactivated or loses admin. Access follows the team, not a shared credential.
Every call is logged with tool, success, error and IP. Each key is limited to 60 requests per minute.
Every action is attributed to the named teammate who created the key and lands in the same project thread your team already reads.
Plans start at $1,199/mo billed yearly. Unused hours roll over, and you can cancel anytime. Rated 4.9 on G2 and TrustPilot.
Competitor prices from their published pricing pages, verified September 24, 2026; offerings may change. Flocksy is not affiliated with Designity or Superside.
Brands have worked with Flocksy since 2016. A model guessing your brand from context is not the same as a team that already holds your colors, fonts and past work.
No. Your AI assistant writes the brief, follows up and pulls the final files. Your dedicated Flocksy designers, video editors and motion editors do the creative work.
Yes. The People API needs an active subscription or trial. Without one, it returns "Organization has no active subscription." API requests draw on your Daily Hours like any other request, and unused time rolls over.
Only organization owners and admins can create or revoke keys, with up to 20 active keys per organization. Keys are created in your Flocksy account under Settings, API Keys.
In your AI tool's connector settings or in your server code, sent in the Authorization header. Never type a key into a chat, and never put it in a URL. A key in a URL is rejected outright.
It stops working immediately. Owners and admins are emailed whenever a key is created or revoked. A key also stops working if the person who created it is deactivated or loses admin access.
Only if you allow it. A view-only key can read but cannot change anything. An allow-changes key can create projects, comment, request revisions and approve delivered work. Start view-only and upgrade when you are comfortable.
Your agent can only brief project types your plan includes. If it asks for one that is not included, it is told what your plan does include.
No. Real people do the work, so turnarounds take hours and days, not seconds. The server tells your assistant that work is asynchronous, so it reports back instead of waiting. You still set needed-by dates.
Unused hours roll over. Cancel anytime. Backed by a 14-day money-back guarantee.