How to integrate Hashnode MCP with LlamaIndex

This guide walks you through connecting Hashnode to LlamaIndex using the Composio tool router. By the end, you'll have a working Hashnode agent that can list your most recent hashnode articles, check if 'devjournal.com' domain is available, fetch popular tags for trending topics through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Hashnode account through Composio's Hashnode MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Hashnode logoHashnode
Api Key

Hashnode is a blogging platform designed for developers to create, manage, and share technical content. It streamlines publishing and helps grow your dev audience effortlessly.

67 Tools

Introduction

This guide walks you through connecting Hashnode to LlamaIndex using the Composio tool router. By the end, you'll have a working Hashnode agent that can list your most recent hashnode articles, check if 'devjournal.com' domain is available, fetch popular tags for trending topics through natural language commands.

This guide will help you understand how to give your LlamaIndex agent real control over a Hashnode account through Composio's Hashnode MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Hashnode with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AICrewAI

TL;DR

Here's what you'll learn:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Hashnode
  • Connect LlamaIndex to the Hashnode MCP server
  • Build a Hashnode-powered agent using LlamaIndex
  • Interact with Hashnode through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

What is the Hashnode MCP server, and what's possible with it?

The Hashnode MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Hashnode account. It provides structured and secure access to your blog and developer publication data, so your agent can fetch articles, manage publication invites, reply to comments, and explore tags or user details on your behalf.

  • Fetch and analyze articles: Let your agent retrieve single articles or lists of posts from your publications, making it easy to summarize, review, or manage your content.
  • Publication invite handling: Effortlessly accept publication invitations or view all your pending invites, streamlining the process of joining new developer teams or publications.
  • Interact with comments and replies: Have your agent add replies to existing comments, enabling automated engagement and conversation management on your posts.
  • Tag discovery and trend tracking: Easily fetch popular tags so your agent can suggest relevant topics, optimize your writing focus, or help you follow industry trends.
  • User and publication insights: Retrieve detailed profile information for any user or publication, giving your agent the context needed for personalized recommendations and content actions.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Hashnode account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Hashnode

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Hashnode access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called hashnode_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["hashnode"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Hashnode actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, hashnode)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Hashnode tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Hashnode
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Hashnode tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Hashnode
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Hashnode, then start asking questions.

Complete Code

