Hashnode for AI agents

Hashnode is a blogging platform for developers, letting them publish posts, manage publications, and run documentation sites. Developers wire it into their own apps and internal tools instead of building the underlying capability from scratch. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Developer toolsAPI keyMCP + RESThashnode.com
AUDIT LOG · HASHNODEPOLICY: acme-support
09:41:07 · claude · u_8f2read
hashnode.list_publications
Hashnode: List Publications✓ allowed · 212ms
09:41:08 · claude · u_8f2read
hashnode.me
Hashnode: Get Current User✓ allowed · 164ms
09:41:09 · claude · u_8f2write
hashnode.create_documentation_link
Create Documentation Link✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
hashnode.delete_content_block
Hashnode Delete Content Block✕ blocked · policy: deny
EVERY HASHNODE CALL, ON THE RECORD
01 · USE CASES

What agents do in Hashnode.

01

Publish a new blog post

Publish a drafted article to a developer's Hashnode publication with the right tags.

02

Fetch a published article

Pull the content of a published post to repurpose it for a newsletter or social snippet.

03

Reply to a comment

Post a reply to a reader's comment on an article to keep the discussion going.

02 · ACTIONS

67 Hashnode actions, graded by risk.

Every Hashnode action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

18

Look things up. Allowed by default.

  • hashnode.get_tag
    Hashnode: Get Tag Details
  • hashnode.get_post
    Get Post by ID
  • hashnode.list_publications
    Hashnode: List Publications
  • hashnode.list_top_commenters
    Hashnode: List Top Commenters
  • hashnode.get_documentation_project
    Get Documentation Project
  • hashnode.search_posts_of_publication
    Search Posts of Publication
  • hashnode.get_publication_by_id_or_host
    Get Publication by ID or Host
  • hashnode.me
    Hashnode: Get Current User
  • hashnode.fetch_posts
    Fetch Publication Posts
  • hashnode.fetch_invitations
    Hashnode: Fetch Invitations
  • hashnode.fetch_popular_tags
    Hashnode: Fetch Popular Tags
  • hashnode.fetch_series_posts
    Fetch Series Posts
  • hashnode.fetch_stories_feed
    Fetch Stories Feed
  • hashnode.fetch_user_details
    Hashnode: Fetch User Details
  • hashnode.fetch_single_article
    Fetch Single Article
  • hashnode.check_subdomain_availability
    Hashnode: Check Subdomain Availability
+ 2 MORE

write

36

Create and change things. Allow, or ask the user first.

  • hashnode.add_reply
    Hashnode Add Reply
  • hashnode.add_comment
    Hashnode Add Comment
  • hashnode.update_post
    Hashnode Update Post
  • hashnode.update_reply
    Hashnode Update Reply
  • hashnode.update_comment
    Hashnode Update Comment
  • hashnode.add_custom_mdx_component
    Hashnode Add Custom MDX Component
  • hashnode.create_documentation_link
    Create Documentation Link
  • hashnode.update_documentation_link
    Update Documentation Link
  • hashnode.update_documentation_guide
    Update Hashnode Documentation Guide
  • hashnode.create_documentation_project
    Hashnode: Create Documentation Project
  • hashnode.create_documentation_section
    Hashnode Create Documentation Section
  • hashnode.update_documentation_section
    Hashnode Update Documentation Section
  • hashnode.update_documentation_appearance
    Update Documentation Appearance
  • hashnode.update_documentation_integrations
    Hashnode: Update Documentation Integrations
  • hashnode.create_documentation_api_reference
    Create Documentation API Reference
  • hashnode.create_hashnode_documentation_guide
    Create Hashnode Documentation Guide
+ 20 MORE

destructive

13

Delete, cancel or archive. Ask first, or deny outright.

  • hashnode.remove_post
    Hashnode Remove Post
  • hashnode.remove_reply
    Hashnode Remove Reply
  • hashnode.remove_comment
    Hashnode Remove Comment
  • hashnode.delete_content_block
    Hashnode Delete Content Block
  • hashnode.remove_documentation_guide
    Hashnode Remove Documentation Guide
  • hashnode.delete_custom_mdx_component
    Hashnode Delete Custom MDX Component
  • hashnode.remove_documentation_project
    Remove Documentation Project
  • hashnode.remove_documentation_sidebar_item
    Remove Documentation Sidebar Item
  • hashnode.remove_documentation_project_custom_domain
    Hashnode Remove Documentation Project Custom Domain
  • hashnode.add_content_block
    Hashnode Add Content Block
  • hashnode.update_content_block
    Hashnode Update Content Block
  • hashnode.unsubscribe_from_newsletter
    Unsubscribe from Newsletter
  • hashnode.disable_documentation_project_ai_search
    Disable Documentation Project AI Search
03 · HOW IT WORKS

Hashnode in three steps.

  1. 01Your users connect HashnodeThey add their Hashnode api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Documentation Link” can wait for the user, and “hashnode Delete Content Block” can be denied outright.
  3. 03Any agent can actYour agent calls Hashnode through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('hashnode', {
  read: 'allow',
  write: 'ask',        // create_documentation_link
  destructive: 'deny',  // delete_content_block
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Hashnode connects.

Users add their Hashnode api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Hashnode connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Hashnode from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Hashnode and Arc0, answered.

Q01

Can I use Hashnode with Claude, ChatGPT or Cursor?

Yes. Connect Hashnode to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Hashnode actions you allow.

Q02

How do users connect Hashnode?

Users add their Hashnode api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Hashnode actions can my agent take?

67 in total: 18 read, 36 write and 13 destructive, such as “create Documentation Link”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Hashnode?

Yes. Actions like “hashnode Delete Content Block” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Hashnode too?

Yes. The same Hashnode connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Hashnode into your agent.

Your users connect Hashnode once, under your brand. Your agent gets 67 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan