How to Use the AlgoDocs MCP in CrewAI

Q: How do I give different AlgoDocs tools to different agents in CrewAI?

When defining your Agent in CrewAI, use the toolfilter argument with the MCPServerHTTP class. This lets you expose only specific tools, like giving uploaddocumentfromurl to one agent and getdocumentdata to another.

Q: How would an agent in CrewAI find the right document folder in AlgoDocs?

The agent would use the listfolders tool to get a directory of all available folders. Based on its goal, it can then parse the list and identify the correct folder to work with, using getfolderdetails if it needs more info.

Q: What's the best way to do batch processing with AlgoDocs and CrewAI?

Assign an agent to periodically call listextractordata. This tool is made for grabbing bulk results. The agent can then process all the new data at once or delegate each item to other agents for parallel processing.

Deploy a crew of AI agents with CrewAI to automate your entire AlgoDocs document lifecycle.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect AlgoDocs MCP to CrewAI

Create your Vinkius account to connect AlgoDocs to CrewAI 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 AlgoDocs with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Assign roles for document processing

With CrewAI, you can build a team of specialized agents. Assign a 'Clerk' agent the job of submitting new files using `upload_document_from_url`. This agent's only task is to get documents into the system. Meanwhile, a separate 'Auditor' agent can periodically run `get_document_status` on all in-progress jobs. If a job gets stuck or fails, the Auditor can delegate the problem to an 'Operator' agent for resolution. This divides the labor just like a human team.

Create an autonomous analysis crew

Once a document is processed, the 'Clerk' agent passes the document ID to an 'Analyst' agent. The Analyst's job is to use `get_document_data` to pull the structured data and look for key information. This Analyst agent can then collaborate with a 'Reporter' agent. The Analyst finds the data, and the Reporter formats it into a summary. This MCP server provides the raw data; your CrewAI team provides the intelligence.

Build monitoring and admin agents with CrewAI

Dedicate one agent in your crew to be the 'Accountant.' Its job is to use `get_my_account` and `get_api_usage` to watch your AlgoDocs consumption. If usage spikes, it can alert you or even pause other agents. You can also have a 'Librarian' agent that uses `list_folders` and `list_recent_documents` to maintain an index of all processed files. This creates a searchable knowledge base, managed entirely by your autonomous crew.

Setup guide

Set up AlgoDocs MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke AlgoDocs tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="AlgoDocs Analyst",
    goal="Access and analyze AlgoDocs data via MCP.",
    backstory="Expert analyst with direct AlgoDocs access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent AlgoDocs transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="AlgoDocs Analyst",
        goal="Access and analyze AlgoDocs data via MCP.",
        backstory="Expert analyst with direct AlgoDocs access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent AlgoDocs transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

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 AlgoDocs. 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 AlgoDocs 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 AlgoDocs MCP in CrewAI

When defining your Agent in CrewAI, use the `tool_filter` argument with the MCPServerHTTP class. This lets you expose only specific tools, like giving `upload_document_from_url` to one agent and `get_document_data` to another.

Absolutely. One agent can submit the doc, a second can monitor its status with `get_document_status`, and a third can analyze the results from `get_document_data`. This is exactly what CrewAI's multi-agent system is designed for.

The agent would use the `list_folders` tool to get a directory of all available folders. Based on its goal, it can then parse the list and identify the correct folder to work with, using `get_folder_details` if it needs more info.

Assign an agent to periodically call `list_extractor_data`. This tool is made for grabbing bulk results. The agent can then process all the new data at once or delegate each item to other agents for parallel processing.

Your CrewAI agents connect to the MCP server via a secure URL with a Vinkius-managed token. The server only processes the document data from the URLs your agents submit. The entire execution happens in an isolated, zero-trust sandbox that is wiped clean after the job is done.

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