Here's the complete code to get you started with Hashnode and LlamaIndex:

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["hashnode"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Hashnode actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Hashnode to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Hashnode tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
TOOLS

Supported Tools

Every Hashnode action and event your agent gets out of the box.

Hashnode Accept Publication Invite

Tool to accept a publication invitation.

Hashnode Add Comment

Add a comment to a Hashnode post.

Hashnode Add Content Block

Tool to add a content block to a Hashnode documentation project.

Hashnode Add Custom MDX Component

Tool to add a custom MDX component to a Hashnode documentation project.

Hashnode: Add Documentation Project Custom Domain

Tool to add a custom domain to a Hashnode documentation project.

Hashnode Add Reply

Tool to add a reply to an existing comment.

Hashnode: Check Custom Domain Availability

Tool to check if a custom domain is available for your Hashnode publication.

Hashnode: Check Subdomain Availability

Tool to check if a subdomain is available for a Hashnode publication.

Create Documentation API Reference

Tool to create a documentation API reference from an OpenAPI specification URL in a Hashnode project.

Create Documentation Link

Tool to create a link within a Hashnode documentation guide.

Hashnode: Create Documentation Project

Tool to create a new documentation project on Hashnode.

Hashnode Create Documentation Section

Tool to create a new documentation section in a Hashnode documentation guide.

Create Hashnode Documentation Guide

Tool to create a new documentation guide in a Hashnode documentation project.

Hashnode Delete Content Block

Tool to delete a content block from a Hashnode documentation project.

Hashnode Delete Custom MDX Component

Tool to delete a custom MDX component from a Hashnode documentation project.

Disable Documentation Project AI Search

Tool to disable AI search for a documentation project on Hashnode.

Hashnode: Fetch Invitations

Fetch pending publication invitations for a Hashnode publication.

Hashnode: Fetch Popular Tags

Tool to fetch a paginated list of popular tags.

Fetch Publication Posts

Tool to fetch a paginated list of posts from a publication.

Fetch Series Posts

Tool to fetch posts from a series within a publication.

Fetch Single Article

Tool to fetch a single article by slug from a publication.

Fetch Stories Feed

Fetch a paginated feed of stories from Hashnode.

Hashnode: Fetch User Details

Tool to fetch detailed user profile information by username.

Hashnode: Follow Tags

Follow specified tags to customize your content feed on Hashnode.

Generate Documentation Project Preview Authorization Token

Tool to generate a JWT authorization token for previewing a documentation project.

Get Documentation Project

Tool to fetch details of a Docs by Hashnode project by ID or hostname.

Get Post by ID

Tool to retrieve a published post by ID from Hashnode.

Get Publication by ID or Host

Tool to fetch publication details by ID or hostname.

Hashnode: Get Tag Details

Tool to fetch detailed information about a tag by its slug.

Hashnode Like Comment

Tool to like a comment on Hashnode.

Hashnode Like Post

Tool to like a post on Hashnode.

Hashnode: Like Reply

Tool to like a reply on Hashnode.

Hashnode: List Publications

Tool to list all publications of the authenticated user.

Hashnode: List Top Commenters

Tool to fetch users who have most actively participated in discussions by commenting in the last 7 days.

Hashnode: Map Documentation Project WWW Redirect

Tool to configure WWW redirect for a documentation project's custom domain.

Hashnode: Get Current User

Retrieves profile details of the currently authenticated Hashnode user.

Move Documentation Sidebar Item

Tool to reorder documentation sidebar items within a Hashnode guide.

Publish Documentation API Reference

Tool to publish a documentation API reference in a Hashnode documentation project.

Hashnode Publish Post

Tool to publish a new blog post to a Hashnode publication.

Hashnode Remove Comment

Tool to remove a comment from a Hashnode post.

Hashnode Remove Documentation Guide

Tool to remove a documentation guide from a Hashnode project.

Remove Documentation Project

Tool to remove a documentation project from Hashnode.

Hashnode Remove Documentation Project Custom Domain

Tool to remove a custom domain from a Hashnode documentation project.

Remove Documentation Sidebar Item

Tool to remove a sidebar item from a documentation guide on Hashnode.

Hashnode Remove Post

Tool to remove (delete) a post from Hashnode.

Hashnode Remove Reply

Tool to remove a reply from a comment.

Hashnode Rename Documentation Guide

Tool to rename a documentation guide in a Hashnode project.

Rename Documentation Sidebar Item

Tool to rename a documentation sidebar item within a Hashnode guide.

Hashnode Restore Post

Tool to restore a previously deleted Hashnode post.

Save Documentation Page Draft Content

Tool to save draft content for a documentation page in Hashnode.

Search Posts of Publication

Tool to search and retrieve posts from a specific publication based on a search query.

Subscribe to Newsletter

Tool to subscribe an email address to a Hashnode publication's newsletter.

Hashnode: Toggle Follow User

Tool to toggle follow status for a Hashnode user.

Hashnode: Unfollow Tags

Unfollow specified tags to customize your content feed on Hashnode.

Unsubscribe from Newsletter

Tool to unsubscribe an email address from a Hashnode publication's newsletter.

Hashnode Update Comment

Tool to update an existing comment on a Hashnode post.

Hashnode Update Content Block

Tool to update a content block in a Hashnode documentation project.

Update Documentation Appearance

Tool to update the appearance settings of a Hashnode documentation project.

Update Documentation General Settings

Tool to update general settings of a Hashnode documentation project.

Update Hashnode Documentation Guide

Tool to update an existing documentation guide in a Hashnode project.

Hashnode: Update Documentation Integrations

Tool to update third-party integrations for a Docs by Hashnode project.

Update Documentation Link

Tool to update an existing link within a Hashnode documentation guide.

Hashnode: Update Documentation Project Subdomain

Tool to update the subdomain of a Hashnode documentation project.

Hashnode Update Documentation Section

Tool to update a section in a Hashnode documentation guide.

Hashnode Update Post

Tool to update an existing Hashnode post via the updatePost mutation.

Hashnode Update Reply

Tool to update a reply.

Hashnode Verify Documentation Project Custom Domain

Tool to verify a custom domain for a Hashnode documentation project.

FRAMEWORKS

How to build Hashnode MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Hashnode MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Hashnode MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Hashnode MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Hashnode MCP with Claude Cowork

Codex logo

Codex

Use Hashnode MCP with Codex

OpenClaw logo

OpenClaw

Use Hashnode MCP with OpenClaw

Hermes logo

Hermes

Use Hashnode MCP with Hermes

CLI logo

CLI

Use Hashnode MCP with CLI

Google ADK logo

Google ADK

Use Hashnode MCP with Google ADK

LangChain logo

LangChain

Use Hashnode MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Hashnode MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Hashnode MCP with Mastra AI

CrewAI logo

CrewAI

Use Hashnode MCP with CrewAI

FAQ

Frequently asked questions

With a standalone Hashnode MCP server, the agents and LLMs can only access a fixed set of Hashnode tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Hashnode and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. LlamaIndex fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Hashnode tools.

Yes, absolutely. You can configure which Hashnode scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Hashnode data and credentials are handled as safely as possible.

Start with Hashnode.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Hashnode tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies