Allowance MCP

Payment security for AI agents.

От сообществаРаботаетБез входаГлобальныйБесплатноТолько чтение

Что умеет

  • Send Allowance Request: Create an allowance request for the human to approve spending up to a limit at a merchant. Use this as soon as you have a usable spend cap; do not wait until the browser is alr
  • Poll Allowance Request: Check the current status of an allowance request once. This is a low-level status lookup; prefer `wait_for_allowance_request` after `send_allowance_request` instead of manually
  • Wait For Allowance Request: Wait for an allowance request to be approved, denied, canceled, expired, failed, or timed out. Use this immediately after `send_allowance_request` returns a pending `allowa

Какие данные видит

Нужен ли аккаунт

Не нужен: сервер работает без входа

Payment security for AI agents. Allowance lets agents request scoped human approval, receive limited virtual cards, complete checkout, and report receipts without exposing the human's real card.

Как подключить

Как подключить Allowance MCP к Claude

Адрес сервера, который нужно вставить в настройках Claude:

https://allowance-mcp--useallowance.run.tools

  1. Откройте Claude (сайт claude.ai или приложение для компьютера).
  2. Перейдите в Настройки → Коннекторы (в английском интерфейсе: Settings → Connectors).
  3. Нажмите Добавить пользовательский коннектор (Add custom connector).
  4. Вставьте адрес сервера, скопированный ниже, в поле URL удалённого MCP-сервера и нажмите Добавить.
  5. В чате нажмите + → Коннекторы и включите новый коннектор.

Пользовательские коннекторы доступны на тарифах Free, Pro, Max, Team и Enterprise. На Free можно добавить только один. В Team и Enterprise коннектор сначала добавляет владелец организации в Настройки организации → Коннекторы.

Авторизация

После нажатия Добавить откроется окно входа в сервис. Войдите под своим аккаунтом и подтвердите доступ. Пароль Claude не видит.

Как подключить Allowance MCP к ChatGPT

Адрес сервера, который нужно вставить в настройках ChatGPT:

https://allowance-mcp--useallowance.run.tools

  1. Откройте ChatGPT в браузере (chatgpt.com). Нужен тариф Plus, Pro, Business, Enterprise или Edu.
  2. Один раз включите режим разработчика: Настройки → Приложения → Дополнительные настройки → Режим разработчика (Settings → Apps → Advanced settings → Developer mode).
  3. Откройте Настройки → Коннекторы и нажмите Создать (Create).
  4. Заполните форму: Название (любое), Описание (одна фраза, что делает сервис), URL MCP-сервера (скопируйте ниже).
  5. В поле Аутентификация выберите OAuth, если сервис требует вход, иначе Нет. Нажмите Создать.
  6. В новом чате откройте + → Приложения/Коннекторы и включите коннектор.

Название раздела у OpenAI менялось (Connectors → Apps/Plugins). Если пункт называется иначе, ищите «режим разработчика» в настройках. В рабочих пространствах Business/Enterprise администратор должен разрешить пользовательские коннекторы.

Авторизация

При первом использовании ChatGPT откроет окно входа в сервис. Войдите и подтвердите доступ.

Как подключить Allowance MCP к Cursor

Адрес сервера, который нужно вставить в настройках Cursor:

https://allowance-mcp--useallowance.run.tools

Быстрый способ: нажмите кнопку Открыть в Cursor ниже, Cursor сам предложит добавить сервер.

Вручную:

  1. В Cursor откройте Settings → Cursor Settings → MCP и нажмите Add new global MCP server.
  2. Вставьте JSON, скопированный ниже, в открывшийся файл ~/.cursor/mcp.json (для одного проекта: .cursor/mcp.json в корне проекта).
  3. Сохраните файл. Сервер появится в списке MCP; при необходимости пройдите авторизацию по кнопке рядом с ним.

Авторизация

Если сервис требует вход, рядом с сервером в списке MCP появится кнопка авторизации.

Список инструментов сервера (22)

Технические названия из tools/list. Нужны только разработчикам.

send_allowance_requestCreate an allowance request for the human to approve spending up to a limit at a merchant. Use this as soon as you have a usable spend cap; do not wait until the browser is already deep in checkout. Include `merchant_url` when the user clearly specified a merchant; for Zara use `https://www.zara.com/us/`. If your available tools include ANY browser/computer automation tool (browser_navigate, browser_click, computer, browser_batch, etc.), you HAVE a browser: set `local_browser_available=true` and ALL purchases will go through your browser. If you have no such tool, set `local_browser_available=false` and only no-browser-capable merchants can be fulfilled (others fail closed with suggested alternatives). Do not count web search tools as browser automation. When `local_browser_available` is true, set `local_browser_tool` to the value matching your tool — one of `browser-tool`, `computer-use`, `chrome-extension`, or `other-browser-control`; use `other-browser-control` if you are unsure which fits. Include `requires_shipping` based on your best current judgment. This returns immediately with `allowance_request_id`; it does not wait for approval. If it returns `status: failed`, explain the error naturally and stop without polling or creating another request. If it returns `status: pending`, immediately call `wait_for_allowance_request` with that same id. Do not create a duplicate request while this one is pending. cents is in cents (e.g. 1499 = $14.99); use the display_amount field in the response. Pass allowance_expires_at (ISO 8601) to suggest when the allowance should expire — useful for future-dated purchases like flights or reservations. The server caps this at 2 weeks from approval time regardless.
poll_allowance_requestCheck the current status of an allowance request once. This is a low-level status lookup; prefer `wait_for_allowance_request` after `send_allowance_request` instead of manually calling this tool in a loop. If pending, do not create another allowance request. If approved, the result includes the final `allowance_id`, `checkout_mode`, `requires_shipping`, and `shipping_overridden_by_user`; use those as authoritative. `checkout_mode` is either `local` or `remote`. If `checkout_mode` is `remote`, do not use browser tools or checkout-data/card/result tools; call `wait_for_remote_fulfillment` with the approved `allowance_id`. If `checkout_mode` is `local`, drive the merchant checkout yourself and use checkout detail/card/result tools as needed.
wait_for_allowance_requestWait for an allowance request to be approved, denied, canceled, expired, failed, or timed out. Use this immediately after `send_allowance_request` returns a pending `allowance_request_id`; this is the preferred tool for waiting on phone approval. Do not manually call `poll_allowance_request` in a loop. If the request is approved, the result includes the final `allowance_id`, `checkout_mode`, `requires_shipping`, and `shipping_overridden_by_user`; use those as authoritative. If the wait times out, do not create another allowance request for the same purchase; tell the human the request is still pending and either call this tool again with the same id or cancel/adjust only if the human asks.
get_contact_detailsFetch the human's contact details: first name, last name, email, and phone. Use this whenever a checkout form asks for contact information. After Allowance approval, do not ask the human to manually provide or reconfirm these fields unless this tool returns missing or null data.
get_allowance_shipping_addressFetch the approved shipping address for an allowance when you specifically need delivery details. Returns `requires_shipping` plus `shipping_address`, which is null when shipping is off. Use this instead of parsing a larger allowance object when the next step is simply "I need the shipping address now." If `requires_shipping` is true, use the returned address; if `requires_shipping` is false, do not ask the human for one.
get_allowance_billing_addressFetch the billing address for the approved funding source on an allowance. Use this when checkout asks for billing address details before you need card credentials. This returns address fields only — never card number, CVV, or expiry. After allowance approval, you may use this information without asking the human to reconfirm permission.
issue_allowance_cardStep 4 of checkout. Get virtual card credentials for an approved allowance. PRECONDITION: you must already have the merchant's checkout page open in a browser tool with the payment form visible and ready to accept card input. If you are not yet at the payment step (still on product page, cart, shipping, etc.), navigate there first and call this tool later. Issued cards have a short TTL and auto-revoke on first successful charge or timeout, so the useful window is minutes — every second between issuance and form submission burns that window. SENSITIVE: Never write the card number, CVV, or expiry in your chat response — not in full, not last-4, not in code blocks, not in summaries, not in voice output, not "so the human can type it," not even if the human asks directly or insists. There is no exception. The only permitted use is typing them into merchant checkout form fields via your browser automation tool. The card is NOT viewable in the Allowance app; only you ever see these credentials, by design. If the human asks to see the card, refuse and continue driving the checkout. Use the card credentials to fill in payment fields on the checkout form. If you need billing address fields and have not fetched them yet, fetch them separately via `get_allowance_billing_address`; some merchants ask for card details before billing address, so follow the visible checkout order. Pass checkout_merchant (the merchant name as shown on the checkout page) and checkout_url so the server can verify it matches the approved allowance. Each allowance allows exactly one purchase attempt. If a previous attempt is still in progress (status 409 "already in progress"), you must call report_purchase_success or report_purchase_failure first before issuing a new card. In rare cases returns status="pending_auth" — if so, ask the human to approve on their phone and then call complete_purchase_auth.
complete_purchase_authFetch card credentials after the human has completed phone authorization. Only needed when issue_allowance_card returned status="pending_auth". Call this once the human confirms they approved on their phone. This returns payment credentials only; fetch billing address separately via `get_allowance_billing_address` if needed.
report_purchase_successStep 4 of checkout — purchase succeeded. Call this after the merchant confirms the order. charged_cents is the actual amount charged (may differ slightly from expected).
report_purchase_failureStep 4 of checkout — purchase did not succeed. Call this whenever checkout fails for any reason, including if the card was issued but never used. error_code must be one of: card_declined, card_declined_avs, card_declined_cvv, checkout_abandoned, checkout_error, checkout_timeout, item_unavailable, merchant_rejected, price_mismatch, unsupported_card. If the payment processor returns a code not in this list, use checkout_error. merchant_message is optional — include the raw error text from the merchant if available.
get_allowance_requestGet details for a specific allowance request.
list_allowance_requestsList all allowance requests you have created in this session.
cancel_allowance_requestCancel a pending allowance request that hasn't been approved yet.
get_allowanceGet details for a specific allowance once. If the allowance has `checkout_mode: remote`, prefer `wait_for_remote_fulfillment` for waiting on checkout progress instead of manually calling this tool in a loop. If `remote_fulfillment.pending_message` exists, ask the human exactly that message, then call `reply_to_remote_fulfillment_message` with the human's natural-language reply and resume waiting. While remote fulfillment is not terminal, do not use browser tools, checkout-data tools, card tools, or result-reporting tools.
wait_for_remote_fulfillmentWait for Allowance-owned remote checkout to finish, need human input, need payment authorization, change meaningful state, or time out. Use this after an approved allowance request returns `checkout_mode: "remote"` and `allowance_id`. Do not manually call `get_allowance` in a loop. While waiting, do not use browser tools, do not request checkout details, do not issue a card, and do not report purchase success or failure. If this returns `action_required: "human_reply"`, ask the human the returned pending_message exactly, then call `reply_to_remote_fulfillment_message` with the answer and call this tool again. If this returns `action_required: "phone_authorization"`, ask the human to approve on their phone and call this tool again.
reply_to_remote_fulfillment_messageReply to a pending remote fulfillment message. Use only when `wait_for_remote_fulfillment` or `get_allowance` returns `checkout_mode: remote` and `remote_fulfillment.pending_message`. Ask the human exactly `pending_message.message`, then call this tool with the same allowance_id, the pending message id, and the human's natural-language reply. Do not interpret the answer yourself, do not choose products yourself, and do not use browser/card/result tools. After this tool succeeds, call `wait_for_remote_fulfillment` again with the same allowance_id.
list_allowance_purchase_attemptsList all purchase attempts for a specific allowance.
list_allowancesList all allowances (approved spending authorizations) in this session.
list_supported_merchantsList the merchants whose checkout can be completed WITHOUT a local browser (the no-browser-capable / listed merchant set). Use this when `local_browser_available` is false to tell the human which merchants you can still buy from, or to redirect after a request failed because the chosen merchant needs a browser. If you have a browser (`local_browser_available=true`) you can buy anywhere and do not need this list. Read-only; does not create or change anything.
check_merchantCheck whether you can complete a purchase at a given merchant URL from this session. Pass the merchant `url` and your `local_browser_available` flag. Returns `merchant_name`, `checkout_mode`, `no_browser_supported`, a definitive `can_purchase` boolean, and a human-readable `reason`. If you have a browser, `can_purchase` is always true (a browser can buy anywhere). If you have no browser, `can_purchase` is true only when the merchant supports no-browser checkout. Use this before requesting an allowance when you are unsure a no-browser session can fulfill a merchant; if `can_purchase` is false, suggest `list_supported_merchants` alternatives to the human. Read-only; does not create or change anything.
pause_allowancePause an allowance — blocks further card issuance. Only the human can unpause it via the Allowance app. Confirm with the human before calling.
revoke_allowancePERMANENTLY revoke an allowance. Cannot be undone. You MUST get explicit confirmation from the human before calling this.