# How to connect Hashnode to OpenClaw (paste one key, 67 tools) > Connect Hashnode to OpenClaw with ClawLink: paste your Hashnode key once and 67 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/hashnode The usual route to Hashnode access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Hashnode setup: install one ClawHub skill, connect Hashnode in the browser, and OpenClaw can call real Hashnode actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Hashnode. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Hashnode** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect hashnode # connect Hashnode (browser OAuth) npx -y @useclawlink/cli actions hashnode # list available actions npx -y @useclawlink/cli run hashnode --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Hashnode in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Hashnode API key once. Verify the connection by asking OpenClaw: > Use Hashnode to check custom domain availability and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Hashnode is connected in the dashboard, that agent calls the same 67 Hashnode tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Hashnode MCP for OpenClaw Looking for a Hashnode MCP server for OpenClaw? ClawLink connects Hashnode to OpenClaw and exposes 67 Hashnode tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Hashnode integration](https://claw-link.dev/hermes/hashnode) works the same way. ## What the OpenClaw Hashnode integration can do 67 Hashnode tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 67. ### 30 of 67 Hashnode tools for OpenClaw | Tool | What it does | |---|---| | **Check custom domain availability** `hashnode_check_custom_domain_availability` | Check if a custom domain is available for your Hashnode publication | | **Check subdomain availability** `hashnode_check_subdomain_availability` | Check if a subdomain is available for a Hashnode publication | | **Fetch invitations** `hashnode_fetch_invitations` | Fetch pending publication invitations for a Hashnode publication | | **Fetch popular tags** `hashnode_fetch_popular_tags` | Fetch a paginated list of popular tags | | **Fetch posts** `hashnode_fetch_posts` | Fetch a paginated list of posts from a publication | | **Fetch series posts** `hashnode_fetch_series_posts` | Fetch posts from a series within a publication | | **Fetch single article** `hashnode_fetch_single_article` | Fetch a single article by slug from a publication | | **Fetch stories feed** `hashnode_fetch_stories_feed` | Fetch a paginated feed of stories from Hashnode | | **Fetch user details** `hashnode_fetch_user_details` | Fetch detailed user profile information by username | | **Get documentation project** `hashnode_get_documentation_project` | Fetch details of a Docs by Hashnode project by ID or hostname | | **Get post** `hashnode_get_post` | Retrieve a published post by ID from Hashnode | | **Get publication by ID or host** `hashnode_get_publication_by_id_or_host` | Fetch publication details by ID or hostname | | **Get tag** `hashnode_get_tag` | Fetch detailed information about a tag by its slug | | **List publications** `hashnode_list_publications` | List all publications of the authenticated user | | **List top commenters** `hashnode_list_top_commenters` | Fetch users who have most actively participated in discussions by commenting in the last 7 days | | **Me** `hashnode_me` | Retrieves profile details of the currently authenticated Hashnode user | | **Search posts of publication** `hashnode_search_posts_of_publication` | Search and retrieve posts from a specific publication based on a search query | | **Accept invite to publication** `hashnode_accept_invite_to_publication` | Accept a publication invitation | | **Add comment** `hashnode_add_comment` | Add a comment to a Hashnode post | | **Add content block** `hashnode_add_content_block` | Add a content block to a Hashnode documentation project | | **Add custom mdx component** `hashnode_add_custom_mdx_component` | Add a custom MDX component to a Hashnode documentation project | | **Add documentation project custom domain** `hashnode_add_documentation_project_custom_domain` | Add a custom domain to a Hashnode documentation project | | **Add reply** `hashnode_add_reply` | Add a reply to an existing comment | | **Create documentation API reference** `hashnode_create_documentation_api_reference` | Create a documentation API reference from an OpenAPI specification URL in a Hashnode project | | **Create documentation link** `hashnode_create_documentation_link` | Create a link within a Hashnode documentation guide | | **Create documentation project** `hashnode_create_documentation_project` | Create a new documentation project on Hashnode | | **Create documentation section** `hashnode_create_documentation_section` | Create a new documentation section in a Hashnode documentation guide | | **Create hashnode documentation guide** `hashnode_create_hashnode_documentation_guide` | Create a new documentation guide in a Hashnode documentation project | | **Disable documentation project AI search** `hashnode_disable_documentation_project_ai_search` | Disable AI search for a documentation project on Hashnode | | **Follow tags** `hashnode_follow_tags` | Follow specified tags to customize your content feed on Hashnode | ## Example prompts **Check Custom Domain Availability** > Use Hashnode to check custom domain availability and walk me through the result in plain English. **Check Subdomain Availability** > Use Hashnode to check subdomain availability and walk me through the result in plain English. **Fetch Invitations** > Pull the relevant data from Hashnode, summarize it in plain English, and point out anything that needs attention. **Fetch Popular Tags** > Pull the relevant data from Hashnode, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Hashnode working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Hashnode API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Hashnode account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Hashnode. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Hashnode actions to the runtime in a format your agent can reliably use. | 67 tools for Hashnode are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Hashnode to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Hashnode in the browser, and the 67 tools above work from chat. There is no SDK and no config file, and the Hashnode key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Hashnode skill but can't call the tools The ClawHub skill teaches OpenClaw about Hashnode, but the calls run through the ClawLink plugin and your connected account. Make sure Hashnode is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Hashnode from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Hashnode tools Hashnode tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Hashnode call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Hashnode returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Hashnode has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Hashnode integration? Yes. ClawLink is the fastest way to connect OpenClaw to Hashnode: link your Hashnode account once in the browser and OpenClaw can call the Hashnode API through 67 ready-made tools — no custom code or token handling. ### How do I add Hashnode to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Hashnode skill from ClawHub, then you click Connect in the dashboard to authorize Hashnode. OpenClaw calls the tools from the next message — no config files, and the Hashnode key you paste is stored server-side instead of in your environment. ### How long does it take to connect Hashnode to OpenClaw? About two minutes. Sign in, click Connect next to Hashnode in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Hashnode up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Hashnode working from chat. ### OpenClaw installed the Hashnode skill but can't call the tools The ClawHub skill teaches OpenClaw about Hashnode, but the calls run through the ClawLink plugin and your connected account. Make sure Hashnode is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.