Hashnode MCP connector
The Hashnode connector brings your publications, posts and drafts into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each writer works inside their own Hashnode access with every action logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Which drafts in our engineering publication are still unpublished?
Working in Hashnode with Elaichi
-
List all Hashnode me
-
List all Hashnode publications
-
Get single Hashnode publication by ID
How to connect Hashnode to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Hashnode MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Hashnode MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Hashnode MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Hashnode MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Hashnode MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Hashnode to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Hashnode through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Hashnode is logged.
-
Marketing
Draft the launch post before the announcement
Describe the release in a few lines and get a Hashnode draft ready for review in the right publication. Nothing goes live until someone chooses to publish it.
-
Developer relations
Turn a conference talk into a draft
Paste the talk outline and have a Hashnode draft written up with the code examples and headings in place, ready for a final edit.
-
Content
Find and fix an outdated post
Pull up the Hashnode post by title, replace the paragraph that no longer holds, and leave the rest of the piece untouched.
-
Engineering
Publish the changelog once it is approved
When a draft has been signed off, publish it to the engineering publication on Hashnode without opening the editor.
-
Product
See what went out this month
Ask for every Hashnode post published across your publications this month and get a short rundown with dates and titles.
-
Community
Clean up drafts nobody will finish
List the Hashnode drafts that have sat untouched for months and delete the ones the team agrees to drop.
Try asking
- “Which drafts in our engineering publication are still unpublished?”
- “Draft a post announcing the API rate limit change.”
- “Update last week's release notes post with the hotfix details.”
What connecting Hashnode gets you
6 screens from Elaichi, each doing one job for your Hashnode account.
Ask Elaichi to work across your apps.
Which drafts in our engineering publication are still unpublished?
Draft a post announcing the API rate limit change.
Update last week's release notes post with the hotfix details.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Hashnode drafts in plain words.
Ask which drafts are waiting and get the answer from live Hashnode records.
Copy the endpoint
AI apps
One endpoint puts Hashnode in every client.
Claude, ChatGPT and Cursor reach Hashnode through one governed endpoint, no SDK, no shared key.
Tool catalog
14 Hashnode tools, no code to write.
Publications, posts and drafts, listed, created, updated and published, with nothing to build.
Toolboxes
Each team gets its own Hashnode toolbox.
Marketing drafts, developer relations publishes, each team sees only the Hashnode tools it needs.
Shared connections
Share the Hashnode connection, not the key.
One person connects Hashnode, teammates publish through it and never see the API key.
Audit log
Every Hashnode action lands in the log.
See who published, edited or deleted which post, and when, in one place.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Hashnode digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch publications
Hashnode
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Hashnode
Queued
Workflows
A schedule drafts the Hashnode digest itself.
Posts are fetched and grouped, an agent drafts, a person approves, and it posts to Hashnode.
Hashnode health
Refreshed 4 minutes ago · every 15 minutes · from the publications collection
Publications
1,284 ↓ 12%
Posts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Publications created
Last 14 days
By team
Share of activity
Marketing 34%
Developer relations 27%
Engineering blog 21%
Product updates 18%
Collections and dashboards
Hashnode health, computed without a model.
Posts created over 14 days, broken down by team, refreshed on a schedule with no prompt.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Hashnode
All three can connect Hashnode to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Hashnode tools | Allow or restrict single Hashnode tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Hashnode call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Hashnode tools for your AI agents
14 tools are ready to call through Elaichi's MCP endpoint the moment you connect Hashnode, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Hashnode to Claude?
Connect Hashnode in Elaichi first, which asks for your Hashnode API key and nothing else, there is no client ID or secret to generate and no app to register. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Hashnode publications, posts and drafts are available in the chat.
Does Hashnode work with ChatGPT and Cursor as well as Claude?
Yes. Hashnode connects to Elaichi once, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. There is nothing to set up again per client.
What can an AI agent actually do with my Hashnode data?
An agent can list your Hashnode publications, read posts and drafts, write a new draft, update a post or draft, publish a draft and delete what is no longer needed. Short concrete asks work best, such as "draft a post about the new pricing page" or "update the onboarding post with the new screenshots".
Does connecting Hashnode give the AI access to every publication?
No. Every action in Hashnode runs as the person who signed in, so an agent sees only the Hashnode publications, posts and drafts that person can already reach. Elaichi can narrow that access further with roles and restrictions, and it can never widen it.
Can I stop an agent from deleting or changing things in Hashnode?
Yes. Restrictions in Elaichi work per action, so you can restrict deleting or publishing Hashnode posts for a role or for one person while leaving reading and drafting open. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Hashnode connection when someone leaves?
Offboarding a person in Elaichi ends their access to Hashnode through every client at once. A Hashnode connection they shared keeps working for everyone else on the team. If the connection itself should go, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the Hashnode MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Hashnode is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Hashnode?
Yes. Both let Claude, ChatGPT or Cursor use Hashnode. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Hashnode call.
How is Elaichi different from Composio for Hashnode?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Hashnode: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Hashnode in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot