2,500+ MCP servers ready to use
Vinkius

Fellow MCP Server for LangChain 12 tools — connect in under 2 minutes

Built by Vinkius GDPR 12 Tools Framework

LangChain is the leading Python framework for composable LLM applications. Connect Fellow through Vinkius and LangChain agents can call every tool natively. combine them with retrievers, memory, and output parsers for sophisticated AI pipelines.

Vinkius supports streamable HTTP and SSE.

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

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with MultiServerMCPClient({
        "fellow": {
            "transport": "streamable_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,
        )
        response = await agent.ainvoke({
            "messages": [{
                "role": "user",
                "content": "Using Fellow, show me what tools are available.",
            }]
        })
        print(response["messages"][-1].content)

asyncio.run(main())
Fellow
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Fellow MCP Server

Connect your Fellow.app account to any AI agent and take full control of your meeting management, collaborative agendas, and action item tracking through natural conversation.

LangChain's ecosystem of 500+ components combines seamlessly with Fellow through native MCP adapters. Connect 12 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.

What you can do

  • Meeting Note Orchestration — List all meeting notes and retrieve full structured content including agenda items, discussion points, and decision metadata natively
  • Action Item Auditing — List and filter all tasks across meetings to track descriptions, assignees, and due dates for cross-meeting accountability flawlessly
  • Recording Management — Browse meeting recordings and retrieve video/audio details including time-limited download or stream URLs securely
  • AI Transcription Retrieval — Fetch full transcripts with speaker attribution and timestamps to review critical discussions or extract specific insights limitlessly
  • Task Lifecycle Control — Mark action items as complete or archive them to manage your active workspace and notify relevant stakeholders synchronously
  • Identity Oversight — Retrieve the authenticated profile identity including name, email, and workspace contexts to verify permission limits natively
  • Data Invalidation — Irreversibly vaporize specific meeting notes or recordings findable by ID to manage your organizational records strictly

The Fellow MCP Server exposes 12 tools through the Vinkius. Connect it to LangChain in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Fellow to LangChain via MCP

Follow these steps to integrate the Fellow MCP Server with LangChain.

01

Install dependencies

Run pip install langchain langchain-mcp-adapters langgraph langchain-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save the code and run python agent.py

04

Explore tools

The agent discovers 12 tools from Fellow via MCP

Why Use LangChain with the Fellow MCP Server

LangChain provides unique advantages when paired with Fellow through the Model Context Protocol.

01

The largest ecosystem of integrations, chains, and agents. combine Fellow MCP tools with 500+ LangChain components

02

Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step

03

LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging

04

Memory and conversation persistence let agents maintain context across Fellow queries for multi-turn workflows

Fellow + LangChain Use Cases

Practical scenarios where LangChain combined with the Fellow MCP Server delivers measurable value.

01

RAG with live data: combine Fellow tool results with vector store retrievals for answers grounded in both real-time and historical data

02

Autonomous research agents: LangChain agents query Fellow, synthesize findings, and generate comprehensive research reports

03

Multi-tool orchestration: chain Fellow tools with web scrapers, databases, and calculators in a single agent run

04

Production monitoring: use LangSmith to trace every Fellow tool call, measure latency, and optimize your agent's performance

Fellow MCP Tools for LangChain (12)

These 12 tools become available when you connect Fellow to LangChain via MCP:

01

archive_action_item

Archive an action item, removing it from active views without deleting it

02

complete_action_item

Use when a task has been finished. Mark an action item as complete

03

delete_note

Confirm with the user before executing — this cannot be undone. Permanently delete a meeting note by ID

04

delete_recording

Confirm with the user before executing. Permanently delete a meeting recording by ID

05

get_action_item

Use to inspect a single task. Retrieve details of a specific action item by ID

06

get_current_user

Use to verify which account is connected. Retrieve the authenticated Fellow user profile

07

get_note

Essential for reviewing a specific meeting. Retrieve the full content and metadata of a specific meeting note by ID

08

get_recording

Use to access a specific recording. Retrieve details of a specific meeting recording

09

get_transcript

Use for detailed review, compliance documentation, or extracting specific discussion points. Retrieve the full transcript of a meeting recording

10

list_action_items

Use for cross-meeting task tracking and accountability. List all action items across all meetings

11

list_notes

Use as the primary entry point to browse all meeting documentation. List all meeting notes in the Fellow workspace

12

list_recordings

Use to browse all recorded meetings. List all meeting recordings captured by Fellow

Example Prompts for Fellow in LangChain

Ready-to-use prompts you can give your LangChain agent to start working with Fellow immediately.

01

"Show me all my pending action items"

02

"Get the notes for the meeting 'Product Sync' from last Tuesday"

03

"List the last 3 meeting recordings"

Troubleshooting Fellow MCP Server with LangChain

Common issues when connecting Fellow to LangChain through the Vinkius, and how to resolve them.

01

MultiServerMCPClient not found

Install: pip install langchain-mcp-adapters

Fellow + LangChain FAQ

Common questions about integrating Fellow MCP Server with LangChain.

01

How does LangChain connect to MCP servers?

Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
02

Which LangChain agent types work with MCP?

All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
03

Can I trace MCP tool calls in LangSmith?

Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.

Connect Fellow to LangChain

Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.