How to Use the Document360 MCP in CrewAI

Q: How do I add the Document360 MCP Server to a CrewAI agent?

Pass your Vinkius HTTP URL directly into the mcps parameter when defining your CrewAI agent. The framework automatically discovers tools like listarticles and makes them available to the agent.

Q: How do I restrict a CrewAI agent to only read Document360 articles?

Use the MCPServerHTTP class from the CrewAI MCP module and apply a toolfilter. This lets you expose only getarticle and listarticles while hiding administrative tools like listteam.

Deploy specialized agent crews to audit, organize, and update your Document360 knowledge base autonomously.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Document360 MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Deploy a specialized CrewAI squad to audit your docs

Assign distinct roles to your CrewAI agents using `analytics` to find low-performing pages. An analyst agent tracks down the weak spots, while a writer agent runs `get_article` to read the actual content. This MCP Server allows the agents to work in parallel. They share context dynamically, ensuring that the editor agent knows exactly which categories to restructure based on real user behavior.

Coordinate multi-agent search and rescue for broken docs

Let your agents hunt down missing information across your entire project using the `search` tool. A researcher agent uses the tool to look for broken links or outdated terms across all active versions. Once found, a coordinator agent calls `list_categories` to find the best place for new articles. The crew operates autonomously, escalating complex structural issues to your team only when necessary.

Manage team assignments and workloads autonomously

Keep your documentation team organized using `list_team` to see active members. A manager agent can run the tool to see active members, then cross-reference this with recent article updates. By querying `list_projects`, the CrewAI squad maps out which writers are assigned to which versions. The system then balances the workload by flagging unassigned articles to the correct team lead.

Setup guide

Set up Document360 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 Document360 tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Document360 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="Document360 Analyst",
        goal="Access and analyze Document360 data via MCP.",
        backstory="Expert analyst with direct Document360 access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Document360 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 Document360. 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 Document360 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 Document360 MCP in CrewAI

Pass your Vinkius HTTP URL directly into the `mcps` parameter when defining your CrewAI agent. The framework automatically discovers tools like `list_articles` and makes them available to the agent.

Yes, CrewAI supports parallel tool execution. Your researcher agent can run `search` while your analyst agent queries `analytics` without blocking each other.

Use the `MCPServerHTTP` class from the CrewAI MCP module and apply a `tool_filter`. This lets you expose only `get_article` and `list_articles` while hiding administrative tools like `list_team`.

Yes, you can define a sequential process where Agent A calls `list_categories` to find a slot, Agent B drafts the content, and Agent C verifies it using the `search` tool.

Vinkius runs the MCP Server in an isolated V8 sandbox. Your team roster, analytics logs, and article drafts are only accessed via secure, encrypted tool calls initiated by your autonomous crew.

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