GrowFlux
Turn product updates into channel-ready copy and visuals through GrowFlux’s authenticated MCP workflows.
Hosted MCP Server
npx add-mcp 'https://mcp.growflux.io'Installs into Claude Code, Codex, Cursor and more
Documentation
Connection details
| Setting | Value |
|---|---|
| Server URL | https://mcp.growflux.io |
| Transport | Streamable HTTP, JSON-RPC 2.0 over POST |
| Protocol version | 2025-11-25, with compatibility for supported earlier clients |
| Authentication | Standard MCP OAuth discovery and browser sign-in |
Your client must support remote HTTP MCP servers and OAuth browser sign-in. A client that can only launch local command servers cannot use this endpoint.
Client configuration
Add the GrowFlux server URL to a compatible client. The client discovers the GrowFlux authorization service, opens a browser sign-in, and asks you to choose the workspace and permissions. You do not need to copy a secret.
{
"mcpServers": {
"growflux": {
"type": "http",
"url": "https://mcp.growflux.io"
}
}
}
Client configuration formats vary, but the server URL stays the same. Scoped API keys remain available under advanced settings for CI, service accounts, and older clients that cannot complete browser authorization.
Approve only the permissions you need
| Need | Typical permissions |
|---|---|
| Discover projects and workflows | projects:read |
| Run and observe workflows | runs:write, runs:read |
| Read or decide reviews | review:read, optionally review:decide |
| Publish approved content | publish:write |
| Read performance evidence | metrics:read |
GrowFlux shows these permissions in plain language before you approve the browser connection. Start with discovery and observation; add write or publishing access only when the Agent genuinely needs it.
Verify the connection before you rely on it
A client can show a server as added and still fail on the first real call. Check the connection with a read-only step before you ask for work that runs, reviews, or publishes content.
-
Finish the browser sign-in
Approve the workspace and only the scopes you intend to use. Closing the browser before approval leaves the client without a usable session. -
Read the capability guide
Ask the assistant to fetch the current GrowFlux capability guide. It should return the capabilities and boundaries that apply to your connection. -
List the projects you can access
A project list means the connection reaches the workspace. A successful empty list means no projects are visible to this connection, which is a valid result. Check that you selected the intended workspace if you expected projects. -
Treat discovery as discovery
Reading projects proves the connection works. It does not grant permission to run, review, or publish. Those remain separate scopes with their own confirmation.
Illustrative result · not live workspace dataExample
Projects returned2 projects
- Summer launch read only
- Evergreen content read only
Empty workspace0 projects
No projects yet
The connection works. Create a project in the app, or ask the assistant to prepare a first-project proposal for your confirmation.
An empty project list is not a connection failure. If the workspace has no projects yet, create one in the app or ask the assistant to prepare a first-project proposal for your confirmation.
Troubleshooting
| What you see | Likely cause | Next step |
|---|---|---|
| The client cannot add the server, or says the transport is unsupported | It only supports local command servers. | Use a client that supports remote HTTP MCP. A scoped API key does not add transport support. For an HTTP-capable client that cannot complete OAuth, check the advanced scoped API key configuration. |
| The client asks you to authorize again, or returns an invalid or expired session | Browser sign-in was not completed, or the session expired. | Run the client's authorization flow again, sign in to the same workspace, and approve the scopes you need. |
| A read or run is denied even though the connection works | The approved scopes do not include that permission. | Re-authorize with only the permission the task needs. Do not add publishing access to work around a read error. |
Do not disable review or widen permissions to make an error disappear. If a tool reports success but returns no content, read the capability guide and list projects again before you re-authorize. Exact tool names and response fields are available from tools/list.
Available tool groups
- Agent guide, project, workflow path, version, manifest, and delivery-route discovery.
- Saved content routines and coordinated run-group operation.
- Create, inspect, revise, compare, and keep durable Results.
- Approved production run start and status/event observation.
- Review decisions, exports, publication metrics, and workflow validation.
Exact tool schemas are returned by MCP tools/list. Agents should discover them rather than relying on a copied static list.
Current boundary
MCP can create or resume a first-project setup, preview the exact proposal, and—after explicit confirmation—commit a paused project with its first workflow. It cannot silently activate, schedule, connect a social account, spend on testing, or publish. Those remain separate permission and confirmation steps. The MCP Worker is a protocol adapter and does not access the application database directly.
Questions
How do I know the connection really works?
Run a read-only check: read the capability guide, then list the projects the workspace can access. A project list, or an explicit empty list, means the connection reaches GrowFlux. A connected label in the client is not enough on its own.
What does an empty project list mean?
A successful empty list means no projects are visible to this connection. Check the selected workspace and access if you expected projects. If this is a new workspace, create a project in the app or confirm a first-project proposal from the assistant.
Is the MCP endpoint public?
The server URL is public, but every workspace action requires an approved browser authorization or, for advanced compatibility, a valid scoped GrowFlux API key.
Does the Agent see provider secrets?
No. Provider and channel credentials stay in GrowFlux. MCP receives governed capability and status projections rather than raw stored secrets.
Should I grant every scope?
No. Start with read-only discovery scopes and add run, review, or publishing permissions only when the Agent genuinely needs them.
Is a successful tool response proof of publication?
No. Publication requires destination-specific delivery evidence; connection health and accepted scheduling intent are separate states.