Connect an AI assistant

Heth MCP gives an assistant limited access to your own account, including available business functions. It cannot grant platform administration access. Opening a connection screen grants no permission.

Connect an assistant

1. In the Heth app where your wallet is already open, go to Settings → AI connections and choose Create connection code. The one-time code belongs to that account and expires after five minutes.
2. In your AI client’s connection settings, add https://mcp.heth.me/mcp and choose OAuth. Start connecting.
3. In the connection window, enter only the code from Heth. You do not sign in to your wallet in this browser. The code sends a request to the exact account that created it; it grants no access.
4. Open the push in the Heth app. If it does not arrive, open Settings → AI connections → Connection requests. Compare the request verification code with the one in the connection window, and check the account, client identifier and service address. The application name alone does not verify identity.
5. In Heth, uncheck permissions you do not want to share and choose Approve selected AI access, or choose Deny AI access. Opening the push alone does not approve anything.
6. Return to the AI client. Its connection window finishes automatically after your decision in Heth. Your wallet session and signing keys stay in Heth.

A used or expired connection code cannot be reused. Create a new code in Heth; creating one replaces the previous unused code. If the whole connection request expires, restart from the AI client.

In ChatGPT

Open Plugins → Add → Add custom MCP server, enter a name such as Heth.me and the server address above, and keep OAuth selected. ChatGPT discovers the connection settings automatically; no wallet API key, client secret or recovery phrase is needed. Create the personal plugin, choose Connect Heth.me, then follow the code-and-push steps above. You can select default permissions under Advanced OAuth settings; the final account permission choice is confirmed in the Heth app.

After connection, select Heth.me in the chat and try “Show my wallet balances using Heth”. The available tools depend on the permissions you approved.

Permissions and tools

Only permissions requested by the client and currently available to your account can be approved. A tool is visible only with its required permission. Tools cover account data, transfers, ordinary business changes, subscription requests and OBS.

Permission	Tools and purpose
heth:wallets:read	get_wallet_balances: own wallet balances
heth:transactions:read	list_transactions, get_transaction: own history and original transaction status
heth:business:read	list_products, list_business_payment_links, list_business_subscriptions: own products, managed links and merchant subscriptions; get_business_subscription, list_business_subscription_requests read an agreement or outgoing requests
heth:payments:prepare	prepare_transfer, get_transfer_request: prepare a transfer for approval in Heth and read the original result
heth:business:manage	create_business_product, update_business_product, delete_business_product; create_business_payment_link, update_business_payment_link, delete_business_payment_link: ordinary changes confirmed in the AI client
heth:business:manage	request_business_subscription: request a customer's approval in Heth; prepare_business_subscription_change: review pause, resume or cancellation in Heth
heth:obs:read	get_obs_widget, list_obs_events: settings and incoming events
heth:obs:configure	prepare_obs_connection, update_obs_widget: Heth review link, or appearance fields only with confirmation in the AI client

prepare_obs_connection creates no access and returns no OBS token. Currency/network, receiving accounts, keys and access permissions cannot be changed by an appearance tool. See the OBS setup and customization guide, including the open source project and instructions for coding assistants.

How long access lasts

Your connection permission lasts until you revoke it. Technical credentials expire separately: MCP access tokens last 15 minutes; refresh tokens rotate and expire after 30 days without renewal. An expired technical credential may require you to connect again even if the consent record remains active.

Each request checks the current connection and account permissions. Heth uses a separate restricted API credential valid for at most 60 seconds to serve MCP requests; the full wallet session is not shared with MCP. Revoking consent or withdrawing account permissions blocks subsequent requests, including requests with unexpired tokens. Data already returned to the client cannot be recalled.

Revoke or reconnect

In Heth, open Settings → AI connections, check the client identifier, service address, permissions and status. Choose Revoke AI access and confirm in Heth. Revocation does not cancel completed payments or subscription debit mandates; manage those separately in subscription settings.

If asked to reconnect, start a fresh authorization in your AI client. Revocation, expired credentials, withdrawn permissions or detected reuse of a refresh token can end access. Do not paste recovery phrases, wallet keys or browser-session credentials into an assistant to repair the connection. An unavailable service is an error, not an empty account or a successful approval.

Payments and other changes

Heth requires separate confirmation in Heth for every monetary operation. A connection permission does not authorize automatic spending.

Ordinary product and payment-link edits require confirmation in the AI client. Changes to access rights, payout recipients or future-debit authorization require Heth confirmation. OBS appearance follows the client-confirmation policy. A tool annotation alone does not prove that a client obtained approval.

You can also use the Heth application or the supported API integration.

Transfer with an assistant

1. Tell the assistant the transfer type, recipient, currency, network and amount. Internal-to-internal (hot_hot), internal-to-blockchain (hot_cold), blockchain-to-your-internal-account (cold_hot) and blockchain-to-blockchain (cold_cold) are distinct operations. Use self as the recipient for cold_hot; it credits your own Heth account.
2. prepare_transfer saves the terms and returns a Heth review link. It creates no payment. Amounts and max_debit use exact integer strings in the token's minor units. max_debit caps the token debit including platform fees. For a blockchain source, max_network_fee caps the transaction's network gas charge in wei (ETH/Base) or sun (TRON). Base may additionally charge an L1 data fee.
3. Open Heth and check the account, requesting client, recipient, source, amount, network and fee limits. Choose Confirm and send in Heth only when all terms are correct. Opening the link does not approve or send anything. Requests expire after 15 minutes.
4. Heth signs the displayed instruction and uses its normal transfer flow. Blockchain transactions are signed on your device or a connected signing device. Open Heth where the source account can be signed; private keys never go to the assistant.
5. The assistant reads get_transfer_request to check the original transaction. Approved or processing is not the same as paid. After a timeout, read the original result; reuse the same request_id and identical terms if a preparation must be retried. Do not create a second transfer to resolve an uncertain outcome.

Revocation blocks a new transfer from starting. A transaction already accepted for execution can still complete; revoking an AI connection does not cancel an accepted blockchain transfer.

Products, links and subscriptions

The assistant shows ordinary product or managed-link changes for confirmation in the AI client. Price and link amounts are integer strings in minor units; product quantities are positive whole numbers. A stable request_id makes retries idempotent. These operations cannot edit payment routing, payout recipients, keys or access rights. Deleting a link or product does not reverse an earlier payment.

request_business_subscription creates a request for the payer to review in Heth. It grants no future-debit permission and creates no charge by itself. The payer reviews the amount, frequency and first charge before signing in Heth. Use list_business_subscription_requests to check requests, and get_business_subscription or list_business_subscriptions for existing agreements.

To pause, resume or cancel an agreement, prepare_business_subscription_change returns a Heth review screen. Nothing changes until the owner confirms there. Resuming permits scheduled charges under the existing payment permission. Cancellation stops future charges and does not refund completed payments. Changing the agreed billing terms requires a new payer approval.