2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 12 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Fellow as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to Fellow. "
            "You have 12 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in Fellow?"
    )
    print(response)

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.

LlamaIndex agents combine Fellow tool responses with indexed documents for comprehensive, grounded answers. Connect 12 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

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 LlamaIndex 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 LlamaIndex via MCP

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

01

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.py and run: python agent.py

04

Explore tools

The agent discovers 12 tools from Fellow

Why Use LlamaIndex with the Fellow MCP Server

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

01

Data-first architecture: LlamaIndex agents combine Fellow tool responses with indexed documents for comprehensive, grounded answers

02

Query pipeline framework lets you chain Fellow tool calls with transformations, filters, and re-rankers in a typed pipeline

03

Multi-source reasoning: agents can query Fellow, a vector store, and a SQL database in a single turn and synthesize results

04

Observability integrations show exactly what Fellow tools were called, what data was returned, and how it influenced the final answer

Fellow + LlamaIndex Use Cases

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

01

Hybrid search: combine Fellow real-time data with embedded document indexes for answers that are both current and comprehensive

02

Data enrichment: query Fellow to augment indexed data with live information before generating user-facing responses

03

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Fellow for fresh data

04

Analytical workflows: chain Fellow queries with LlamaIndex's data connectors to build multi-source analytical reports

Fellow MCP Tools for LlamaIndex (12)

These 12 tools become available when you connect Fellow to LlamaIndex 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 LlamaIndex

Ready-to-use prompts you can give your LlamaIndex 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 LlamaIndex

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

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Fellow + LlamaIndex FAQ

Common questions about integrating Fellow MCP Server with LlamaIndex.

01

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
02

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query Fellow tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
03

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

Connect Fellow to LlamaIndex

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