Hashnode MCP for AI. Publish and edit content without leaving your agent.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Hashnode MCP lets you manage your entire blog from within your AI agent conversation. You can fetch user profiles, read full articles, list posts from any publication feed, and publish or update content without leaving your writing environment.
What your AI can do
Create post
Publishes a brand new blog post with Markdown content directly to your Hashnode site.
Get post
Fetches the full text and metadata of a single article using its slug.
Get publication posts
Lists recent articles published by an entire blog publication feed.
Fetch specific details and follower counts for any user on the Hashnode platform.
Get a list of recent posts from an entire blog publication, using only its domain name.
Fetch the complete text and metadata for any single post by providing its unique slug.
Write a new blog article in Markdown format, and then publish it directly to your Hashnode site.
Update the title or body content of an already published article without logging into the admin panel.
Ask an AI about this
Waiting for input…
Hashnode MCP: 5 Tools
These five tools let you perform every major action needed for blogging—from fetching user data to publishing final drafts.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Hashnode on VinkiusCreate Post
Publishes a brand new blog post with Markdown content directly to your Hashnode site.
Get Post
Fetches the full text and metadata of a single article using its slug.
Get Publication Posts
Lists recent articles published by an entire blog publication feed.
Get User
Retrieves profile details for a specific Hashnode user using their unique handle.
Update Post
Modifies the title or body of an existing published article on your Hashnode account.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Hashnode, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Hashnode. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 5 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The Old Way: Jumping Between Tabs
Right now, getting a new article published feels like a three-act play. You write the draft in your chat client, then you copy everything into a local markdown file just to check it. Then you have to switch context entirely and log into the Hashnode dashboard—all before you can hit publish.
With this MCP, that whole process collapses back into the conversation. Your agent sees the raw content, figures out the slug, and executes `create_post` for you. You get a confirmation message; your article is live.
Publishing Content with Hashnode
The manual steps that disappear are the login dance, the copy-paste cycle between editors, and manually figuring out which slug corresponds to which post. You don't touch any of those things anymore.
You simply tell your agent what needs updating or creating. It handles the entire backend process with a single call—like `update_post` or `create_post`. Period.
What your AI can actually do with this
Got a technical article idea? Instead of opening the Hashnode dashboard, drafting in one tool, then copying everything over to another editor, you just tell your AI agent what you want. This connector handles it all. You can ask for details about any user profile using their handle, or list out recent posts from an entire publication feed before writing a follow-up piece.
Need to publish? You write the Markdown right in the chat, and this MCP publishes the post directly. If you spot an old article that needs tweaking, you don't need to jump through three sets of admin menus; you just tell your agent to update it. It’s all about keeping the focus on writing, not context switching.
Connect Hashnode via Vinkius and keep your publishing workflow inside your preferred AI client.
019e38a6-60d2-7023-a4e1-a0a70192b4c7 Here's how it actually works
The bottom line is that your AI agent handles the API calls and content deployment for you.
Subscribe to this MCP and provide your Hashnode Personal Access Token.
Connect your agent client (like Claude or Cursor) through Vinkius.
Tell your agent what you need done—whether it’s fetching user data, listing posts, or publishing a new draft.
Who is this actually for?
This MCP is built for people who live in the intersection of writing and publishing. If you’re tired of switching between a CMS dashboard, a code editor, and a chat window just to get an article out the door, this is for you.
Drafting and finalizing technical guides. They use this MCP to fetch user data before writing and then publish the completed guide without ever leaving their AI drafting environment.
Monitoring multiple publication feeds for updates or required changes. They can list all posts from a specific publication feed and use that data to schedule bulk content revisions using update_post.
Creating knowledge-sharing blogs. They fetch user profiles of contributors, draft the article, and then publish it directly so the information is live immediately.
What Changes When You Connect
Drafting is faster. You can write new articles using the create_post tool, bypassing the entire web interface just to hit 'submit.'
Stop context switching. If you need to revise an old article, simply ask to run update_post; your agent handles fetching and modifying the content behind the scenes.
Keep track of who's writing what. Use get_user to quickly pull profile details on any contributor so you can reference them in your current draft.
Monitor entire sites at a glance. The get_publication_posts tool lets you see all recent activity from one feed without clicking through dozens of article pages.
Get the full story. When you need to read an existing piece, get_post retrieves the complete content and metadata in one call.
See it in action
Need to reference a contributor's stats?
A technical writer needs to cite a specific developer. Instead of searching Hashnode manually, they tell their agent to use get_user for that developer’s handle. The agent returns the profile details instantly, letting the writer include accurate follower counts in the draft.
The content feed is stale.
A content manager needs an overview of what's been published recently on a major site. They instruct their agent to run get_publication_posts for that domain, getting a list of titles and dates in minutes, not hours.
I just finished the draft and it needs to go live.
The developer writes the final Markdown section. They prompt their agent: 'Publish this as a new post.' The agent executes create_post, and the article is immediately available on Hashnode.
I need to correct a typo in an old guide.
A developer realizes they messed up a key detail in a published piece. They ask their agent to run update_post on the specific article slug, providing the corrected text. The fix goes live instantly.
The honest tradeoffs
Manual publishing workflow
Drafting an article in your AI client, then copy-pasting it into a local file, and finally logging into the Hashnode website to paste it and hit publish.
Just tell your agent: 'Publish this markdown content.' It handles the create_post call entirely, keeping you in your chat window.
Checking status manually
Needing to check if a publication received its weekly roundup of posts. Having to visit and scroll through the site’s index page repeatedly.
Use get_publication_posts. It gives you an immediate list of recent articles from that entire feed, skipping all the scrolling.
Forgetting old details
Writing about a user but not knowing their current follower count or job title without leaving the writing process.
Run get_user first. It pulls that specific data point directly into your chat, so you can reference it accurately.
When It Fits, When It Doesn't
Use this MCP if your primary goal is content creation or management on Hashnode—specifically drafting, publishing, revising, or querying published posts and user profiles. If you need to analyze complex data structures (like connecting post metadata with external analytics tools), this isn't enough; look for a dedicated API connector. However, if your task involves simply writing code or managing internal records that have nothing to do with blogging, don't use it. Stick to content lifecycle management.
Questions you might have
How do I use get_user to find a person's profile? +
Just ask your agent for the user’s handle. The tool uses that unique identifier to fetch their details instantly, saving you from having to guess their full name or blog URL.
Can I use get_publication_posts to see a feed? +
Yes. You provide the domain of the publication feed, and the MCP runs get_publication_posts. It returns a list of recent articles so you know what content is already out there.
What's the difference between create_post and update_post? +
Think of it this way: create_post makes something brand new. update_post only modifies a piece that already exists, so you need to know its slug or ID.
Does get_post give me the whole article? +
Yes, it fetches the entire post content and all associated metadata for a specific article when you provide the correct slug. You don't get partial data; you get everything.
What do I need to set up my connection before running a tool like `create_post`? +
You must provide your Hashnode Personal Access Token when subscribing this MCP. This token authorizes your AI client to write and modify content on your behalf.
When I use `get_post`, does the output include metadata beyond just the article text? +
Yes, get_post returns structured data that includes not only the full content but also important metadata like publication details and creation slugs.
If I run `update_post` on a post ID that doesn't exist, how does the MCP handle it? +
The MCP catches API errors. If you reference an invalid slug or non-existent ID, your agent will report a clear error message instead of failing silently.
Is the data retrieved by `get_user` restricted to public information only? +
The MCP pulls standard profile details available through the Hashnode API. It provides publicly visible metrics and user handles, but it won't access private account data.
Can I fetch profile details for any Hashnode user? +
Yes! Use the get_user tool with the specific username handle. The agent will return their profile information, bio, and social links.
Does the publishing tool support Markdown formatting? +
Absolutely. Both create_post and update_post accept contentMarkdown, allowing you to publish rich technical content with code blocks, headers, and links.
How do I list posts from a specific blog domain? +
Use the get_publication_posts tool and provide the host domain (e.g., 'engineering.hashnode.dev' or your custom domain). It will return a list of recent posts from that publication.
We've already built the connector for Hashnode. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 5 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.