Genfeed.ai

Ghost in Cursor, powered by Genfeed

Connect Cursor to Genfeed for Ghost. Bring your brand context, media tools, and posts into one creative workflow.

CursorGenfeedIntegration preview
A sculptural sharp silver pointer-shaped tool traces a precise path through a graphite editor-like frame and reveals a coral campaign image
Brand contextCreative toolsGhost

01 / Native Cursor install

Your tools.
Now connected.

Open the install link, confirm the Genfeed MCP server in Cursor, and sign in with Genfeed OAuth. This installs the connector; the packaged playbook is available separately in the agent repository.

Packaged Genfeed plugins already include the playbook. Use this skills-only alternative when connecting through MCP without a Genfeed plugin.

Skills-only alternative

npx skills add genfeedai/agent

Skills add the Genfeed playbook. To connect your account too, paste the setup prompt into Cursor with local shell access.

Setup prompt

Set up the Genfeed MCP server on this machine, with its agent playbook, for Cursor.

Endpoint: https://mcp.genfeed.ai/mcp
Claude endpoint: https://mcp.genfeed.ai/mcp/claude (the connector for every Claude client).
The Claude endpoint covers brands, drafts, scheduling and analytics. For image, video and audio generation in a Claude client, add the standard endpoint above as a second server named genfeed-media.
Authentication: browser OAuth (no API key required)
Setup reference: https://github.com/genfeedai/agent/blob/main/llms-install.md

Do this end to end:
1. Inspect the selected client's existing Genfeed plugins, skills, and MCP configuration. Preserve unrelated configuration and use the existing Genfeed installation when present. Set up only this client; ask which client to use if you cannot identify it.
2. For Claude Code, install the dedicated content plugin with /plugin install genfeed --marketplace genfeedai/agent (Claude Code 2.1.275 or newer). For Claude chat, Desktop, Cowork and other Claude clients, skip playbook installation and connect through their supported OAuth flow instead. Never run skills add for any Claude client. For non-Claude clients, install the Genfeed playbook with npx skills add genfeedai/agent and select only the intended client in the installer. Skip this step if the playbook is already available through an installed Genfeed plugin, extension, or standalone skill. Installing skills alone does not configure or authenticate MCP.
3. If Genfeed MCP is not already configured, add the remote Streamable HTTP server for the selected client using browser authorization:
   - Only if the selected client is Claude Code: claude mcp add --transport http genfeed --scope user https://mcp.genfeed.ai/mcp/claude
   - Only if the selected client is Codex: codex mcp add genfeed --url 'https://mcp.genfeed.ai/mcp?profile=studio'
   - For Codex only, equivalent user-level ~/.codex/config.toml:

[mcp_servers.genfeed]
url = "https://mcp.genfeed.ai/mcp?profile=studio"

For other clients, follow their supported remote MCP configuration. Claude and Cowork use the Claude endpoint, and add the standard endpoint above as a second server named genfeed-media only when the user asks for image, video or audio generation; other clients use the standard endpoint above. Do not duplicate a server provided by an installed plugin.
4. Only for Claude Code: Open /mcp inside Claude Code, select genfeed, and authenticate. Sign in and approve access in your browser, then return to Claude Code.
   Only for Codex: Run codex mcp login genfeed if authorization did not open during setup. Sign in and approve access in your browser, then return to Codex.
   For other clients, open their OAuth connection flow. Authenticate only the selected client.
5. Ask the user to complete consent in their browser. Never request tokens or passwords in this chat. If authorization is denied or expires, restart the client authorization flow.
6. Verify access with read-only get_account and get_brands calls (list my Genfeed brands); request only the profile section from get_account. A copied command, registered plugin source, or server list entry alone does not verify authorization.
7. Do not generate content, schedule, publish, or resolve approvals during setup. Report skill installation, MCP configuration, and authenticated verification separately, including any remaining user step. Claude requires OAuth. If another client does not support OAuth, direct its user to Genfeed's guided setup for the advanced manual-key path.

Genfeed connector URL

https://mcp.genfeed.ai/mcp

Sign in to Genfeed in your browser. Then ask Cursor to show your brands to check the connection.

Connect your Ghost account in Genfeed once to make it available to Cursor.

What can you ask Cursor to do on Ghost?

Ask in plain language. Genfeed holds posts for review before anything goes to Ghost.

“Turn this podcast transcript into a Ghost blog post draft.”

“Generate a featured image in our brand style for the draft.”

“Publish the approved post on Monday morning.”

Ghost content Genfeed creates

Everything Cursor can make for Ghost through Genfeed.

AI-generated blog posts with Ghost-compatible Mobiledoc formatting

Newsletter content creation with email-optimized layouts and CTAs

SEO optimization with meta titles, descriptions, and structured data

Featured image generation with AI for posts and newsletters

Tag and author management for organized content taxonomy

More about Genfeed for Ghost

Cursor and Ghost: frequently asked questions

Can Cursor post to Ghost?

Yes. Once your Ghost account is connected in Genfeed, Cursor can draft, schedule, and publish Ghost posts through the Genfeed MCP server.

Do I need a Ghost API key?

Yes, once. Genfeed connects Ghost with your Ghost Admin API key, which you add in Genfeed. Cursor reaches Genfeed over MCP with browser OAuth and never receives that key.

Does Cursor publish to Ghost without my approval?

No. Genfeed holds posts for review, and you approve before anything goes to Ghost, unless you set up a workflow that publishes directly.

How do I connect Cursor to Genfeed?

Open the install link, confirm the Genfeed MCP server in Cursor, and sign in with Genfeed OAuth. This installs the connector; the packaged playbook is available separately in the agent repository.

What URL do I connect?

Connect this client to: https://mcp.genfeed.ai/mcp.

Post to Ghost from Cursor.

Start on managed cloud, connect Ghost, then connect Cursor with the steps above.