How to Use the Mastodon MCP in LangChain

Q: Can LangChain chains handle media uploads to Mastodon?

Yes, your LangChain agent can chain uploadmedia and poststatus together. The agent first uploads the file, retrieves the media ID from the tool output, and then passes that ID to the status creation tool in the next step of the chain.

Q: Can I filter the timeline before my agent reads it?

Yes. Your agent can call gethometimeline or gettagtimeline and run the raw text through a LangChain parser. This lets you filter out noise, extract key metrics, or search for specific keywords before passing the data to your LLM.

Chain together Mastodon API actions inside your LangChain agents to post, read timelines, and moderate accounts in single execution runs.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Mastodon MCP to LangChain

Create your Vinkius account to connect Mastodon to LangChain and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Mastodon with LangChain

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Sequence Fedi actions with LangChain chains

The `post_status` and `upload_media` tools let your LangChain agents publish media-rich updates to the Fediverse in a single, observable sequence. By mapping the output of a research chain directly to these tools, your agent posts updates without manual intervention or context switching. You can monitor every step of this automated posting pipeline using LangSmith. This visibility ensures you see exactly what text went into the `post_status` tool and can debug failed media attachments before they hit your public feed.

Automate moderation via this Mastodon MCP Server

This MCP Server exposes tools like `block_account`, `mute_account`, and `clear_notifications` to help you manage your digital space through LangChain's ReAct framework. Your agent can read incoming notifications using `get_notifications_v2`, evaluate them against your custom rules, and take immediate defensive actions. LangChain's multi-step reasoning ensures the agent doesn't just blindly block users. Instead, it checks the offending account's profile via `get_account` and only runs `block_account` if the profile matches your specific spam criteria.

Analyze trending topics across instances

Use `get_trending_tags`, `get_trending_statuses`, and `get_trending_links` to feed live Fediverse trends directly into your LangChain summarization pipelines. This setup lets your agent pull what's hot right now and immediately draft relevant responses or reports based on actual live data. Because LangChain supports over 500 integrations, you can instantly feed these trending Mastodon statuses into a vector database. This means you avoid writing boilerplate API connector code.

Setup guide

Set up Mastodon MCP in LangChain

Prerequisites

Python 3.10+ installed
langchain-mcp-adapters + langgraph packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install langchain-mcp-adapters langgraph langchain-openai. The MCP adapters package converts MCP tools into native LangChain BaseTool objects.
2

Connect via HTTP transport
Use MultiServerMCPClient with "transport": "http" pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create a ReAct agent
Pass the discovered tools to create_react_agent() from LangGraph. The agent automatically routes Mastodon tool calls through the MCP protocol.
4

Run with any LLM
Swap ChatOpenAI for ChatAnthropic, ChatGoogleGenerativeAI, or any LangChain-compatible model. The MCP tools work identically across all providers.

agent.py

from langchain_mcp_adapters.client import MultiServerMCPClient
from langgraph.prebuilt import create_react_agent
from langchain_openai import ChatOpenAI

async with MultiServerMCPClient({
    "mastodon-mcp": {
        "transport": "http",
        "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    }
}) as client:
    tools = client.get_tools()

    agent = create_react_agent(
        ChatOpenAI(model="gpt-4o"),
        tools,
    )
    result = await agent.ainvoke({
        "messages": "List recent Mastodon transactions"
    })
    print(result["messages"][-1].content)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Mastodon. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Mastodon now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Mastodon MCP in LangChain

Look, the setup is simple: you provide your instance URL and access token as environment variables when starting the MCP Server. LangChain then accesses tools like `verify_credentials` securely through the MultiServerMCPClient configuration, keeping your keys out of the actual LLM prompts.

Yes, your LangChain agent can chain `upload_media` and `post_status` together. The agent first uploads the file, retrieves the media ID from the tool output, and then passes that ID to the status creation tool in the next step of the chain.

The server returns standard Mastodon API rate limit errors directly to your LangChain agent. You should configure your LangChain runnables or LangGraph nodes with retry logic to handle these 429 status codes when making heavy use of tools like `get_home_timeline`.

Yes. Your agent can call `get_home_timeline` or `get_tag_timeline` and run the raw text through a LangChain parser. This lets you filter out noise, extract key metrics, or search for specific keywords before passing the data to your LLM.

Your account credentials, private direct messages, and draft statuses never leave your local environment. Vinkius runs the server in an isolated sandbox, meaning your API tokens and raw Mastodon status data are processed ephemerally and never stored on external servers.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript