Writio
Draft, schedule, and measure LinkedIn posts from your coding agent using Writio’s API without switching to the Writio web app.
Overview
Writio is a MCP server for the Grow phase that lets agents create, schedule, and analyze LinkedIn content through Writio’s API.
What is this MCP server?
- LinkedIn-native AI content creation exposed through MCP (npm @writio/mcp-server v0.1.3)
- Post scheduling and analytics from the agent conversation
- stdio transport with WRITIO_API_TOKEN from app.writio.ai Settings → API Access
- Keeps founder distribution workflow inside Claude Code or Cursor
- Server package version 0.1.3 (@writio/mcp-server on npm)
- 1 required secret env var: WRITIO_API_TOKEN
What problem does it solve?
Shipping in the terminal while LinkedIn drafts and schedules live in another SaaS tab breaks momentum for solo founders who rely on organic distribution.
Who is it for?
Solo builders who already use or plan to use Writio for LinkedIn and want Claude Code or Cursor to handle posts and metrics via MCP.
Skip if: Builders who do not use LinkedIn, need multi-network scheduling only, or want fully offline content pipelines without a Writio account.
What do I get? / Deliverables
After you add @writio/mcp-server with a valid API token, your agent can drive LinkedIn content workflows from the same MCP session as your code.
- Agent-driven LinkedIn post creation via Writio
- Scheduled publishing controlled through MCP tools
- Access to Writio-linked analytics for post performance
Recommended MCP Servers
Journey fit
LinkedIn publishing and performance tracking compound after you ship; grow is where distribution and content rhythm matter for solo founders. Content subphase fits because the MCP surface is creation, scheduling, and analytics for LinkedIn-native posts, not paid ads or app-store ASO.
How it compares
LinkedIn-specific growth MCP, not a general SEO or codebase integration server.
Common Questions / FAQ
Who is Writio for?
Solo founders and developers who publish on LinkedIn and use Writio, and want their MCP-enabled agent to create, schedule, and review performance without leaving the IDE.
When should I use Writio?
Use it in the grow phase when you are maintaining a LinkedIn cadence, repurposing ship logs into posts, or checking analytics while planning the next release narrative.
How do I add Writio to my agent?
Create a WRITIO_API_TOKEN at https://app.writio.ai → Settings → API Access, install @writio/mcp-server (v0.1.3) as a stdio MCP server, and reference the token in your client env block.