# 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.

Source: https://elaichi.ai/connectors/hashnode/

## Facts

| | |
| --- | --- |
| Application | Hashnode |
| Category | Marketing Automation |
| AI tools | 14 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Hashnode is connected

- 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.

## Connect Hashnode in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Hashnode.
2. Optionally set Share with, then press Connect.
3. Paste a Hashnode API key. One person generates a token in Hashnode and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Hashnode tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Hashnode MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Hashnode MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Hashnode tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Hashnode through Elaichi

### Draft the launch post before the announcement

Marketing. 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.

### Turn a conference talk into a draft

Developer relations. Paste the talk outline and have a Hashnode draft written up with the code examples and headings in place, ready for a final edit.

### Find and fix an outdated post

Content. Pull up the Hashnode post by title, replace the paragraph that no longer holds, and leave the rest of the piece untouched.

### Publish the changelog once it is approved

Engineering. When a draft has been signed off, publish it to the engineering publication on Hashnode without opening the editor.

### See what went out this month

Product. Ask for every Hashnode post published across your publications this month and get a short rundown with dates and titles.

### Clean up drafts nobody will finish

Community. List the Hashnode drafts that have sat untouched for months and delete the ones the team agrees to drop.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Hashnode connection?

Yes. One person connects Hashnode with their API key and shares the connection with a team, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names who published or edited each post.

### 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.

## All 14 Hashnode tools

Every tool below is callable through https://api.elaichi.ai/mcp once Hashnode is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Hashnode me** (List). Get the Hashnode user who owns the token, with their publications (blogs). Works without a Pro plan.
- **List all Hashnode publications** (List). List the publications (blogs) the user owns. Use an ID from here as publication_id or publicationId elsewhere.
- **Get single Hashnode publication by ID** (Get). Get one publication (blog) by ID. Needs the publication to be on Hashnode's Pro plan.
- **List all Hashnode posts** (List). List the published posts of a publication, newest first. Give publication_id or host. Needs Pro.
- **Get single Hashnode post by ID** (Get). Get one post by ID, including its Markdown and HTML content. Needs Pro.
- **Create a Hashnode post** (Create). Publish a new post straight to a publication (no draft step). Needs Pro.
- **Update a Hashnode post by ID** (Update). Update a published post by ID. Send only the fields to change. Needs Pro.
- **Delete a Hashnode post by ID** (Delete). Remove a post by ID (Hashnode soft-deletes it: it leaves feeds and its slug is freed). Needs Pro.
- **List all Hashnode drafts** (List). List the user's drafts in a publication. Give publication_id or host. Needs Pro.
- **Get single Hashnode draft by ID** (Get). Get one draft by ID, including its Markdown. Needs Pro.
- **Create a Hashnode draft** (Create). Create a draft in a publication. Publish it later with drafts publish. Needs Pro.
- **Update a Hashnode draft by ID** (Update). Update a draft by ID. Send only the fields to change. Needs Pro.
- **Hashnode drafts publish** (Publish). Publish a draft as a post. Hashnode removes the draft once the post exists. Needs Pro.
- **Delete a Hashnode draft by ID** (Delete). Delete a draft by ID. Needs Pro.
