← Todas as Integrações

Claude Desktop

Anthropic's desktop app has first-class MCP support. Connect locally via the CLI or point to the remote server.

Local (stdio) Remote (HTTP + OAuth)
  • A Bipa account with an active registration.
  • bipa CLI installed (for local mode). Prefer the managed installer: curl -fsSL https://agents.bipa.app/install.sh | sh. Developer package-manager installs are listed in the docs.
  • Run bipa login --web --open to authenticate before configuring Claude Desktop (local mode only). Use --web alone to get the URL without auto-opening the browser.

Configuração Local (stdio)

01

Open Claude Desktop settings

Click the Claude menu → SettingsDeveloperEdit Config. This opens the claude_desktop_config.json file.

02

Add the Bipa Agents MCP server

Add the following to your mcpServers configuration:

{
  "mcpServers": {
    "bipa": {
      "command": "bipa",
      "args": ["mcp", "serve", "--stdio"]
    }
  }
}
03

Restart Claude Desktop

Close and reopen Claude Desktop. You should see the MCP tools icon (hammer) in the chat input, confirming the connection.

If the bipa command is not found, ensure ~/.local/bin is in your PATH or use the full path to the binary.

Configuração Remota (HTTP + OAuth)

Conecte-se diretamente ao servidor MCP remoto do Bipa Agents. Nenhuma instalação local é necessária. A autenticação é feita via OAuth 2.1 com PKCE.

01

Open Claude Desktop settings

Click the Claude menu → SettingsDeveloperEdit Config.

02

Add the remote MCP server

Add the following to your mcpServers configuration:

{
  "mcpServers": {
    "bipa": {
      "url": "https://mcp.bipa.app/mcp"
    }
  }
}
03

Authenticate via OAuth

Restart Claude Desktop. When you first use a Bipa Agents tool, Claude will open your browser to complete the OAuth flow with Bipa. After authorization, the token is managed automatically.

The remote server uses OAuth 2.1 with PKCE. No API keys to manage.

Ferramentas MCP Disponíveis

Uma vez conectado, as seguintes ferramentas ficam disponíveis para o assistente de IA:

bipa_whoami

Current session info

bipa_account

Account profile

bipa_balance

Check all wallet balances

bipa_limits

Check spending limits

bipa_deposit

Get deposit addresses

bipa_pay

Send a PIX transfer (supports scheduling)

bipa_pix_pay_key

Pay via Pix key

bipa_pix_pay_brcode

Pay via BR Code

bipa_pix_pay_tag

Pay a Bipa user by tag

bipa_pix_pay_trusted_contact

Pay a trusted contact

bipa_pix_pay_recipient

Pay a saved recipient

bipa_pix_brcode_decode

Decode a Pix BR Code

bipa_pix_brcode_preview

Preview a BR Code payment before paying

bipa_pix_tag_preview

Look up a Bipa user by tag

bipa_pix_keys

List Pix keys

bipa_pix_trusted_contacts

List trusted contacts

bipa_pix_recipient_suggestions

Suggest recent recipients

bipa_history

Transaction history

bipa_transactions

Multi-asset transaction list

bipa_transaction_detail

Detail of a specific transaction

bipa_timeline

Unified activity timeline

bipa_tickers

Current BTC/USDT prices

bipa_btc_prices

BTC/BRL price history

bipa_usdt_prices

USDT/BRL price history

bipa_portfolio

Portfolio summary by asset and period

Modo local: O CLI autentica abrindo seu navegador. Você faz login pelo app Bipa e o token de sessão é armazenado localmente.

Modo remoto: O cliente MCP lida com o OAuth 2.1 automaticamente. Ele descobre os endpoints via /.well-known/oauth-authorization-server, redireciona você ao app Bipa para autorização e troca o código por um token de acesso usando PKCE.