REST API and MCP
Everything the dashboard does, from code or an AI assistant
The REST API and the MCP server run the same 87 actions as the dashboard, with the same checks: plan limits, sender rules, pre-send checks, campaigns paused for their bounce or complaint rates or Gmail's spam rate, blocked accounts and first sends in steps.
REST APIJSON in and out
https://eu.flockstack.io/api/v1MCP serverStreamable HTTP
https://eu.flockstack.io/mcp- 1
Create an API key
On the API keys page. Full access for scripts and AI assistants; signups only for signup forms in your website's code. Keys are shown once.
- 2
Make a request
Every request sends the key as a bearer token. This one lists your newsletters with their settings.
Terminal curl https://eu.flockstack.io/api/v1/newsletters \ -H "Authorization: Bearer $FLOCKSTACK_API_KEY" - 3
Or connect an AI assistant
One command for Claude Code. Codex and Cursor take a few lines, and ChatGPT, Claude and Grok Bot connect with your sign-in, on the MCP page.
Terminal claude mcp add --transport http --scope user flockstack https://eu.flockstack.io/mcp \ --header "Authorization: Bearer $FLOCKSTACK_API_KEY"
What you can do
Overview1Subscribers, email results and sends per hour, as on the dashboard's first page.Newsletters6Sender, postal address, welcome and confirmation emails, list cleanup and archive.Campaigns17Drafts, test emails, scheduling, sending, sending in steps and reports.Contacts7Search, signups, imports with checks, status changes, deletes and exports.Referrals4A referral program with rewards: settings, who referred whom, and the leaderboard.Tags and fields9Free-form tags on contacts, and custom fields (text, number, date) for merge tags, segments and automations.Segments6Saved audiences: rules over a newsletter's contacts, with live counts, that a campaign or an automation can use.Automations8Series of emails and actions that start for a contact when they subscribe, get a tag, join a segment or reach a date.Domains4Own sending domains with their DNS records, and the shared address.Payments2Whether the account can take payments, and connecting its Stripe account. FlockStack takes no cut of sales.Paid subscriptions2A newsletter's paid tier: prices, free trial and subscribers. Campaigns can go to paid readers only.Products6Digital products readers buy once: files kept private, pages on the newsletter's site, Stripe Checkout on your own account.Orders3What readers bought, who got their download link, and resending it. Refunds are made in Stripe.Images2Pictures for campaign content, on FlockStack's CDN, kept in the account's library to use again.API keys5Keys for the REST API and MCP.Billing3Plan, usage and links to Stripe to change plan.Export2Everything the account has in ZIP files: contacts, issues, images and settings. Never a paid feature.
For agents reading this
- /llms.txt lists these pages and every endpoint.
- /llms-full.txt is the whole reference in Markdown.
- /api/v1/openapi.json is the API as OpenAPI 3.1, made from the same schemas as the MCP tools.