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

Bring Totvs
to Claude Desktop

Learn how to connect TOTVS to Claude Desktop 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 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

See it in action

TOTVS in Claude Desktop

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 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.

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 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.

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 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.

< 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 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.

05

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.

06

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.

07

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.

08

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.

09

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).

10

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

11

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 →