Ship your blog from the editor you already code in.
Add Quillly to Cursor’s MCP and let the agent write changelogs, docs, and SEO posts to your domain — the same flow you use to ship code.
14-day free trial · No card · ~3 hours saved per post
Draft a launch post for v2.0 from the CHANGELOG and publish it to our blog.
Reading the changelog, writing the post, linking to the relevant docs, then publishing.
Used 5 Quillly tools — researched, drafted, SEO-scored, linked & published
Shipped “What’s New in v2.0” — 89/100 SEO, links to 4 docs pages, indexing requested.
Connect Cursor to Quillly
Paste once. After that, you just talk to Cursor like normal.
Connect Cursor
Three steps. ~30 seconds.
Heads up: Any Cursor plan. Project-level .cursor/mcp.json works too.
- 1Settings (Cmd/Ctrl+Shift+J) → MCP → Add server
- 2Or paste the JSON above into ~/.cursor/mcp.json
- 3Approve Quillly when prompted — tools load on the next agent run
~/.cursor/mcp.json
{
"mcpServers": {
"quillly": {
"url": "https://quillly.com/api/mcp"
}
}
}Why Cursor users pick Quillly
Zero context switch
Write release notes and blog posts in the same window you write code. No CMS tab, no second tool.
Changelog → post, automatically
Point the agent at your CHANGELOG, commits, or PRs and let it draft the announcement, then publish it.
Built for technical content
Code blocks, callouts, and internal links survive intact — none of the formatting loss a CMS introduces.
Agent mode does the whole loop
Research, draft, SEO-score, fix, publish — all as tool calls in one agent run you can review.
Everything Cursor can do with Quillly
Say it in plain English and Cursor runs it mid-conversation — no dashboard, no commands to memorize.
0 capabilities under the hood — publishing, SEO, analytics, images, planning. No AI? The dashboard does all of it too.
Cursor + Quillly questions
Where does the MCP config go?
Global config lives at ~/.cursor/mcp.json (applies everywhere). For a single repo, use a project-level .cursor/mcp.json so only that workspace sees Quillly.
Does it work in Cursor’s agent mode?
Yes — that’s the point. In agent/Composer mode Cursor calls Quillly’s tools autonomously, so “write and publish a post” becomes a single instruction.
Will it touch my codebase?
No. Quillly’s tools only read and write your blogs on Quillly. Cursor edits files; Quillly publishes content — they don’t overlap.
Everything, in one simple plan.
Start with a 14-day free trial — no card required. Then $9/month for unlimited blogs, full SEO, and publishing straight from your own AI. Saves ~3 hours of manual work per post.
Pro
Everything in Quillly.
or $96/year (save $12)
14-day free trial · no card needed
- Connect up to 5 websites
- Unlimited blogs
- Unlimited traffic
- Full analytics (90-day retention)
- GSC integration
- SEO audit & scoring
- Full MCP capabilities
- Custom CSS theming
- Branding settings
- Scheduled publishing
- Priority support
Cancel anytime. Your content stays on your domain — you own everything you publish.
“Went from 4 hours per blog to literally one prompt. The SEO score is the unlock — I can see exactly why my old posts under-ranked.”
Marcus L.
Indie SaaS founder
“I run blogs for 5 client sites. One-click switching, each on its own domain with its own analytics — and publishing straight from chat is the part my team loves.”
Priya N.
Agency owner
“The reverse-proxy setup looked scary — turns out it's one rewrite rule. Live in 12 minutes including SSL.”
Tom K.
Solo developer
“Internal linking is the killer feature for me. Every new post automatically suggests links into older posts — my topic clusters finally make sense.”
Sarah R.
Content lead, B2B
“I keep two windows open: Claude on the left, Quillly dashboard on the right. I literally watch the SEO score climb while it edits.”
Dev A.
Bootstrapped founder
“We had GSC connected within 30 seconds of finishing onboarding. Top-query data already feeding our content calendar.”
Aria F.
Marketing manager
“Went from 4 hours per blog to literally one prompt. The SEO score is the unlock — I can see exactly why my old posts under-ranked.”
Marcus L.
Indie SaaS founder
“I run blogs for 5 client sites. One-click switching, each on its own domain with its own analytics — and publishing straight from chat is the part my team loves.”
Priya N.
Agency owner
“The reverse-proxy setup looked scary — turns out it's one rewrite rule. Live in 12 minutes including SSL.”
Tom K.
Solo developer
“Internal linking is the killer feature for me. Every new post automatically suggests links into older posts — my topic clusters finally make sense.”
Sarah R.
Content lead, B2B
“I keep two windows open: Claude on the left, Quillly dashboard on the right. I literally watch the SEO score climb while it edits.”
Dev A.
Bootstrapped founder
“We had GSC connected within 30 seconds of finishing onboarding. Top-query data already feeding our content calendar.”
Aria F.
Marketing manager
“Went from 4 hours per blog to literally one prompt. The SEO score is the unlock — I can see exactly why my old posts under-ranked.”
Marcus L.
Indie SaaS founder
“I run blogs for 5 client sites. One-click switching, each on its own domain with its own analytics — and publishing straight from chat is the part my team loves.”
Priya N.
Agency owner
“The reverse-proxy setup looked scary — turns out it's one rewrite rule. Live in 12 minutes including SSL.”
Tom K.
Solo developer
“Internal linking is the killer feature for me. Every new post automatically suggests links into older posts — my topic clusters finally make sense.”
Sarah R.
Content lead, B2B
“I keep two windows open: Claude on the left, Quillly dashboard on the right. I literally watch the SEO score climb while it edits.”
Dev A.
Bootstrapped founder
“We had GSC connected within 30 seconds of finishing onboarding. Top-query data already feeding our content calendar.”
Aria F.
Marketing manager
“Went from 4 hours per blog to literally one prompt. The SEO score is the unlock — I can see exactly why my old posts under-ranked.”
Marcus L.
Indie SaaS founder
“I run blogs for 5 client sites. One-click switching, each on its own domain with its own analytics — and publishing straight from chat is the part my team loves.”
Priya N.
Agency owner
“The reverse-proxy setup looked scary — turns out it's one rewrite rule. Live in 12 minutes including SSL.”
Tom K.
Solo developer
“Internal linking is the killer feature for me. Every new post automatically suggests links into older posts — my topic clusters finally make sense.”
Sarah R.
Content lead, B2B
“I keep two windows open: Claude on the left, Quillly dashboard on the right. I literally watch the SEO score climb while it edits.”
Dev A.
Bootstrapped founder
“We had GSC connected within 30 seconds of finishing onboarding. Top-query data already feeding our content calendar.”
Aria F.
Marketing manager