Hashnode MCP integration for AI agents.
Connect AI agents to Hashnode through 11 structured actions, including get current user, create draft, and delete draft. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 11
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Hashnode integration exposes
The Hashnode Agent App exposes 11 provider-backed actions for developer tools and social work. Its current contract lets an authorized agent get the profile for the user authenticated by the connected hashnode pat, create a draft in a hashnode publication with an active pro plan, and soft-delete an accessible hashnode draft from a pro publication. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Hashnode account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Hashnode capabilities.
Showing 11 of 11 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_userREADGet the profile for the user authenticated by the connected Hashnode PAT.
create_draftWRITECreate a draft in a Hashnode publication with an active Pro plan.
INPUTS: publicationId / title / subtitle / contentMarkdown / slug
delete_draftHIGH IMPACTSoft-delete an accessible Hashnode draft from a Pro publication.
INPUTS: draftId
get_draftREADGet one accessible Hashnode draft by ID from a Pro publication.
INPUTS: id
get_postREADGet one published Hashnode post by ID, including Markdown and rendered HTML.
INPUTS: id
list_my_publicationsREADList publications available to the authenticated Hashnode user.
INPUTS: first / after
list_publication_postsREADList posts from a Hashnode publication with cursor pagination; the publication must have an active Pro plan.
INPUTS: publicationId / host / first / after
publish_draftHIGH IMPACTPublish an existing Hashnode draft from a Pro publication.
INPUTS: draftId
publish_postHIGH IMPACTPublish a Markdown post to a Hashnode publication with an active Pro plan.
INPUTS: publicationId / title / contentMarkdown / subtitle / coverImage
update_draftWRITEUpdate fields on an existing Hashnode draft in a Pro publication.
INPUTS: draftId / title / subtitle / contentMarkdown / slug
update_postWRITEUpdate fields on an existing Hashnode post in a Pro publication.
INPUTS: id / title / contentMarkdown / subtitle / coverImage
INPUT CONTRACTS
Know what the action needs before it runs.
create_draft
publicationIdREQUIRED- The ID of the target Hashnode publication.
titleOPTIONAL- The optional draft title.
subtitleOPTIONAL- The optional draft subtitle.
contentMarkdownOPTIONAL- The optional draft content in Markdown format.
slugOPTIONAL- The optional custom slug for the resulting post.
delete_draft
draftIdREQUIRED- The ID of the Hashnode draft to delete.
get_draft
idREQUIRED- The Hashnode draft ID.
get_post
idREQUIRED- The Hashnode post ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current User
Get the profile for the user authenticated by the connected Hashnode PAT. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_userControl Create Draft
Create a draft in a Hashnode publication with an active Pro plan. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_draftVerify with Get Draft
Get one accessible Hashnode draft by ID from a Pro publication. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_draftSAFETY BOUNDARY
Operate Hashnode with explicit limits
- Authorize Hashnode with API key and grant only the provider access required by the selected actions.
- 6 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_draft`, `publish_draft`, and `publish_post` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Hashnode rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Hashnode task completed successfully.
CONNECTION MODEL
API key
Hashnode Personal Access Token sent as a Bearer credential. Create or manage tokens in Hashnode Account Settings > Developer: https://hashnode.com/settings/developer
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 3
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Hashnode.