Which TOTVS systems are compatible with this MCP?

This MCP is designed to work with standard REST APIs from Protheus, RM, and Fluig. Ensure your specific instance has the relevant API modules enabled.

How do I find my TOTVS Base URL?

The Base URL is the address of your ERP or Fluig web service (e.g., `https://erp.mycompany.com:8080/rest`). You can find this in your system's technical documentation or environment settings.

Can I automatically advance a Fluig process request?

Yes! Use the `advance_process` tool with the specific Process Instance ID. Your agent will trigger the workflow transition based on the logic defined in Fluig.

TOTVS MCP Server for CrewAI 11 tools — connect in under 2 minutes

Name: TOTVS
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to TOTVS through Vinkius, pass the Edge URL in the `mcps` parameter and every TOTVS tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="TOTVS Specialist",
    goal="Help users interact with TOTVS effectively",
    backstory=(
        "You are an expert at leveraging TOTVS tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in TOTVS "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 available tools "
        "and what they can do."
    ),
)

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

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 TOTVS MCP Server

Connect your AI agents to TOTVS, the largest technology company in Brazil and Latin America. This MCP provides 10 tools to manage organizational data across Protheus, RM, and Fluig ecosystems, enabling seamless orchestration of HR, Financial, and Business Process Management (BPM) workflows.

When paired with CrewAI, TOTVS becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call TOTVS tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

HR Orchestration — List employees and retrieve detailed profiles across the organization
Financial Control — Monitor accounts payable/receivable and list real-time receipts and payments
BPM Workflows — Track and advance process requests in Fluig and manage the Electronic Content Management (ECM) system
Multi-System Access — Unified interaction with Protheus, RM, and Fluig through a single AI interface

The TOTVS MCP Server exposes 11 tools through the Vinkius. Connect it to CrewAI 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 TOTVS to CrewAI via MCP

Follow these steps to integrate the TOTVS MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 11 tools from TOTVS

Why Use CrewAI with the TOTVS MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with TOTVS through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

TOTVS + CrewAI Use Cases

Practical scenarios where CrewAI combined with the TOTVS MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries TOTVS for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries TOTVS, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain TOTVS tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries TOTVS against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

TOTVS MCP Tools for CrewAI (11)

These 11 tools become available when you connect TOTVS to CrewAI via MCP:

get_available_services

List available RM DataServers

get_employee_details

Get detailed information for a specific employee

get_process_request

Get details for a specific Fluig process request

get_rm_data

Query a specific record from an RM DataServer

list_companies

List all companies and branches in the Protheus environment

list_documents

List documents in the Fluig ECM

list_employees

List employees from the HR module

list_payments

List accounts payable (Finance)

list_processes

List all BPM processes in Fluig

list_receipts

List accounts receivable (Finance)

move_process_request

Advance a Fluig process request to the next state

Example Prompts for TOTVS in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with TOTVS immediately.

"List all active employees in my TOTVS RM environment."

"Show the accounts payable summary for this month from Protheus."

"List all pending workflow requests in Fluig."

Troubleshooting TOTVS MCP Server with CrewAI

Common issues when connecting TOTVS to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

TOTVS + CrewAI FAQ

Common questions about integrating TOTVS MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.