Hashnode MCP server: manage your blog from Claude, ChatGPT, and Cursor

Connect once with your Hashnode login. Publish, draft, edit, search, and upload images without leaving your chat.

Ipseeta Priyadarshini14 hours ago4 min read

What is the Hashnode MCP server?

The Hashnode MCP server lets Claude, ChatGPT, Cursor, and other AI clients publish, draft, edit, search, and delete posts on your Hashnode blog. Add one URL, log in with your Hashnode account, and you're connected. No API token, nothing to install.

https://mcp.hashnode.com/mcp

How to connect

In Claude Code, run one command:

claude mcp add --transport http hashnode-mcp https://mcp.hashnode.com/mcp

Your browser opens Hashnode. Log in and approve access. That's it.

In Cursor, add the URL to your mcp.json:

{
  "mcpServers": {
    "hashnode": {
      "url": "https://mcp.hashnode.com/mcp"
    }
  }
}

In ChatGPT and other clients, paste the same URL wherever the client asks for a remote MCP server.

What your agent can do

Ask in plain language. "Publish notes.md to my blog." "Save notes.md as a draft." "Submit it for review." "Find my posts about Postgres and fix the tags." "Use cover.png as the cover image." "Credit Priya as the author." Your agent picks the right tool.

There are 32:

Tool	What it does
`create_post`	Publish a new post
`update_post`	Edit an existing post
`delete_post`	Delete a post
`create_draft`	Save a new draft without publishing
`update_draft`	Edit a draft
`get_draft`	Read a draft
`list_drafts`	List your drafts in a publication
`publish_draft`	Publish a draft as a post
`delete_draft`	Delete a draft
`submit_draft_for_review`	Submit your draft to the owner and admins for review
`reject_draft_submission`	Send a submitted draft back to its author
`list_submitted_drafts`	See drafts waiting for review
`list_all_drafts`, `list_scheduled_drafts`, `list_all_scheduled_drafts`	See everyone's drafts, or the ones scheduled for later
`get_post`, `get_post_by_slug`	Read a post by id or by slug
`list_posts`	List your publication's posts
`search_posts`	Search your publication's posts
`list_series`, `get_series`	Browse your series
`list_members`	See who's on your publication
`list_publications`, `get_publication`	Find the publications you own and read their details
`list_static_pages`	Read a publication's static pages
`list_comments`, `top_commenters`	Read a post's comments, or see who comments most
`create_image_upload_url`, `confirm_image_upload`	Upload a local image
`whoami`, `get_user`, `get_tag`	Look up yourself, another user, or a tag

You stay in control

You never handle a token. Every client you connect shows up in Developer Settings, and you can disconnect any of them at any time. Access stops immediately.

MCP server or agent skill?

If you work in a coding agent and want the whole GraphQL API, use the GraphQL skill. If you work in a chat client, or you'd rather not manage a token, use the MCP server. Both follow the same Pro rules, and you can use both.

Before you publish

Posts go live immediately. To look first, ask your agent to save a draft, then publish it when you're ready.
Contributors can't publish directly. Ask your agent to submit your draft for review, and an owner or admin publishes it.
Deleting a post removes it from your blog, and the API can't bring it back. Only the author or a publication admin can delete.