MCP and Flux API | Query data with AI
Login
Try free for 7 days

Query Flux through API or AI, with MCP

Pull projects, posts, and approvals out of Flux, through an external system or by asking an AI assistant in natural language.

Start your free 7-day trialLearn about Flux

First version, read-only. You still can't create, edit, schedule, or approve posts through these integrations.

Two ways to reach the same data

The API lets an external system query Flux on a schedule. An agency could, for example, pull projects, posts, and approvals into an internal dashboard, or automate a daily check of what's still waiting for approval.

MCP connects Flux to AI assistants, like Claude Code, so you can ask for the same information in natural language, without opening the Flux dashboard or building an integration of your own.

What you can ask through MCP

Y

Which posts are waiting for approval this week?

AI

5 posts waiting for approval.
2 from Padaria Aurora, 2 from Cotta Studio, and 1 from Loja XPTO. The Padaria Aurora post has been stuck for 3 days, waiting on Ana Lima's review.

"What's scheduled for the Padaria Aurora client?""Is any project missing a connected social account?""Which posts got requested changes?""Who still needs to approve tomorrow's posts?"

What you can already query

Both the API and MCP give access to the same information, in this first version:

  • Projects: projects available on the account and their connected networks.
  • Posts: posts, captions, media, status, and scheduling or publish dates.
  • Approvals: number of approvals, requested changes, and pending reviewers.
  • Approval history: who approved, who requested changes, and the comments logged.
  • Approval groups: posts grouped for review and the progress of each one.
  • Social accounts: connected, disconnected, or expired accounts.
  • Multi-network content: different versions of the same content published across more than one network.

How to turn it on

  1. Go to settings

    Inside Flux, go to Company settings, then API.

  2. Pick your option

    Integration guide to connect an AI assistant through MCP, or Create token to use the API.

  3. Follow the steps

    Connect your assistant or system and start querying.

Before you use it

  • In this first version, the API and MCP are read-only. Creating, editing, scheduling, or logging approvals is still done inside Flux.
  • Each key is limited to 120 requests per minute.
  • Media links returned expire after 48 hours.

Documentation for developers

The full setup guide, with request examples, is available for whoever implements the integration.

API documentation ↗MCP integration guide ↗

More organization to create, approve, and publish.

More than 10,000 companies use Reportei. Check out Flux and organize your team's content routine.

Start your free 7-day trialLearn about Flux

Frequently asked questions

Can I create or edit posts through the API or MCP?

Not in this first version. Both integrations are read-only. Creating, editing, scheduling, or approving posts is still done inside Flux.

What's the usage limit?

Each key is limited to 120 requests per minute.

Do the media links returned last forever?

No. They expire 48 hours after being generated.

Which AI assistants work with Flux's MCP?

Any assistant compatible with the Model Context Protocol, like Claude Code. The integration guide inside Flux walks you through the connection.

Do I need to build something to use the API?

Yes, the API is for anyone with their own system, dashboard, or automation that will consume Flux's data. If you just want to query in natural language, MCP is the simpler path.

Explore Flux

☰