4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
TOTVS MCP Server

Bring Totvs
to CrewAI

Learn how to connect TOTVS to CrewAI and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get Available ServicesGet Employee DetailsGet Process RequestGet Rm DataList CompaniesList DocumentsList EmployeesList PaymentsList ProcessesList ReceiptsMove Process Request

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
TOTVS

What is the 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.

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

How it works

  1. Subscribe to this server
  2. Log in to your TOTVS Portal
  3. Navigate to Web Services / API Settings in your ERP (Protheus/RM) or Fluig instance
  4. Obtain your Username, Password, and Base URL
  5. Identify your Tenant ID or Company ID if required
  6. Connect your account to Vurb to start managing your enterprise data.

Who is this for?

  • HR Business Partners — quickly retrieve employee data and monitor leave trends via natural language
  • Finance Teams — automate the monitoring of accounts and payment statuses smoothly
  • Process Analysts — track and advance business workflows across the organizational ecosystem

Built-in capabilities (11)

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

Why CrewAI?

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.

  • 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

See it in action

TOTVS in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

TOTVS and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect TOTVS to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for TOTVS in CrewAI

The TOTVS 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. All 11 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

TOTVS
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

The Vinkius Advantage

How Vinkius secures TOTVS for CrewAI

Every tool call from CrewAI to the TOTVS MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

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

10

Agent not using tools

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

11

Timeout errors

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

12

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.

Explore More MCP Servers

View all →