Protheus MCP Server

TOTVS Protheus

TOTVS Protheus MCP, your ERP answering in plain language

Talk to your company's TOTVS Protheus ERP from Claude, ChatGPT or any MCP client. It runs on the official TOTVS REST API, against your own installation: you provide the REST service URL and your Protheus user and password, and nothing goes through an ERP middleman. Unlike the Protheus MCPs that already exist, which are developer tools (compiling AdvPL, searching the TDN), this one reads business data: branches, customers and vendors, products, stock, price lists, sales and orders, invoice totals, production orders and MRP purchasing. Read-only. Not affiliated with TOTVS.

• 🏢 Your Protheus, not a middleman — connects to your company's installation through the official TOTVS REST API
• 🔎 Finds out what YOUR installation answers — every Protheus publishes a different set of APIs, and the diagnostic maps it in one question
• 📦 Business data, not a dev tool — branches, customers and vendors, products, stock, price lists, sales, orders, invoice totals, production orders and MRP purchasing
• 🧩 Calls any REST route, including the custom endpoints your company built in Protheus
• 🔒 Read-only — v1 only queries, it never writes to the ERP
• 💬 Works with any MCP client: Claude Desktop, ChatGPT, Cursor, VS Code, Cline, Continue

Versão em português · Full docs (PT-BR) · Agent skill

---

One-click install

Claude (Web and Desktop)

Anthropic unified MCP installation at claude.ai/customize/connectors. The same link works for Claude Web and Claude Desktop (just be logged in):

➕ Open in Claude and connect

Manual (if the deeplink does not open): claude.ai/customize/connectors → + → Add custom connector → paste Name TOTVS Protheus and URL https://api.mcp.ai/p_protheus.

Cursor

➕ Install TOTVS Protheus in Cursor

VS Code (Copilot Chat)

➕ Install TOTVS Protheus in VS Code

ChatGPT, Manus, OpenClaw and 40+ other clients

Works with any MCP client that speaks MCP over HTTP. The server URL is always:

https://api.mcp.ai/p_protheus

Per-client details: INSTALL.md.

---

Example prompts

Which Protheus APIs does my installation answer?
List the group's branches with their company codes
What is today's stock balance by product?
Show price list 001 with its items
Which production orders are scheduled for this week?
What is customer X's credit limit?

---

26 tools available

Details for each tool: docs/ferramentas.md (PT-BR)

---

What you can ask

An honest note before you connect

Protheus is not a SaaS with a single address: every company runs its own installation. Two practical consequences:

1. The REST service has to be published. Your IT team enables REST in appserver.ini, allocates the threads (which consume licenses) and opens the port. Without that there is nothing to connect to, with any tool.
2. Each installation answers a subset of the APIs. TOTVS publishes 125 APIs for the Protheus line, but what yours answers depends on the LIB version, the licensed modules and your customizations. That is why the first question to ask is the diagnostic: it probes your installation and reports, API by API, what is available, what does not exist there, and what your user cannot see.

---

Pricing

Plans start at a free tier. See docs/precos.md (PT-BR).

---

Privacy & data protection

• Read-only, no tool changes data at the source.
• Sub-processors: TOTVS, the LLM host you choose (Claude, ChatGPT, Cursor, your own agent). Full list in docs/privacidade-lgpd.md.
• Data returned by the tools is sent to the LLM host you choose, a sub-processor outside our control. We recommend plans with training opt-out.

---

FAQ

Is this the official TOTVS MCP? No. This is an independent MCP that talks to your own company's official Protheus REST API using your credentials. It is not affiliated with TOTVS and implies no partnership. TOTVS and Protheus are trademarks of TOTVS S.A., referenced here nominatively.

What data do you access? Only what your Protheus user can already see, and only for reading. v1 issues GET requests exclusively: it creates no orders, settles no invoices, and writes nothing to the ERP.

Do I have to expose my Protheus to the internet? The REST service must be reachable by our platform. That is usually done by publishing the endpoint over HTTPS and restricting access by IP or VPN, together with your IT team. If REST is not up today, that is step one, and it applies to any integration, not just ours.

Why does one question work and another says the route does not exist? Because the API is shared but the deployment is yours. TOTVS publishes the contract for 125 Protheus-line APIs; your installation answers the ones your LIB version and licensed modules enable. When a route does not exist there, the answer says exactly that instead of pretending there are no records. Run the diagnostic to see the full map of your installation.

What about the endpoints my company built in Protheus? They work. There is a wildcard tool that calls any REST route on your installation, so your in-house custom MVC APIs are reachable without us shipping anything new.

Where do my password and ERP URL live? Encrypted, and used only to request the token from your own installation's oAuth2 API. The Protheus access token is transient (it expires in an hour) and is not stored.

My user has two-factor authentication. Does it work? Not yet. Use an integration user without a second factor, permissioned only for what you want to expose. That is the recommended practice anyway: access stays auditable and scoped inside Protheus itself.

Does it work for Datasul, RM or Logix? No. This MCP targets the Protheus line. The other TOTVS lines have their own APIs and would be a separate MCP.

---

Support

• 📧 protheus@mcp.ai
• 🐛 GitHub Issues
• 📄 docs/

---

License

MIT — see LICENSE. The MCP server at api.mcp.ai/p_protheus is proprietary (hosted); this repo (manifests, docs, skills) is MIT.