Flowcontent
Let your agent read and manage FlowContent assets from Claude or Cursor instead of copying drafts in and out of the dashboard.
Overview
FlowContent MCP is a MCP server for the Grow phase that connects your agent to your FlowContent account via API token for content workflows inside Claude or Cursor.
What is this MCP server?
- npm package @flowcontent/mcp-server version 0.1.1 with stdio transport
- Requires FLOWCONTENT_API_TOKEN (fc_xxx) secret in MCP environment
- Bridges any MCP client to your FlowContent account APIs
- Published as io.github.Mahfod-dev/flowcontent in the MCP registry manifest
- Keeps content operations inside the agent loop for newsletters, posts, or managed editorial queues
- npm identifier @flowcontent/mcp-server version 0.1.1
- Required env FLOWCONTENT_API_TOKEN (secret)
- Transport stdio
What problem does it solve?
You waste time copying content between your AI coding session and a separate FlowContent dashboard.
Who is it for?
Solo builders already on FlowContent who want agent-driven drafting, updates, and content ops from their IDE.
Skip if: Builders without a FlowContent account, offline-only editorial stacks, or teams that only need generic markdown files in git.
What do I get? / Deliverables
After configuring @flowcontent/mcp-server with FLOWCONTENT_API_TOKEN, your agent can operate on FlowContent data directly through MCP tools.
- Agent-driven reads and writes against FlowContent via MCP tools
- Less manual copy-paste between IDE and content dashboard
Recommended MCP Servers
Journey fit
Grow is where solo builders systematize content pipelines after the product exists and distribution needs steady output. Content is the natural shelf because the MCP server authenticates to FlowContent and exposes that platform’s workflows to the agent.
How it compares
Hosted FlowContent account MCP connector, not a standalone SEO research skill.
Common Questions / FAQ
Who is FlowContent MCP for?
Growth-minded solo builders using FlowContent who want Claude Code, Cursor, or similar clients to interact with their content library via MCP.
When should I use FlowContent MCP?
Use it during grow and content subphase work when you batch posts, newsletters, or lifecycle copy and want the agent to read or update FlowContent without manual export.
How do I add FlowContent MCP to my agent?
Install @flowcontent/mcp-server from npm, add it as a stdio MCP server, and set the required secret environment variable FLOWCONTENT_API_TOKEN to your fc_xxx token from FlowContent.