# Connect Oobit in Grok

Oobit is a payments app. Its MCP server lets an AI assistant pay online for a user with single-use virtual cards. Every purchase needs the user's confirmation in the chat. This page describes how the Oobit connector is set up in Grok Bot.

## Connector settings

Oobit is available in Grok Bot as the **Oobit** plugin, or can be added as a custom remote MCP server with these settings:

| Setting                       | Value                                                                         |
| ----------------------------- | ----------------------------------------------------------------------------- |
| Name                          | Oobit                                                                         |
| MCP server URL                | `https://mcp.oobit.co`                                                        |
| Transport                     | Streamable HTTP                                                               |
| Headers                       | None                                                                          |
| Authentication                | OAuth authorization code with PKCE (`S256`). Public client, no client secret. |
| Authorization server metadata | `https://mcp.oobit.co/.well-known/oauth-authorization-server`                 |
| Protected resource metadata   | `https://mcp.oobit.co/.well-known/oauth-protected-resource`                   |
| Client registration           | Dynamic client registration at `https://mcp.oobit.co/register`                |
| Redirect URI                  | Grok Bot's own OAuth callback                                                 |

There are no API keys.

## Sign-in

1. After the connector is added, Grok Bot starts OAuth and shows the user a sign-in link (or an **Authorize** button). Each attempt uses a new link; a link is valid for about 5 minutes.
2. The user opens the link. On a computer, the page shows a QR code to scan with the phone camera. On a phone, the Oobit app opens directly.
3. In the Oobit app, the user checks that the request is from Grok Bot and taps **Approve**.
4. The user returns to the sign-in page, which completes on its own.

Note for the user: on iPhone, the browser sometimes stays on a Cursor page after approving instead of returning to Grok Bot. The connection is already saved; switching back to Grok Bot is enough.

## Checking the connection

Once connected, the `get_account` tool returns the user's name and available balance. A successful call confirms the connection.

## Tools

| Tool              | What it does                                                              |
| ----------------- | ------------------------------------------------------------------------- |
| `get_account`     | Name, available balance and card limits                                   |
| `get_card`        | Creates a single-use card for one purchase the user confirmed in the chat |
| `get_card_status` | Whether a card was used, canceled or expired                              |
| `list_cards`      | The user's cards, newest first                                            |
| `cancel_card`     | Cancels an unused card and releases the funds                             |

Each card covers one purchase of up to the confirmed amount ($1 to $500) and expires one hour after it is created. The MCP server's own instructions describe the purchase flow in detail.

## Security

* Sign-in happens on Oobit's page and in the Oobit app. Oobit never asks for a password, one-time code, card number or token in the chat.
* Card numbers are returned only to the connected assistant, for the confirmed purchase.

## Troubleshooting

| Situation                                                               | Resolution                                                                                                        |
| ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| The Oobit app shows "Agent cards are not available on your account yet" | The Oobit account isn't eligible yet, usually because no Oobit card has been issued. Contact <support@oobit.com>. |
| "This request expired"                                                  | The link is older than 5 minutes or was already used. Start sign-in again for a new link.                         |
| On iPhone, the browser didn't return to Grok Bot                        | Switch back to Grok Bot; the connection is saved.                                                                 |

Support: <support@oobit.com>