TOTVS MCP. Manage HR, Finance, and BPM data across Protheus, RM, and Fluig.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
TOTVS MCP Server connects your AI agent to Protheus, RM, and Fluig ecosystems. It lets you manage employee data, check accounts payable/receivable, and track BPM workflows across major Brazilian and Latin American enterprise systems from one place.
What your AI agents can do
Get available services
Lists all available data servers within the RM environment so you know what systems are connected.
Get employee details
Pulls detailed profile information for a single, specified employee record.
Get process request
Retrieves all details about one specific workflow request in the Fluig system.
List all employees or pull detailed profiles for specific staff members using list_employees or get_employee_details.
Check accounts payable (list_payments) and receivable (list_receipts), getting summaries of pending payments and received funds from the finance modules.
View, track, and move process requests in Fluig using get_process_request or advancing them with move_process_request.
Run targeted queries against specific databases or record types via tools like get_rm_data.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
TOTVS MCP Server: 11 Tools for ERP & HR
Use these tools to query RM data, manage employee details, monitor process requests, and list core financial records across the TOTVS environment.
019d8490get available services
Lists all available data servers within the RM environment so you know what systems are connected.
019d8490get employee details
Pulls detailed profile information for a single, specified employee record.
019d8490get process request
Retrieves all details about one specific workflow request in the Fluig system.
019d8490get rm data
Runs a targeted query to pull any specific record type from an RM DataServer.
019d8490list companies
Lists every company and branch registered within the Protheus environment for organizational context.
019d8490list documents
Retrieves a list of all documents stored in the Fluig Electronic Content Management (ECM).
019d8490list employees
Gets a foundational listing of all employees currently registered in the HR module.
019d8490list payments
Lists outstanding accounts payable records, giving you visibility into bills that need paying (Finance).
019d8490list processes
Shows an index of every workflow process defined within the Fluig BPM system.
019d8490list receipts
Lists accounts receivable records, detailing money that has been received or is due to be collected (Finance).
019d8490move process request
Advances a specific Fluig process request from its current state to the next required step.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with TOTVS, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
This server hooks up your AI agent directly to the heart of big Brazilian and Latin American enterprise systems, including Protheus, RM, and Fluig. You can manage employee data, check out accounts payable and receivable, and track complex BPM workflows across major company backends from one place. It lets you stop hopping between three different portals just to get basic financial or HR info.
Managing People Records (HR)
You've got two ways to handle staff details. You can start by running list_employees to grab a foundational list of every employee registered in the HR module; it’s like getting the master directory. If you need more than just names, you can run get_employee_details and pull up the full profile for one specific staff member—you'll get all their detailed info there.
Handling Money Flow (Finance)
Checking accounts payable and receivable doesn't have to be a headache. To see what bills are waiting to get paid, you run list_payments, which gives you visibility into all outstanding accounts payable records. For money that’s coming in, you use list_receipts; this tool lists your accounts receivable records and details exactly what was received or is due for collection.
Before checking the books, you might need context on where the company sits—you can run list_companies to get a full rundown of every registered company and branch in the Protheus environment.
Driving Workflows (BPM & Documents)
Fluig is where your business processes live. If you're tracking a specific approval, you use get_process_request to pull up all the details about that one workflow request. You can then actually move it forward by invoking move_process_request, which advances a particular Fluig process from its current stalled state to the next required step in the chain.
If you need an index of all possible processes, running list_processes shows you every single workflow defined within the BPM system. When those processes involve paperwork, list_documents retrieves a list of everything stored in the Fluig Electronic Content Management (ECM), keeping your paper trail tight.
Querying Core Systems (RM & Protheus)
For deeper dives, this server gives you targeted query capabilities. You can run get_available_services to list every data server available within the RM environment so you know exactly what systems are connected and ready for action. If you need a specific piece of record-level data that doesn't fit into HR or Finance, get_rm_data lets you run a targeted query against any specific record type from an RM DataServer, pulling out whatever bits you need.
These tools make sure your agent can talk to every corner of the TOTVS stack.
How TOTVS MCP Works
- 1 First, subscribe to the TOTVS server. Then, log into your organization's dedicated TOTVS Portal.
- 2 Next, you need credentials: get a Username, Password, and Base URL from your ERP (Protheus/RM) or Fluig instance settings. You might also need a Tenant ID.
- 3 Finally, connect those details to Vurb so your AI client can start managing the enterprise data.
The bottom line is: you use these credentials once to give your agent access to multiple core business systems that normally require separate logins.
Who Is TOTVS MCP For?
This server is for people who deal with data across multiple departments and platforms. It's the HR Business Partner tired of jumping between the employee database and the leave management portal. It’s the Finance Analyst who needs to check both pending payments (Protheus) and document receipts (Fluig). And it's the Process Analyst who has to manually track a request from start to finish across different systems.
Uses list_employees or get_employee_details to pull staff records and monitor trends without logging into multiple HR portals.
Runs checks on both accounts payable (list_payments) and accounts receivable (list_receipts) to get a full picture of monthly cash flow.
Uses list_processes or move_process_request to track, advance, and audit the lifecycle of business requests in Fluig.
What Changes When You Connect
- Check employee status with
list_employeesor get deep profiles usingget_employee_details. You don't have to switch between the HR system and the database just to verify a single person’s role. - Get a full financial snapshot by running both
list_payments(AP) andlist_receipts(AR). This lets your agent summarize cash flow across different business units in one go. - Stop chasing paperwork. Use
get_process_requestto check the status of any pending workflow, then usemove_process_requestwhen it's ready for review. - Consolidate data sources: You can query employee info (
list_employees) and then immediately check related financial records or documents stored in Fluig (list_documents). - Better context from the start. Use
list_companiesto narrow down your searches, ensuring that all reports—whether HR or Finance—are tied to the correct branch.
Real-World Use Cases
Employee Onboarding Check
A new employee is starting. Instead of logging into three separate systems (HR, Payroll, Document Management), your agent runs list_employees to confirm the record exists. It then uses get_employee_details to pull their manager's ID and checks for any associated documents using list_documents. The person gets a single status report confirming readiness across departments.
Dispute Payment Status
A vendor calls asking about an overdue bill. Instead of calling the finance department, your agent runs list_payments to see pending invoices and then uses get_rm_data if needed to verify a specific contract ID, providing an immediate answer.
Tracking Approvals
A travel reimbursement request is stuck. The agent first runs list_processes to see all open workflows, identifies the correct process number, then uses get_process_request to check who it’s waiting on. Finally, if approved, it advances the status with move_process_request.
Branch Directory Lookup
You need payroll data for a branch you rarely deal with. Instead of guessing the system ID, your agent first runs list_companies to get all active branches and selects the correct one before running any other HR or Finance tools.
The Tradeoffs
Manual Data Sourcing
The user downloads a PDF report from Fluig, copies three names, then opens Protheus to check their employee ID, and finally logs into the Finance system for payments. This takes 15 minutes of manual clicks and copy-pasting.
→
Let your agent run list_employees first. Then, if you need a payment status, it runs list_payments. The AI handles the transitions between systems, giving you the unified answer in seconds.
Guessing Tool Parameters
The user tries to run an HR query but doesn't know if they need the company ID or the employee name. They get a vague error message about missing parameters.
→
Always start by running list_companies to confirm your organizational context. Then, use that confirmed ID in conjunction with tools like get_employee_details for accurate data retrieval.
Ignoring Workflow State
A request is sitting on a desk and the user just tries to 'update' it without knowing where it went wrong. The update fails because the process isn't ready.
→
Always run get_process_request first. It shows the current state, allowing you to accurately use move_process_request only when the request is properly positioned for advancement.
When It Fits, When It Doesn't
Use this TOTVS MCP Server if your core business need involves data that lives across multiple silos: HR (employee records), Finance (payments/receipts), and BPM (workflows). You're dealing with a complex, multi-system problem. Don't use it if you only need to check one thing—like listing all employees in isolation; for that, list_employees is enough. But if you need the employee count and their department budget status, this server connects those dots. It's built for deep orchestration across Protheus, RM, and Fluig.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by TOTVS. 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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 11 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Checking an Employee's Status Should Not Require Five Different Tabs
Today, finding a single employee profile requires jumping through hoops. You start in the HR system to get the name, then copy that name into the database interface to check their ID. Then you might open a separate document management portal just to see if they have current contracts attached. It’s fragmented, slow, and prone to human error.
With this MCP server, your agent handles it all. You ask for an employee profile, and the system runs `get_employee_details`, pulling data from HR, verifying associated documents with `list_documents`, and giving you one cohesive answer without you ever leaving the chat window.
TOTVS MCP Server: Control Workflow Requests
Manually tracking a process request involves checking status in Fluig, then figuring out who needs to approve it, and then logging into the workflow system again just to click 'Advance.' This cycle of viewing status and manually progressing it is tedious.
Now, you tell your agent the goal: 'Advance this request.' The agent uses `get_process_request` to confirm its details and then executes `move_process_request`. You get confirmation that the state changed—it's done.
Common Questions About TOTVS MCP
How do I find employee data using get_employee_details? +
You need to provide a unique identifier, like an ID or name, for the specific employee. The tool pulls detailed records from the HR module after you pass the necessary identifying parameters.
Can list_payments help me check overdue bills? +
Yes, list_payments checks accounts payable. It provides a summary of pending payments and lets you identify which invoices are past their due date for immediate action.
What is the difference between list_processes and get_process_request? +
list_processes gives you an index—it shows all available types of workflows. get_process_request, however, looks at a specific instance (a single request) to show its current status and history.
How do I list accounts receivable? +
Use the list_receipts tool. This checks your accounts receivable ledger, letting you see which money has been collected or is expected soon.
What does running `get_available_services` show my AI client about my TOTVS environment? +
It lists every active RM DataServer. This lets your agent confirm which databases are connected and ready for querying, preventing connection errors before you run any reports.
If I need to manually advance a workflow step in Fluig, how does `move_process_request` work? +
You must provide the specific request ID and the target state. The tool executes that transition immediately, moving the process forward inside Fluig's system.
Can I use `get_rm_data` to pull a single record with highly specific criteria from Protheus? +
Yes. You input the necessary table name and key parameters. This bypasses general listing tools, letting your agent grab exactly one record you need directly.
Before querying employee records, should I run `list_companies` to confirm the correct business unit? +
Running this first confirms all active branches and legal entities in Protheus. It ensures your agent targets the right company scope before pulling HR or financial data.
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.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
SEON
Prevent online fraud with device fingerprinting, email and phone analysis, and real-time risk scoring for digital transactions.
Mercado Livre Interactions
Answer buyer questions, check reputation, and view metrics on Mercado Livre.
Pylon
Automate B2B support and CRM via Pylon — manage issues, accounts, and knowledge bases with AI.
You might also like
Freshteam
Manage HR operations, track job applicants, and oversee employee records via AI agents with Freshteam.
Agora
Orchestrate Agora real-time engagement — manage channels, monitor usage, and handle cloud recording directly from any AI agent.
ALESP (Assembleia SP)
Access open data from the Legislative Assembly of São Paulo, including deputy info, expenses, and legislative proposals.