Compatible with every major AI agent and IDE
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
- Subscribe to this server
- Log in to your TOTVS Portal
- Navigate to Web Services / API Settings in your ERP (Protheus/RM) or Fluig instance
- Obtain your Username, Password, and Base URL
- Identify your Tenant ID or Company ID if required
- 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)
List available RM DataServers
Get detailed information for a specific employee
Get details for a specific Fluig process request
Query a specific record from an RM DataServer
List all companies and branches in the Protheus environment
List documents in the Fluig ECM
List employees from the HR module
List accounts payable (Finance)
List all BPM processes in Fluig
List accounts receivable (Finance)
Advance a Fluig process request to the next state
Why Claude Desktop?
Claude Desktop is the definitive way to connect TOTVS to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 11 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
TOTVS in Claude Desktop
TOTVS and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect TOTVS to Claude Desktop 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for TOTVS in Claude Desktop
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 Claude Desktop 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.

* 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
How Vinkius secures
TOTVS for Claude Desktop
Every tool call from Claude Desktop to the TOTVS MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Cloopen / 容联云
10 toolsLeading cloud communication platform in China — manage SMS, voice calls, and applications via AI.

Better Stack
10 toolsMonitor uptime and incidents via Better Stack — list monitors, heartbeats, and on-call schedules directly from any AI agent.

Amplitude
10 toolsAnalyze product data via Amplitude — get user activity, calculate retention, analyze funnels, and track revenue directly from any AI agent.

Vercel
11 toolsDeploy frontend applications instantly with a platform optimized for Next.js, serverless functions, and edge computing globally.
