MCP server
Machine translation, not yet reviewed.
Tax360 MCP server
Connect AI assistants to the Tax360 fiscal platform using the MCP protocol.
Preview
The MCP server is in preview. Tools and the access process may change before general availability. To join, contact support.
MCP (Model Context Protocol) is an open standard for connecting AI assistants to external systems. With the Tax360 MCP server, a compatible assistant can, for example, check the SEFAZ status of an NF-e, search received invoices, list SPED bookkeepings or follow a file's validation in RocketPVA, all from a natural-language question.
How it works
- Remote server: the assistant connects to an HTTPS URL (MCP Streamable HTTP transport). There is nothing to install.
- Your user, your permissions: the connection is authorized by signing in to Tax360 (OAuth 2.1). Every call runs with the identity, companies and permissions of the user who authorized it. The assistant sees nothing that user could not see in Tax360.
- Curated tools: the server exposes a curated set of tools. Most are read-only. The ones that create something (SPED upload and report generation in RocketPVA) require specific permissions.
- Lean responses: tools return summaries. Access keys, CPFs and e-mails are masked, and files (XML, DANFE, reports) come as temporary links.
What it covers
| Product | What the assistant can do |
|---|---|
| DF-e | NF-e status at SEFAZ, search of issued and received NF-e, NFC-e, NFS-e and CT-e, events and occurrences, XML and DANFE, SEFAZ status per state and last-24-hour metrics |
| Companies | List your user's companies and find documents by access key |
| RocketPVA | List SPED bookkeepings, upload files for validation, follow status and errors and generate the Excel report |
The full list, with example prompts, is in Tools.
Next steps
- Connect your client.
- Ask a first question, for example: "List my companies in Tax360".
- Read Security and limits before using it in production.