Blipen MCP

Connect an AI assistant to your authorized Blipen records. Explore financial data, compare income and expenses, and prepare manual accounts, cards and transactions for your approval.

Manual records do not move money. Every proposed record must be reviewed and confirmed in Blipen before it is saved. The connector cannot execute payments, bank transfers, trades, bank connections or deletions.

Before connecting

You need an active Blipen account and an assistant that supports remote MCP over Streamable HTTP and OAuth with dynamic client registration. Available data depends on your Blipen plan, granted permissions and accessible profiles. Features and publishing eligibility also vary by assistant.

Connection setup

1. In Blipen, open Settings → Integrations → AI assistants and select your assistant.
2. Use an approved Blipen directory listing when available. If Blipen shows guided setup, add a custom remote MCP connector in your assistant with the name Blipen and URL https://api.blipen.com/api/mcp.
3. Select OAuth and automatic client registration (DCR). In Claude, use Register automatically. Do not enter fixed API keys, client secrets, your Blipen PIN or session tokens into the assistant.
4. Sign in to Blipen and review the permissions requested by that assistant. Consent covers accessible current and future profiles within those permissions. Each request rechecks access on the server.
5. Finish the return to your assistant and enable Blipen in the conversation.

Guide entry points: Claude, Grok, and Manus. These are setup pages, not public Blipen installation links. Directory publication is separate from a successful custom connection. Gemini setup remains pending in this rollout.

Try Blipen

• “List the Blipen profiles I can access.”
• “Summarize income, expenses and net result for this month in my personal profile. State the dates and currency.”
• “Compare income and expenses in my personal profile for the last two months.”

Prepare and confirm manual records

1. Ask the assistant to prepare a record and supply any missing fields. For a test, use only synthetic data: a BRL checking account with a unique synthetic institution and zero opening balance; a card with a BRL 100 limit, closing day 3 and due day 10; a BRL 1 expense linked to the test account.
2. The assistant returns a pending operation and a Blipen review URL. The record is not saved yet.
3. Open the review URL, check the profile and every field, then confirm or decline in Blipen.
4. Ask the assistant to check the operation status and read back the record. Only a committed operation or a saved record confirms success. Check for duplicates before retrying.

Data, permissions and disconnection

The assistant receives the data returned by the tools you authorize. Depending on granted scopes, this can include financial records, planning, investments, identity/contact information, shared companies, taxes, preferences, notifications, conversations, support and company documents. Authorize only the permissions you need. External investment quote tools may contact market-data providers.

Reduce permissions or disconnect a specific assistant in Blipen’s AI assistants panel. Disconnecting stops that connection’s access; it does not delete copies already received by the assistant. The assistant’s own retention and privacy settings also apply. Existing connections are independent.

Troubleshooting

• If setup fails, confirm the exact HTTPS URL, OAuth/DCR, account access and requested permissions.
• If data is missing, check the selected profile, date range, currency, plan and permissions. Empty data is different from a request error.
• If a record is missing, inspect its pending operation and confirm in Blipen. An expired or declined operation does not save a record.
• A duplicate institution can prevent another checking account. Review existing records and choose a distinct synthetic institution for tests.
• Never send passwords, PINs, email codes or tokens to support.

Directory reviewers

Use a dedicated populated synthetic account, separate from any customer account. Reviewer access must be provisioned for an agreed reviewer email before testing. Open review sign-in in a separate browser profile, request an email code and enter it directly in Blipen within ten minutes. No bank or payment is required for the synthetic dataset. Contact contato@blipen.com for provisioning and review coordination. Each provider’s account and consent must be authorized separately.

Watch the synthetic ChatGPT demonstration. This demonstrates the same Blipen backend; it is not a recording from Claude, Manus or Grok and does not certify every tool on those platforms.