MCP.AI connector for Dock (unofficial)

● Active

io.github.mcp-dir/dock-mcp

Unofficial, not affiliated with Dock. Read-only Open Finance MCP by MCP.AI.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "dock-mcp": {
      "url": "https://api.mcp.ai/p_dock"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http dock-mcp https://api.mcp.ai/p_dock
VS Code
code --add-mcp '{"name":"dock-mcp","type":"http","url":"https://api.mcp.ai/p_dock"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
APIs & Integrations
Version
0.1.1
Registry
active
Published
11/20/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: MCP.AI connector for Dock (unofficial) is maintained, open source, hosted endpoint answering without a key.

Maintained
Active
Last commit today (Nov 20, 2026), 0 open issues.
Official registry
Active
Published as io.github.mcp-dir/dock-mcp in the official MCP registry, version 0.1.1.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
Hosted by the publisher
Your client talks to api.mcp.ai: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 08:07 UTCStatus history & uptime →
● Working233 msprotocol 2025-06-18v0.9.483tools

The endpoint answered the MCP handshake as "mcp-ai" and listed 25 tools. Answering since Nov 21, 2026.

Context cost ≈ 10k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 25 tools.

Tools (25)

  • openfinance_search_bank_connectors2 params

    Searches the available bank connectors by name (pass keywords[], e.g. ['nubank','btg']) and returns, per match: the connector id, whether it's Open Finance or API (`access`), PF/PJ (`audience`), the user's already-linked connections (and accounts when include_accounts=true), and a ready `connect_url` with the bank pre-selected. Some non-Open-Finance credential connectors carry a `caveat` warning that they don't auto-update (needs periodic manual reconnection) — surface it so the user can prefer the institution's Open Finance connector for automation. Honors the user's plan (a PF plan hides PJ banks; a PJ plan covers BOTH — PF and PJ banks connect and count under the same plan). Call this BEFORE connecting to hand the user a one-click link to the right bank. keywords[] is REQUIRED — without it returns a hint (never dumps the whole catalog).

    Show parameters
    • keywordsarray
    • include_accountsboolean
  • openfinance_list_connections

    Returns the saved bank connections for this install: connector_id, item_id, bank name, a per-connection reconnect_url, and an add_connection_url to link additional banks via the Open Finance widget. The reconnect_url reopens the widget in UPDATE mode for that EXISTING connection (user re-enters credentials / MFA token and the data refreshes in place) — use it when a connection needs re-authentication (MFA connectors, LOGIN_ERROR, stale non-Open-Finance data). It does NOT consume a connection slot and does NOT require disconnecting first.

  • openfinance_get_item_status3 params

    Returns the current status of a bank connection (UPDATED, UPDATING, LOGIN_ERROR, etc.), its executionStatus, connector metadata, and a reconnect_url that reopens the widget in UPDATE mode for that connection (re-authenticate / enter MFA token in place, without disconnecting and without consuming a connection slot). Omit `item` to get the status of ALL linked banks at once (returns `{ count, items }`); pass `item` for a single bank. Bulk support: accepts item_ids for batched execution.

    Show parameters
    • itemstring
    • item_idstring
    • item_idsarray
  • openfinance_provider_status

    Checks the LIVE operational status of the Open Finance provider (its public status page) — this is the PROVIDER's health, separate from your own connection's `openfinance_get_item_status`. Use it whenever data looks incomplete or stale even though a connection shows UPDATED (accounts/transactions/balances missing, a bank not returning everything): it reveals an upstream outage or a known incident on a specific bank/connector, so you can tell a provider-side problem apart from a connection that just needs reconnecting. Returns the global indicator (none/minor/major/critical), degraded components, open incidents, and — when you have banks connected — flags the incidents that affect YOUR connected banks in `your_banks_affected`.

  • openfinance_list_accounts4 params

    Returns accounts for a bank connection: BANK (checking/savings) and CREDIT (credit card) with balance, number, type, subtype, bankData, and creditData. Also returns `bank` (the brand/connector name like 'Nubank Empresas' — same shown in the dashboard UI) and `connector_id`. Note: each account's `name` is the legal entity that issues the account (e.g. 'Nu Pagamentos S.A. - Instituição de Pagamento'), which is not the same as the brand — when referring to the bank in user-facing text, use `bank`. OMIT `item` to list accounts across ALL linked banks at once — the response aggregates every connection's accounts into `results`, each row tagged with its own `bank`/`connector_id`/`item_id` (use this when the user asks for 'my accounts/cards' without naming a bank). Pass `item` to target a single bank (response carries `bank`/`connector_id`/`item_id` at the root). CREDIT (credit card) `balance`: its meaning is CONNECTOR-DEPENDENT — some banks report the current open-bill partial, others the full revolving/installment debt — so do NOT treat `balance` as 'this month's bill'. The open billing cycle is defined by `creditData.balanceCloseDate` (when it closes) / `balanceDueDate` (when it's due). For a standardized open-bill amount and total debt that mean the same across connectors, use openfinance_list_credit_card_bills (`open_bill` + `total_pending_debt`, derived from PENDING transactions); closed bills come from that same tool's `results`. A CREDIT row may carry `creditData.usedAmount` (how much of THIS card's limit the bank reports as consumed) and a `balance_notice`. `balance_notice` means `balance` came back 0,00 while the bank's own payload indicates an outstanding amount — some issuers never fill the card's consolidated balance field. When it is present, do NOT tell the user the card has nothing to pay: read the amount from openfinance_list_credit_card_bills instead. `bankData.closingBalance` and `automaticallyInvestedBalance` are provider-reported extras that can LAG ri

    Show parameters
    • itemstring
    • item_idstring
    • typestring
    • item_idsarray
  • openfinance_list_transactions8 params

    Returns transactions for a bank account (BANK or CREDIT type). For CREDIT (credit card) accounts, this is the ONLY way to get itemized transactions (purchases, subscriptions, etc.). Each credit card transaction MAY carry `creditCardMetadata.billId` pointing at a bill from openfinance_list_credit_card_bills, but this is a per-connector HINT, not authoritative: some connectors (e.g. Nubank) populate it sparsely (many transactions and installments arrive with no billId) or inconsistently (the same payment tagged to more than one bill). Do NOT reconstruct a bill's total by summing transactions by billId — the bill's own `totalAmount` from openfinance_list_credit_card_bills is the source of truth. CREDIT PENDING vs POSTED varies by connector: where the bank exposes future-dated `status:'PENDING'` installments, those represent the OPEN bill plus future bills (future months); where it does NOT, only the last closed bill's POSTED items appear until ~closing. Same query, different coverage per bank (upstream). To get a standardized open-bill total / total debt regardless, use openfinance_list_credit_card_bills (`open_bill` / `total_pending_debt`). SCHEDULED (future-dated) ROWS: results are ordered by date DESCENDING, and on a card with long installment plans the TOP of the list is the FUTURE — rows dated months ahead are scheduled installments of purchases already made, not new purchases. Every such row is flagged `scheduled:true`, the response carries `scheduled_count` and a `notice` naming the most recent row that actually happened. NEVER read the first row as 'the latest purchase' without checking `scheduled`. To list only what already happened, pass `to` = today. Supports from/to date filters (ISO YYYY-MM-DD) and an optional keyword filter via `search_queries` (case- and accent-insensitive substring match against description and merchant name, OR semantics across multiple terms). When `search_queries` is set the tool aggregates up to 5000 transactions within from/to befo

    Show parameters
    • account_idstringrequired
    • fromstring
    • tostring
    • pagenumber
    • page_sizenumber
    • search_queriesarray
    • detailstring
    • account_idsarray
  • openfinance_list_transactions_by_item9 params

    Consolidated cash-flow analysis for a whole bank CONNECTION over a period, in ONE call. Resolves the connection's accounts internally and fans out their transactions, so you do NOT need to call openfinance_list_accounts first nor carry account_id uuids between calls. Pass `item` (connector_id, connector_name or item_id) to target one bank, or OMIT it to analyze ALL linked banks at once. `from`/`to` are ISO dates (YYYY-MM-DD). Default `granularity:'monthly'` returns a COMPACT summary (no raw rows): total entradas, saídas, saldo_liquido, monthly evolution (`por_mes`), and `top_despesas`/`top_recebimentos` (largest N each), plus a per-account breakdown (`by_account`). Use this for 'análise anual/mensal', 'fluxo de caixa', 'entradas e saídas', 'maiores gastos/recebimentos'. Set `granularity:'raw'` to ALSO get every consolidated transaction (heavier — only when itemized rows are needed); combine with `detail:'rich'` to enrich those rows with merchantInfo (cnpj/cnae/businessName/category) + extra creditCardMetadata (billId, purchaseDate, fees), or `detail:'raw'` for the full untouched Pluggy object per row, when the connector provides them. `type` filters BANK or CREDIT accounts. On a connection with many transactions the scan caps at 5000/account and flags `truncated:true`. May include a `provider_incident` block when the Open Finance provider has an OPEN incident affecting a connected bank: the totals/rows may be incomplete or wrong until the provider recovers, and reconnecting does not fix it. Bulk support: accepts item_ids for batched execution.

    Show parameters
    • itemstring
    • item_idstring
    • fromstring
    • tostring
    • typestring
    • granularitystring
    • top_nnumber
    • detailstring
    • item_idsarray
  • openfinance_list_credit_card_bills5 params

    Returns CLOSED credit card bills for a CREDIT-type account: dueDate, totalAmount, minimumPaymentAmount, allowsInstallments, plus `payments[]` (id, paymentDate, amount, valueType, paymentMode), `payments_count`, `payments_total`, finance charges aggregates, and a derived `payment_status` per bill. IMPORTANT — Brazilian Open Finance semantics: Pluggy does NOT return a `paid`/`status` field. The payment goes into the `payments[]` of the bill whose CYCLE contains the paymentDate (closing ≈ dueDate − 7d): pre-payment before close stays on the bill being paid; payment between close and due, or after due, lands on the NEXT bill. So `payments[]` on a bill commonly carries the previous bill's payment, NOT the current one's — do NOT assume this bill was paid just because `payments[]` is non-empty. Use the derived `payment_status` (`PAID` | `OPEN` | `PAST_DUE_UNCONFIRMED` | `PAST_DUE_UNPAID`): a bill is `PAID` when its OWN `payments[]` (early pre-payment) or ANY newer bill in the payload contains a payment with amount ≈ this bill's `totalAmount` (±R$0.50). The MOST RECENT bill that's past-due, with no own pre-payment match, cannot be confirmed via cross-bill (the next cycle hasn't closed yet) — it returns `PAST_DUE_UNCONFIRMED`. NEVER call such a bill 'vencida' categorically; flag that the payment may have been made between close and due and not yet reflected upstream. The full `payment_status_legend` is returned alongside the results. OPEN BILL & TOTAL DEBT (standardized, derived — OPT-IN): pass `include_open_bill:true` to ALSO get `open_bill` (the current not-yet-closed bill, próxima a vencer) and `total_pending_debt` (saldo devedor total = all pending installments), BOTH derived from PENDING transactions so they mean the same thing across connectors — use these instead of the CREDIT account's `balance`, whose meaning VARIES by connector (some report the open-bill partial, others the full installment debt). `open_bill` = { available, method (`cycle_dates` = real close/due da

    Show parameters
    • account_idstringrequired
    • pagenumber
    • page_sizenumber
    • include_open_billboolean
    • account_idsarray
  • openfinance_list_investments6 params

    Returns the investment portfolio for a connection (broker or bank with INVESTMENTS product enabled): FIIs, stocks, ETFs, fixed income (CDB/LCI/LCA/Tesouro), mutual funds, retirement (previdência) and COE. Each row carries balance, amount, amountOriginal, amountProfit, lastMonthRate / annualRate / lastTwelveMonthsRate (when available), dueDate, issuer, ISIN, etc. When INVESTMENTS isn't enabled (403) returns `available:false` + `reason` + `warning` (no `results`: it does not mean the portfolio is empty). Temporary provider failures fail with an error saying when to retry; with several connections, the ones that failed are listed in `errors` and the response is flagged `complete:false`. DATA INTEGRITY: when MULTIPLE positions come back as TOTAL_WITHDRAWAL with balance/quantity 0 at once (mass zeroing), the tool cross-checks each position's own transaction history upstream; if the zeroing is contradicted (BUY with no sale/redemption/transfer) the response carries `data_integrity_warning` and the affected rows are flagged `integrity:'suspect_zeroed'` — treat those balances as UNAVAILABLE (likely a temporary connector failure publishing zeros), never as real R$0, and do NOT sum them into the portfolio. Bulk support: accepts item_ids for batched execution.

    Show parameters
    • itemstring
    • item_idstring
    • typestring
    • pagenumber
    • page_sizenumber
    • item_idsarray
  • openfinance_list_investment_transactions4 params

    Returns the movement history for a specific investment position: BUY / SELL / TAX / INTEREST / AMORTIZATION / TRANSFER. Each row carries quantity, value, amount, netAmount, agreedRate (treasury), brokerageNumber, and itemized `expenses` (brokerageFee, incomeTax, settlementFee, custodyFee, stockExchangeFee, etc.). Use after openfinance_list_investments to get the investment_id. Bulk support: accepts investment_ids for batched execution.

    Show parameters
    • investment_idstringrequired
    • pagenumber
    • page_sizenumber
    • investment_idsarray
  • openfinance_list_loans1 param

    Lists loan contracts per bank connection (GET /loans). Pass `items` as an array of connection selectors (item_id uuid, connector_id, or connector_name) — one entry per connection to fetch; multiple connections are queried sequentially with rate-limit spacing. OMIT `items` to list loans across ALL linked banks. Returns `{ results, errors }` per connection.

    Show parameters
    • itemsarray
  • openfinance_get_loan_detail1 param

    Returns full loan contract detail by id (GET /loans/:loanId): interestRates[] (taxType, ratePercentage, indexer), contractedFinanceCharges[], balloonPayments[], warranties[], installments schedule (installmentsCount, paidInstallments, numberOfInstallmentsRemaining, installmentFrequency), amortizationScheduled, CET, ipocCode and dates. Use after openfinance_list_loans to deep-dive on a specific contract. Pass `loan_ids` as an array (1-50). `{ results, errors }` batch shape.

    Show parameters
    • loan_idsarrayrequired
  • openfinance_force_sync2 params

    Forces the bank to re-sync one or more connections NOW and WAITS for it to finish (PATCH /items/:id, then polls until the item stops updating, up to ~60s). Use this when a balance or transaction list looks stale: a connection can read UPDATED yet be hours old, and this pulls fresh data WITHOUT disconnecting/reconnecting. Pass `items` as an array of selectors (item_id, connector_id, connector_name, or the user-set custom_label nickname); OMIT `items` to sync ALL linked banks. Returns `{ results, errors }`; each result has the final `status`, `executionStatus`, `lastUpdatedAt` (advances when data is refreshed), and `synced` (true = fresh data is ready). `needs_action` (e.g. MFA_REINTERACTION / LOGIN_ERROR / WAITING_USER_INPUT) means the user must re-authenticate — those results include a `reconnect_url` that opens the widget in UPDATE mode for that exact connection (user enters credentials / MFA token, data refreshes in place, no slot consumed, no disconnect needed). `timed_out: true` means the sync is still running — re-check with openfinance_get_item_status. Set `wait: false` for fire-and-forget (returns immediately while UPDATING).

    Show parameters
    • itemsarray
    • waitboolean
  • openfinance_get_account_balance1 param

    Returns the latest available balance per account id (GET /accounts/:id/balance). This is the freshest balance the provider can serve, but it is a SNAPSHOT anchored to the connection's last upstream sync: the `updateDateTime`/`updatedAt` in each row is that sync instant, NOT a to-the-second live read. If a movement that just happened is not reflected yet, or the balance disagrees with the sum of openfinance_list_transactions, run openfinance_force_sync to pull fresh data and then re-read. Pass `account_ids` as an array (1–50). CREDIT accounts may return Pluggy BALANCE_FETCH_ERROR (provider could not fetch it) or BALANCE_CONSENT_ERROR (the institution refused it because the consent lacks the balance permission — reconnecting the bank restores it) — those rows include a structured `warning` instead of throwing. When the financial institution is temporarily unavailable upstream (5xx) or the connector is not Open Finance, the row DEGRADES to the last-synced balance with `realtime: false`, `updatedAt` and a `warning` instead of an error. Response shape: `{ results: [...], errors: [{ id, status, message }] }`.

    Show parameters
    • account_idsarrayrequired
  • openfinance_get_accounts_detail1 param

    Returns full account objects including extended creditData (additional cards, limits) per id (GET /accounts/:id). Pass `account_ids` as an array (1–50). `{ results, errors }` batch shape. May include a `provider_incident` block when the Open Finance provider has an OPEN incident affecting a connected bank: credit limits and balances may be unreliable (e.g. a limit near 1,00) until the provider recovers. Do not present those values as real.

    Show parameters
    • account_idsarrayrequired
  • openfinance_get_credit_card_bill4 params

    Returns bill-level detail for one or more credit card bills by id (GET /bills/:id): `dueDate`, `billClosingDate` (when the cycle closed — the boundary that defines which purchases belong to this bill), `totalAmount`, financeCharges and payments[] (id, paymentDate, amount, valueType, paymentMode). ITEMIZED PURCHASES (OPT-IN): the bank's bill payload has no transactions in it — they live on the card ACCOUNT. Pass `include_transactions:true` (plus `account_id` of the credit card, since the bill itself carries no account reference) and each row also gets `transactions[]`, `transactions_count`, `transactions_sum` and `reconciles_with_total`, already matched to that bill. Always check `transactions_basis`: `bill_id` = exact (the bank tagged each transaction with this bill — the normal case for CLOSED bills), `date_window` = ESTIMATE (`confidence:'low'`, window echoed in `transactions_window`) used when the connector tags no billId or the bill is still open (PENDING lines get no billId until the cycle closes), `unavailable` = no link possible. Opt-in because it costs an extra full transaction scan of the account. Whatever the basis, the bill's own `totalAmount` is authoritative — do NOT rebuild it by summing transactions. Without the opt-in the response carries a `transactions_hint`; you can also fetch them yourself via openfinance_list_transactions with the credit card account_id and a from/to range ending at `billClosingDate`. Pass `bill_ids` as an array — use openfinance_list_credit_card_bills first to discover ids. `{ results, errors }` batch shape. NOTE: Pluggy does NOT return a paid/status field. In Brazilian Open Finance, `payments[]` reflects payments registered during THIS bill's billing cycle — typically the payment of the PREVIOUS bill (do NOT assume this bill was paid just because `payments[]` is non-empty). To check paid status, prefer `openfinance_list_credit_card_bills` which derives `payment_status` via cross-bill match.

    Show parameters
    • bill_idsarrayrequired
    • include_transactionsboolean
    • account_idstring
    • transactions_detailstring
  • openfinance_list_categories

    Returns Pluggy's transaction category taxonomy (GET /categories), cached for the adapter session. Each entry has `id` (the categoryId used by openfinance_update_transaction_category), `description` (English), `descriptionTranslated` (Portuguese — prefer this for pt-BR users), `parentId` and `parentDescription` (the tree parent). Single aggregated response — no batch ids.

  • openfinance_update_transaction_category1 param

    Corrects the category of one or more transactions (PATCH /transactions/:id). Pass `items` as an array of { transaction_id, category_id } — `transaction_id` comes from openfinance_list_transactions, `category_id` from openfinance_list_categories. This overrides Pluggy's automatic categorization AND teaches Pluggy: recategorizing a transaction automatically creates a Category Rule for this client (case-insensitive exact match on the transaction's data), so FUTURE similar transactions are categorized the same way — use this to fix miscategorized transactions and improve categorization accuracy going forward. Batch shape: returns `{ updated, results: [{ transaction_id, category, categoryId }], errors: [{ id, status, message }] }` — per-item errors do not fail the whole batch.

    Show parameters
    • itemsarrayrequired
  • openfinance_disconnect_bank1 param

    Revokes the Open Finance consent for a specific bank and deletes the connection data. The bank's data will no longer be available. Returns an add_connection_url to re-connect if needed.

    Show parameters
    • itemstringrequired
  • show_version

    Show the current MCP platform and adapter versions.

  • report_bug3 params

    Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

    Show parameters
    • messagestringrequired
    • contextstring
    • conversationstring
  • connect

    Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

  • toolkit_info

    Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

  • marketplace23 params

    The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

    Show parameters
    • actionstring
    • querystring
    • mcp_idstring
    • limitnumber
    • tier_slugstring
    • immediateboolean
    • cancel_reasonstring
    • cancel_commentstring
    • messagestring
    • report_contextstring
    • conversationstring
    • request_namestring
    • request_detailsstring
    • tool_idstring
    • argumentsstring
    • prompt_slugstring
    • prompt_varsstring
    • prompt_categorystring
    • prompt_toolstring
    • prompt_titlestring
    • prompt_descriptionstring
    • prompt_bodystring
    • prompt_targetsarray
  • authenticate1 param

    MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

    Show parameters
    • tokenstring

Checked by Serverdex with a plain initialize + tools/list call to api.mcp.ai/p_dock, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 21, 2026
Stars
0
Forks
0
Last push
Nov 20, 2026
License
MIT

From the README

Conector MCP.AI para Dock Use seus dados do Dock no Claude, ChatGPT e agentes de IA via Open Finance ⚠️ A MCP.AI não é afiliada, patrocinada nem endossada pelo Dock. Dock é marca registrada de seu titular e é citada apenas para indicar com qual instituição este conector funciona. O acesso aos dados acontece pelo Open Finance Brasil, regulado pelo Banco Central, com autorização do próprio cliente. Conecte sua conta do Dock ao Claude, ChatGPT e agentes de IA via Open Finance Brasil. Pergunte sobre saldos, extratos, faturas de cartão e investimentos do Dock em linguagem natural. Regulado pelo Banco Central, somente leitura. • 🏦 Dock via Open Finance Brasil, regulado pelo Banco Central • 💳 Saldos, extratos, faturas de cartão, investimentos e empréstimos • 🔒 Somente leitura — a IA não movimenta dinheiro • 🔑 Login por magic-link, consentimento explícito e revogável (LGPD) • 💬 Funciona com qualquer cliente MCP: Claude Desktop, Cursor, VS Code, Cline, Continue English version · Documentação completa · Skill pra agentes Instalar em 1 clique Claude (Web e Desktop) A Anthropic unificou a instalação de MCPs em claude.ai/customize/connectors.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://api.mcp.ai/p_dock

The most-starred APIs & Integrations servers in the index, with their live-check result.

ServerStarsLast pushLive check
OpenWork MCP Gateway24,576Nov 2026Needs sign-in
API Anything3,699Nov 2026Local / not checked
GoModel1,322Nov 2026Local / not checked
Scaleway MCP server1,027Nov 2026Local / not checked
AnythingMCP817Nov 2026Needs sign-in

MCP.AI connector for Dock (unofficial): questions people ask

Is MCP.AI connector for Dock (unofficial) a remote or a local MCP server?
According to its entry in the official MCP registry, MCP.AI connector for Dock (unofficial) ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does MCP.AI connector for Dock (unofficial) need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is MCP.AI connector for Dock (unofficial) safe to use?
Looks healthy: MCP.AI connector for Dock (unofficial) is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is MCP.AI connector for Dock (unofficial) still maintained?
Active: the repository's last commit today. Last push Nov 20, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 21, 2026.
What tools does MCP.AI connector for Dock (unofficial) expose?
25 tools as listed by the server itself during the live check, including openfinance_search_bank_connectors, openfinance_list_connections, openfinance_get_item_status, openfinance_provider_status, openfinance_list_accounts. The full list with parameters is in the Live check section above.
How do I add MCP.AI connector for Dock (unofficial) to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. Jus MCPBrazilian legal stack in one MCP: lawsuits, court publications, case law, tenders, certificates.★ 19
  2. Astrea (Aurum)Reporting and queries over Astrea (Aurum), Brazilian legal-practice software: cases per client, cale★ 11
  3. OmieFinancial & accounting management on Omie (Brazil's leading cloud ERP), payables/receivables, financ★ 8
  4. InstagramInstagram for AI agents: publish, read comments and DMs, insights, and engage from your account.★ 6
Browse all APIs & Integrations →

Add the badge to your site

Show visitors that MCP.AI connector for Dock (unofficial) is listed here — it’s also the link we check for a free listing.

MCP.AI connector for Dock (unofficial) — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-mcp-dir-dock-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="MCP.AI connector for Dock (unofficial) — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![MCP.AI connector for Dock (unofficial) — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-mcp-dir-dock-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-mcp-dir-dock-mcp) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-mcp-dir-dock-mcp) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-mcp-dir-dock-mcp)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-mcp-dir-dock-mcp"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-mcp-dir-dock-mcp"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-mcp-dir-dock-mcp"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).