# How to integrate Hashnode MCP with LangChain

```json
{
  "title": "How to integrate Hashnode MCP with LangChain",
  "toolkit": "Hashnode",
  "toolkit_slug": "hashnode",
  "framework": "LangChain",
  "framework_slug": "langchain",
  "url": "https://composio.dev/toolkits/hashnode/framework/langchain",
  "markdown_url": "https://composio.dev/toolkits/hashnode/framework/langchain.md",
  "updated_at": "2026-05-12T10:14:41.459Z"
}
```

## Introduction

This guide walks you through connecting Hashnode to LangChain 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 LangChain 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 SDK](https://composio.dev/toolkits/hashnode/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/hashnode/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/hashnode/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/hashnode/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/hashnode/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/hashnode/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/hashnode/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/hashnode/framework/cli)
- [Google ADK](https://composio.dev/toolkits/hashnode/framework/google-adk)
- [Vercel AI SDK](https://composio.dev/toolkits/hashnode/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/hashnode/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/hashnode/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/hashnode/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Connect your Hashnode project to Composio
- Create a Tool Router MCP session for Hashnode
- Initialize an MCP client and retrieve Hashnode tools
- Build a LangChain agent that can interact with Hashnode
- Set up an interactive chat interface for testing

## What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.
Key features include:
- Agent Framework: Build agents that can use tools and make decisions
- MCP Integration: Connect to external services through Model Context Protocol adapters
- Memory Management: Maintain conversation history across interactions
- Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `HASHNODE_ACCEPT_INVITE_TO_PUBLICATION` | Hashnode Accept Publication Invite | Tool to accept a publication invitation. Use when you have a valid invite token and want to join the publication. |
| `HASHNODE_ADD_COMMENT` | Hashnode Add Comment | Add a comment to a Hashnode post. Requires a valid post ID (obtainable via HASHNODE_FETCH_STORIES_FEED or HASHNODE_FETCH_POSTS) and markdown content. For replying to existing comments, use the HASHNODE_ADD_REPLY action instead. |
| `HASHNODE_ADD_CONTENT_BLOCK` | Hashnode Add Content Block | Tool to add a content block to a Hashnode documentation project. Use when you need to add embeddable content (such as code snippets, widgets, or other custom content) to a documentation project. |
| `HASHNODE_ADD_CUSTOM_MDX_COMPONENT` | Hashnode Add Custom MDX Component | Tool to add a custom MDX component to a Hashnode documentation project. Use when you need to register a new reusable React component that can be used in MDX content. Requires a project ID, component identifier, and the JavaScript/React code defining the component. |
| `HASHNODE_ADD_DOCUMENTATION_PROJECT_CUSTOM_DOMAIN` | Hashnode: Add Documentation Project Custom Domain | Tool to add a custom domain to a Hashnode documentation project. Use when setting up custom domain mapping for documentation sites. Requires projectId, domain name, and wwwDomain boolean flag. |
| `HASHNODE_ADD_REPLY` | Hashnode Add Reply | Tool to add a reply to an existing comment. Use after confirming comment ID and reply content. |
| `HASHNODE_CHECK_CUSTOM_DOMAIN_AVAILABILITY` | Hashnode: Check Custom Domain Availability | Tool to check if a custom domain is available for your Hashnode publication. Use when verifying domain mapping before setup. |
| `HASHNODE_CHECK_SUBDOMAIN_AVAILABILITY` | Hashnode: Check Subdomain Availability | Tool to check if a subdomain is available for a Hashnode publication. Use when verifying subdomain availability before creating a publication. |
| `HASHNODE_CREATE_DOCUMENTATION_API_REFERENCE` | Create Documentation API Reference | Tool to create a documentation API reference from an OpenAPI specification URL in a Hashnode project. Use when you need to import and generate API documentation from a Swagger/OpenAPI spec. Requires projectId and the URL of the API specification. |
| `HASHNODE_CREATE_DOCUMENTATION_LINK` | Create Documentation Link | Tool to create a link within a Hashnode documentation guide. Use when you need to add external or internal links to documentation pages, such as API references, GitHub repositories, or related resources. |
| `HASHNODE_CREATE_DOCUMENTATION_PROJECT` | Hashnode: Create Documentation Project | Tool to create a new documentation project on Hashnode. Use when you need to set up a documentation site for API references, product guides, or developer documentation. Requires a unique name and subdomain. |
| `HASHNODE_CREATE_DOCUMENTATION_SECTION` | Hashnode Create Documentation Section | Tool to create a new documentation section in a Hashnode documentation guide. Use when you need to add a new section to an existing documentation guide within a project. |
| `HASHNODE_CREATE_HASHNODE_DOCUMENTATION_GUIDE` | Create Hashnode Documentation Guide | Tool to create a new documentation guide in a Hashnode documentation project. Use when you need to create a new guide within an existing project. Requires a valid projectId and a name for the guide. |
| `HASHNODE_DELETE_CONTENT_BLOCK` | Hashnode Delete Content Block | Tool to delete a content block from a Hashnode documentation project. Use when you need to remove a custom content block from a project. This action is destructive and cannot be undone. |
| `HASHNODE_DELETE_CUSTOM_MDX_COMPONENT` | Hashnode Delete Custom MDX Component | Tool to delete a custom MDX component from a Hashnode documentation project. Use when removing an existing custom component that is no longer needed. This action is destructive and cannot be undone. |
| `HASHNODE_DISABLE_DOCUMENTATION_PROJECT_AI_SEARCH` | Disable Documentation Project AI Search | Tool to disable AI search for a documentation project on Hashnode. Use when you need to turn off AI-powered search capabilities for a specific documentation project. |
| `HASHNODE_FETCH_INVITATIONS` | Hashnode: Fetch Invitations | Fetch pending publication invitations for a Hashnode publication. Returns a list of pending invites that have been sent but not yet accepted. Requires the authenticated user to be a member (owner/admin/editor) of the target publication. Use this to review outstanding team invitations before sending reminders or revoking invites. |
| `HASHNODE_FETCH_POPULAR_TAGS` | Hashnode: Fetch Popular Tags | Tool to fetch a paginated list of popular tags. Use when you need to browse popular tags page by page. |
| `HASHNODE_FETCH_POSTS` | Fetch Publication Posts | Tool to fetch a paginated list of posts from a publication. Use when you need to list posts page by page for a given publication host. |
| `HASHNODE_FETCH_SERIES_POSTS` | Fetch Series Posts | Tool to fetch posts from a series within a publication. Use when retrieving and paginating through series posts in a specific publication. |
| `HASHNODE_FETCH_SINGLE_ARTICLE` | Fetch Single Article | Tool to fetch a single article by slug from a publication. Use when you need the detailed content of a specific post. |
| `HASHNODE_FETCH_STORIES_FEED` | Fetch Stories Feed | Fetch a paginated feed of stories from Hashnode. Returns posts with title, brief, author info, tags, and reading time. Supports filtering by feed type (RECENT, FEATURED, FOLLOWING, etc.), reading time range, and tags. Use cursor-based pagination via the 'after' parameter with the endCursor from previous responses. |
| `HASHNODE_FETCH_USER_DETAILS` | Hashnode: Fetch User Details | Tool to fetch detailed user profile information by username. Use when you need public or authorized profile data. |
| `HASHNODE_FOLLOW_TAGS` | Hashnode: Follow Tags | Follow specified tags to customize your content feed on Hashnode. Use when you want to subscribe to content from specific tags to personalize your feed. |
| `HASHNODE_GEN_DOC_PROJECT_PREVIEW_AUTH_TOKEN` | Generate Documentation Project Preview Authorization Token | Tool to generate a JWT authorization token for previewing a documentation project. Use when you need to obtain a JWT to access a documentation project preview. Requires a preview token that must be generated first using the generateDocumentationProjectPreviewToken mutation. |
| `HASHNODE_GET_DOCUMENTATION_PROJECT` | Get Documentation Project | Tool to fetch details of a Docs by Hashnode project by ID or hostname. Use when you need metadata for a documentation project. Provide either project ID or host domain. |
| `HASHNODE_GET_POST` | Get Post by ID | Tool to retrieve a published post by ID from Hashnode. Use when you need to fetch detailed information about a specific post for rendering or displaying. |
| `HASHNODE_GET_PUBLICATION_BY_ID_OR_HOST` | Get Publication by ID or Host | Tool to fetch publication details by ID or hostname. User can provide either publication ID or host. Use when you need metadata for a given publication. Returns comprehensive publication information including author, title, description, and configuration. |
| `HASHNODE_GET_TAG` | Hashnode: Get Tag Details | Tool to fetch detailed information about a tag by its slug. Use when you need tag metadata, follower/post counts, or logo information. |
| `HASHNODE_LIKE_COMMENT` | Hashnode Like Comment | Tool to like a comment on Hashnode. Use when you have a comment ID and want to add a like to that comment. |
| `HASHNODE_LIKE_POST` | Hashnode Like Post | Tool to like a post on Hashnode. Use when you want to add a like/reaction to a specific post. Requires a valid post ID. |
| `HASHNODE_LIKE_REPLY` | Hashnode: Like Reply | Tool to like a reply on Hashnode. Use when you have a reply ID and want to add a like to that reply. |
| `HASHNODE_LIST_PUBLICATIONS` | Hashnode: List Publications | Tool to list all publications of the authenticated user. Use when you need your publication hostnames for downstream actions. |
| `HASHNODE_LIST_TOP_COMMENTERS` | Hashnode: List Top Commenters | Tool to fetch users who have most actively participated in discussions by commenting in the last 7 days. Use when you need to identify top contributors or most engaged users. |
| `HASHNODE_MAP_DOC_PROJECT_CUSTOM_DOMAIN_WWW_REDIRECT` | Hashnode: Map Documentation Project WWW Redirect | Tool to configure WWW redirect for a documentation project's custom domain. Use when you need to enable automatic www subdomain redirection (e.g., www.docs.example.com -> docs.example.com). The project must already have a custom domain added before calling this action. |
| `HASHNODE_ME` | Hashnode: Get Current User | Retrieves profile details of the currently authenticated Hashnode user. Returns the user's identity (id, username, name), profile info (bio, tagline, profile picture, location), social links (website, github, twitter, linkedin), engagement metrics (followers/followings count), and badges. Use this action to get user context for personalization, verify authentication, or retrieve user data for display purposes. |
| `HASHNODE_MOVE_DOCUMENTATION_SIDEBAR_ITEM` | Move Documentation Sidebar Item | Tool to reorder documentation sidebar items within a Hashnode guide. Use when you need to change the position of a sidebar item or move it under a different parent section. Requires the projectId, guideSlug, and itemId. |
| `HASHNODE_PUBLISH_DOCUMENTATION_API_REFERENCE` | Publish Documentation API Reference | Tool to publish a documentation API reference in a Hashnode documentation project. Use when you need to make an API reference guide publicly available. Requires a projectId and guideSlug. |
| `HASHNODE_PUBLISH_POST` | Hashnode Publish Post | Tool to publish a new blog post to a Hashnode publication. Use when you need to create and immediately publish an article. Requires a publicationId (obtainable via HASHNODE_LIST_PUBLICATIONS), title, and markdown content. |
| `HASHNODE_REMOVE_COMMENT` | Hashnode Remove Comment | Tool to remove a comment from a Hashnode post. Use after confirming the comment ID. Returns the ID of the removed comment upon success. |
| `HASHNODE_REMOVE_DOCUMENTATION_GUIDE` | Hashnode Remove Documentation Guide | Tool to remove a documentation guide from a Hashnode project. Use after confirming the project ID and guide slug. This action is destructive and cannot be undone. |
| `HASHNODE_REMOVE_DOCUMENTATION_PROJECT` | Remove Documentation Project | Tool to remove a documentation project from Hashnode. This action frees the custom domain and subdomain and removes all guides and pages. Use after confirming the project ID to be deleted. |
| `HASHNODE_REMOVE_DOCUMENTATION_PROJECT_CUSTOM_DOMAIN` | Hashnode Remove Documentation Project Custom Domain | Tool to remove a custom domain from a Hashnode documentation project. Use when you need to detach a custom domain from a documentation project, reverting it to use only the Hashnode subdomain. |
| `HASHNODE_REMOVE_DOCUMENTATION_SIDEBAR_ITEM` | Remove Documentation Sidebar Item | Tool to remove a sidebar item from a documentation guide on Hashnode. Use when you need to delete a section or page from a guide's sidebar navigation. This action is destructive and cannot be undone. |
| `HASHNODE_REMOVE_POST` | Hashnode Remove Post | Tool to remove (delete) a post from Hashnode. Use after confirming the post ID to be deleted. This action is destructive and cannot be undone. |
| `HASHNODE_REMOVE_REPLY` | Hashnode Remove Reply | Tool to remove a reply from a comment. Use after confirming comment and reply IDs. Returns the removed reply details. |
| `HASHNODE_RENAME_DOCUMENTATION_GUIDE` | Hashnode Rename Documentation Guide | Tool to rename a documentation guide in a Hashnode project. Use when you need to update the name of an existing guide. Requires the projectId, guideSlug, and new name. |
| `HASHNODE_RENAME_DOCUMENTATION_SIDEBAR_ITEM` | Rename Documentation Sidebar Item | Tool to rename a documentation sidebar item within a Hashnode guide. Use when you need to update the display label of a sidebar item (link, page, or section). Requires the projectId, guideSlug, itemId, and new label. |
| `HASHNODE_RESTORE_POST` | Hashnode Restore Post | Tool to restore a previously deleted Hashnode post. Use when you need to undo a post deletion and make the post accessible again. Requires the post ID of the deleted post. |
| `HASHNODE_SAVE_DOCUMENTATION_PAGE_DRAFT_CONTENT` | Save Documentation Page Draft Content | Tool to save draft content for a documentation page in Hashnode. Use when you need to update the content, title, or description of an existing documentation page draft. Requires pageId and projectId, along with at least one of content, title, or description. |
| `HASHNODE_SEARCH_POSTS_OF_PUBLICATION` | Search Posts of Publication | Tool to search and retrieve posts from a specific publication based on a search query. Use when you need to find posts matching specific keywords within a particular Hashnode publication. Supports pagination and sorting by publication date. |
| `HASHNODE_SUBSCRIBE_TO_NEWSLETTER` | Subscribe to Newsletter | Tool to subscribe an email address to a Hashnode publication's newsletter. Use when you need to add a subscriber to a publication's mailing list. Requires a publicationId (obtainable via HASHNODE_LIST_PUBLICATIONS or GET_PUBLICATION) and a valid email address. |
| `HASHNODE_TOGGLE_FOLLOW_USER` | Hashnode: Toggle Follow User | Tool to toggle follow status for a Hashnode user. If you don't follow the user, this will follow them. If you already follow them, this will unfollow them. Use when you need to manage following relationships for the authenticated user. |
| `HASHNODE_UNFOLLOW_TAGS` | Hashnode: Unfollow Tags | Unfollow specified tags to customize your content feed on Hashnode. Use when you want to unsubscribe from content from specific tags to personalize your feed. |
| `HASHNODE_UNSUBSCRIBE_FROM_NEWSLETTER` | Unsubscribe from Newsletter | Tool to unsubscribe an email address from a Hashnode publication's newsletter. Use when you need to remove a subscriber from a publication's mailing list. Requires a publicationId (obtainable via HASHNODE_LIST_PUBLICATIONS or GET_PUBLICATION) and a valid email address. |
| `HASHNODE_UPDATE_COMMENT` | Hashnode Update Comment | Tool to update an existing comment on a Hashnode post. Use after preparing updated content details. |
| `HASHNODE_UPDATE_CONTENT_BLOCK` | Hashnode Update Content Block | Tool to update a content block in a Hashnode documentation project. Use when you need to modify the label or content of an existing embeddable content block (such as code snippets, widgets, or other custom content). |
| `HASHNODE_UPDATE_DOCUMENTATION_APPEARANCE` | Update Documentation Appearance | Tool to update the appearance settings of a Hashnode documentation project. Use when you need to customize the look and feel of a documentation site, including logos, colors, themes, and custom scripts. |
| `HASHNODE_UPDATE_DOCUMENTATION_GENERAL_SETTINGS` | Update Documentation General Settings | Tool to update general settings of a Hashnode documentation project. Use when you need to modify the name, description, custom CSS, or external links of an existing documentation site. Requires the project ID and at least one field to update. |
| `HASHNODE_UPDATE_DOCUMENTATION_GUIDE` | Update Hashnode Documentation Guide | Tool to update an existing documentation guide in a Hashnode project. Use when you need to modify the name, slug, or SEO meta tags of a guide. Requires the projectId and guideId of the guide to update. |
| `HASHNODE_UPDATE_DOCUMENTATION_INTEGRATIONS` | Hashnode: Update Documentation Integrations | Tool to update third-party integrations for a Docs by Hashnode project. Use when you need to configure analytics (Google Analytics, Clarity), tag management (GTM), customer support (Intercom), marketing pixels (Facebook Pixel, Hotjar), or visitor tracking (Koala) on a documentation site. |
| `HASHNODE_UPDATE_DOCUMENTATION_LINK` | Update Documentation Link | Tool to update an existing link within a Hashnode documentation guide. Use when you need to modify the label or URL of a documentation link. Requires the project ID, guide slug, link ID, and updated label (URL is optional). |
| `HASHNODE_UPDATE_DOCUMENTATION_PROJECT_SUBDOMAIN` | Hashnode: Update Documentation Project Subdomain | Tool to update the subdomain of a Hashnode documentation project. Use when you need to change the subdomain (e.g., from 'old-docs.hashnode.dev' to 'new-docs.hashnode.dev') for a documentation project. |
| `HASHNODE_UPDATE_DOCUMENTATION_SECTION` | Hashnode Update Documentation Section | Tool to update a section in a Hashnode documentation guide. Use when you need to modify the label, slug, or visibility of an existing documentation section. |
| `HASHNODE_UPDATE_POST` | Hashnode Update Post | Tool to update an existing Hashnode post via the updatePost mutation. Use when you need to modify the title, content, tags, or other attributes of an already published or drafted post. |
| `HASHNODE_UPDATE_REPLY` | Hashnode Update Reply | Tool to update a reply. Use when editing an existing reply to a comment after confirming the comment and reply IDs. |
| `HASHNODE_VERIFY_DOCUMENTATION_PROJECT_CUSTOM_DOMAIN` | Hashnode Verify Documentation Project Custom Domain | Tool to verify a custom domain for a Hashnode documentation project. Use when you need to confirm DNS configuration and activate a custom domain that was previously added to the project. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Hashnode MCP server is an implementation of the Model Context Protocol that connects your AI agent to Hashnode. It provides structured and secure access so your agent can perform Hashnode operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

No description provided.

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider.
- Keep the API key safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

No description provided.
```python
pip install composio-langchain langchain-mcp-adapters langchain python-dotenv
```

```typescript
npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates your requests to Composio's API
- COMPOSIO_USER_ID identifies the user for session management
- OPENAI_API_KEY enables access to OpenAI's language models
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import dependencies

No description provided.
```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()
```

```typescript
import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
```

### 5. Initialize Composio client

What's happening:
- We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
- Creating a Composio instance that will manage our connection to Hashnode tools
- Validating that COMPOSIO_USER_ID is also set before proceeding
```python
async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
```

```typescript
const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
```

### 6. Create a Tool Router session

What's happening:
- We're creating a Tool Router session that gives your agent access to Hashnode tools
- The create method takes the user ID and specifies which toolkits should be available
- The returned session.mcp.url is the MCP server URL that your agent will use
- This approach allows the agent to dynamically load and use Hashnode tools as needed
```python
# Create Tool Router session for Hashnode
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['hashnode']
)

url = session.mcp.url
```

```typescript
const session = await composio.create(
    userId as string,
    {
        toolkits: ['hashnode']
    }
);

const url = session.mcp.url;
```

### 7. Configure the agent with the MCP URL

No description provided.
```python
client = MultiServerMCPClient({
    "hashnode-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

agent = create_agent("gpt-5", tools)
```

```typescript
const client = new MultiServerMCPClient({
    "hashnode-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
```

### 8. Set up interactive chat interface

No description provided.
```python
conversation_history = []

print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Hashnode related question or task to the agent.\n")

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ['exit', 'quit', 'bye']:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")
```

```typescript
let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Hashnode related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
```

### 9. Run the application

No description provided.
```python
if __name__ == "__main__":
    asyncio.run(main())
```

```typescript
main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
```

## Complete Code

```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['hashnode']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "hashnode-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any Hashnode related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

if __name__ == "__main__":
    asyncio.run(main())
```

```typescript
import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['hashnode']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "hashnode-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Hashnode related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
```

## Conclusion

You've successfully built a LangChain agent that can interact with Hashnode through Composio's Tool Router.
Key features of this implementation:
- Dynamic tool loading through Composio's Tool Router
- Conversation history maintenance for context-aware responses
- Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

## How to build Hashnode MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/hashnode/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/hashnode/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/hashnode/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/hashnode/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/hashnode/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/hashnode/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/hashnode/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/hashnode/framework/cli)
- [Google ADK](https://composio.dev/toolkits/hashnode/framework/google-adk)
- [Vercel AI SDK](https://composio.dev/toolkits/hashnode/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/hashnode/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/hashnode/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/hashnode/framework/crew-ai)

## Related Toolkits

- [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.
- [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.
- [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.
- [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences.
- [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses.
- [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure.
- [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure.
- [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction.
- [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting.
- [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache.
- [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence.
- [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place.
- [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines.
- [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure.
- [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code.
- [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows.
- [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights.
- [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews.
- [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease.
- [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Hashnode MCP?

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.

### Can I use Tool Router MCP with LangChain?

Yes, you can. LangChain 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.

### Can I manage the permissions and scopes for Hashnode while using Tool Router?

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.

### How safe is my data with Composio Tool Router?

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.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)