Do I need the plugin, or does the deeplink alone work?

The deeplink alone connects the MCP server and every tool call works. The plugin adds the two skills and the editorial rule to your project context; without it you can still ask the agent to follow the same steps by hand.

Does mcp.json go in the project or globally?

Either: `~/.cursor/mcp.json` applies to every project you open, `.cursor/mcp.json` inside the blog's repository scopes it to that one.

Where does an approved draft land?

As a Markdown file with draft: true, committed to the git repository your workspace delivers to. If that is the repository Cursor has open, a git pull brings it next to the posts it references.

Cursor writes posts where your blog's code already lives.

Cursor reaches seodraft the same way any MCP client does: a deeplink or a line in mcp.json, then OAuth through Clerk. What is different in Cursor is the plugin: the same repository that carries the MCP config also carries two Agent Skills and one editorial rule, so the model can load them from your project when the task is blog content. When seodraft delivers to the same repository your editor has open, the approved draft arrives as a commit with draft: true, and a git pull puts it next to the post files it references.

Create account Create account

7 days free, no card needed. Then $5/month if you subscribe.

What runs inside Cursor

Cursor adds the server itself once you follow the deeplink or edit mcp.json; you sign in to seodraft when the OAuth screen opens, and Cursor stores the session, so you never paste an API key or a client ID.

The plugin from github.com/ch0rch/seodraft-agents adds getting-started-seodraft and seodraft-content-desk under skills/, plus rules/seodraft-editorial-standards.mdc. Cursor can load the skills and apply the rule when you work on blog content, so you do not retype the sequence in chat.

Because the rule already states the checks, run_gate confirms the same things the model was told before writing: one primary keyword, three pieces of your accepted evidence, an answer under every heading, no filler intro. After two failed redrafts it stops.

Connect Cursor

The deeplink and the manual mcp.json entry do the same thing; the plugin is the extra step that brings the skills and the rule in.

1
One-click install Follow the deeplink; Cursor opens its MCP settings with the seodraft server pre-filled and asks you to confirm.
Add seodraft to Cursor
2
Or edit mcp.json by hand Global config applies to every project; project config keeps it scoped to the blog's repository.
```
{
  "mcpServers": {
    "seodraft": {
      "url": "https://seodraft.app/mcp"
    }
  }
}
```
3
Sign in Cursor opens the OAuth screen for seodraft.app; sign in once and Cursor keeps the session for later calls.
4
Install the plugin for the skills and the rule For local testing, copy the repository into the plugins folder and reload the window.
```
cp -r seodraft-agents ~/.cursor/plugins/local/seodraft
# Command Palette: Developer: Reload Window
```

After connecting

The seodraft home switches from waiting to connected only when the first authenticated tool call lands. Ask the agent to read your profile or list saved keywords to trigger it.

With the plugin installed, opening a chat in the blog's repository is enough for the model to know the sequence: profile, topics with measured or estimated volume, a SERP brief, a draft that cites only accepted evidence, the checks, your approval, then delivery. A delivered draft is a commit in your blog's repository; pull it and it sits next to the posts it links to.

Limits of this client

The plugin is a local install: `~/.cursor/plugins/local/seodraft` only works on the machine you copied it to, and a teammate needs their own copy or the same repository cloned.
The deeplink and mcp.json connect the server only. The skills and the rule arrive with the plugin, as a separate step.
The MCP connection carries no memory of your editor's open files; seodraft only sees what a tool call sends it, so evidence and profile details still come from your answers.

Questions about Cursor

Do I need the plugin, or does the deeplink alone work?: The deeplink alone connects the MCP server and every tool call works. The plugin adds the two skills and the editorial rule to your project context; without it you can still ask the agent to follow the same steps by hand.
Does mcp.json go in the project or globally?: Either: `~/.cursor/mcp.json` applies to every project you open, `.cursor/mcp.json` inside the blog's repository scopes it to that one.
Where does an approved draft land?: As a Markdown file with draft: true, committed to the git repository your workspace delivers to. If that is the repository Cursor has open, a git pull brings it next to the posts it references.

Listed on

GitHub · seodraft-agents

Other agents

Claude · A skill for the workflow, an MCP connection for the data behind it.
ChatGPT · Connect seodraft as a ChatGPT app through developer mode.
Grok Bot · A ready-made template that carries seodraft's two skills, then walks you through connecting the server.
Agents · Other MCP clients

Agents hub · Every client seodraft runs in.
MCP server · The one connection every client, including Cursor, calls.
CMS delivery · Where an approved draft lands as a file with draft: true.
AI crawlers checker · Free check of which AI bots your robots.txt lets in.
Pricing · $5/month or $50/year, a 7-day trial with no card.