Servidor MCP do BTG Empresas
What it is
The BTG Empresas MCP server gives an AI application read and write access to your business account (PJ) data, authorized by the client themselves through the OAuth2 Authorization Code Flow. Natural-language questions such as "what is my balance?" or "which bank slips are due this week?" are answered with real account data, inside the application the client already uses. New to the protocol? See the MCP specification.
Every write operation has security locks designed to protect your account and your usage. See Security and best practices for more details.
What MCP is not
- Not an AI. The server has no model. It only exposes operations and executes them. The intelligence, understanding the request and choosing the action, lives in the AI assistant being used.
- It does not store your data or your session. Each request is independent and carries its own authentication token.
- It does not issue credentials. Authentication is delegated to BTG Id. The MCP server only reads the token that arrives.
REST API or MCP?
The MCP server does not add new capabilities to the BTG Empresas APIs. It exposes the same operations in a format that an AI assistant understands natively. If you already integrate with the BTG APIs over REST, MCP is conceptually identical: same credentials, same scopes, same registration process. What changes is who writes the call.
| Aspect | Direct REST API | MCP Server |
|---|---|---|
| Who uses it | A developer writing code | A user conversing with an AI assistant |
| Interface | HTTPS | Natural language |
| Typical use case | Automated systems, ERPs, etc. | Interactive queries and operations via assistant |
| Write operations | You control in code | Require explicit user confirmation |
Both models coexist. For automation and systems, use the REST API. For interactive operations with an AI assistant, use MCP.
Compatibility
Any client or assistant compatible with the MCP protocol can connect to the BTG Empresas MCP server.