How to Connect Tabby to Gemini via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Tabby, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Tabby + Gemini

Tabby buy now, pay later (UAE, Saudi Arabia, Kuwait): look up payments with their captures and refunds, checkout sessions, customer disputes and webhooks. Capture, refund and close are included, installed switched off.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

TABBY_API_URL, TABBY_SECRET_KEY

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a Tabby merchant account and its secret API key.

1. Sign in to the Tabby Merchant Dashboard (merchant.tabby.ai for the UAE, merchant.tabby.sa for Saudi Arabia), or ask your Tabby partner manager for the API keys.
2. Copy the secret key into TABBY_SECRET_KEY: sk_test_... for test payments, sk_... for live ones. The public key (pk_...) does not work here.
3. Set TABBY_API_URL to the API of your merchant region: https://api.tabby.ai for the UAE (and Kuwait), https://api.tabby.sa for Saudi Arabia. Tabby expects every call to go to the merchant's region. Test and live use the same address; the key decides.
4. Install the connector and run tabby_search_payments: it lists your latest payments and confirms the key.

Payment id and order number: a payment id is a UUID assigned by Tabby; your own order number is order.reference_id of the payment. To find a payment from an order number, the AI lists the payments of the order date with tabby_search_payments (created_from / created_to) and matches order.reference_id.

What it reads: your payments, newest first, with status, amount and currency, buyer (name, e-mail, phone), order reference and items, captures and refunds; one payment in full, with shipping address, tax, shipping, discount and every capture and refund with amounts and dates; checkout sessions, when a customer's checkout did not finish; customer disputes with reason, comment, attachments, disputed items and the days left before they are approved automatically; and the webhooks registered for a merchant code (the value of their header is not returned).

Payment status: AUTHORIZED means the customer approved and nothing is captured yet; CLOSED means captured in full or closed; REJECTED and EXPIRED mean no money moved. Without a status filter the search returns only AUTHORIZED and CLOSED payments.

Switched off at install: tabby_create_capture (captures an AUTHORIZED payment in full or in part when the order ships), tabby_create_refund (refunds a CLOSED payment; the money goes back to the customer at once and cannot be taken back) and tabby_close_payment (releases what is not captured, for a cancelled order or after a partial capture). They move money, so an administrator turns them on deliberately. Even then the AI shows you the payment, the amount and the currency and waits for your yes, and it passes a reference_id so a retry is not executed twice.

Amounts and times: amounts are strings with up to 2 decimals (AED, SAR) or 3 (KWD). Dates and times are UTC, ISO 8601.

Limits: the payment search returns at most 20 payments per call, and the AI pages with offset. The dispute list returns the 100 most recent disputes and pages with a token.

Common errors: 401 means a wrong secret key or a public key; 400 with an empty body can also be a missing key. 403 or 404 for a payment that exists usually means the wrong region in TABBY_API_URL. 409 on a refund means the payment is not refundable yet (not CLOSED) or the amount is too high.

The connector does not create checkout sessions, update payments, register webhooks or answer disputes; do those in the Tabby Merchant Dashboard.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Gemini

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Gemini CLI reads MCP servers from ~/.gemini/settings.json (on Windows %USERPROFILE%\.gemini\settings.json). Add:

{
  "mcpServers": {
    "anythingmcp": {
      "httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}

1. Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of YOUR_MCP_API_KEY.
2. Save the file and restart gemini.
3. Run /mcp inside Gemini CLI (or gemini mcp list in your shell): anythingmcp should show as connected.
4. Start prompting: Gemini CLI can now call the Tabby tools.

Available tools

Example prompts

• "Which Tabby payments were created yesterday, and which of them are still AUTHORIZED and not captured?"
• "Find the Tabby payment for our order number 100245 and show its captures and refunds."
• "List the open disputes and how many days are left on each before it is approved automatically."
• "A customer says the Tabby checkout did not finish: check this checkout session and tell me what happened."
• "Refund 120 AED on the Tabby payment of order 100245. Show me the payment and the amount first."

FAQ

Where does Gemini CLI look for MCP servers? In ~/.gemini/settings.json for your user, or in .gemini/settings.json inside a project. gemini mcp list shows each server and whether it connects.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Meta Muse
• Connect to Microsoft Copilot