Use an AI assistant
Connect an assistant such as Claude to turn your description into a replay in your binked account. The connection uses MCP, the standard that lets an assistant use tools in another app.
Connect with binked Sign-In (Recommended)
Use OAuth sign-in when your assistant supports it. You approve access on binked and do not need to create or copy a personal token.
- Open your assistant's connectors or remote MCP settings. In Claude, open Customize → Connectors, then + → Add custom connector.
- Name the connector binked and enter
https://api.binked.app/mcpas the server URL. In Claude, leave the optional OAuth Client ID and Client Secret fields empty. - Add the connector and choose Connect. Sign in to the binked account where you want your hands saved.
- Review the app name and permissions on binked, then select Connect to return to your assistant.
- Enable the binked connector in your conversation. In Claude, use the chat's + → Connectors menu.
For Claude workspace restrictions and current setup screens, see Claude's custom connector guide. Other clients need to support binked's MCP authorization flow; see the technical connection reference if sign-in is unavailable.
Describe, Preview, Then Publish
Include the game variant, blinds and any antes or straddles, player positions, starting stacks, known hole cards, and actions on each street. At showdown, say who showed or mucked. For multiple runouts, give each board.
Try this complete example:
Preview this hand in binked without publishing it: heads-up no-limit hold'em, blinds 1/2, both players start with 100 chips. I'm on the button/small blind with As Kd. I raise to 6 total and the big blind folds. Title: Button takes it down. Ask me about anything missing.
Check positions, stacks, cards and bet amounts in the preview. Claude and other clients that support interactive MCP apps can show a playable replay in chat; other clients return text. A preview is not saved and has no public replay link.
When it is correct, ask: “Publish this hand to binked and give me the replay link.” The saved hand appears in Hands. Published replays are public and cannot be edited, so make corrections before publishing.
The assistant may ask follow-up questions because binked requires a complete, valid hand. Unknown hole cards can stay unknown when they are not needed to determine the result; missing actions or required showdown cards need to be supplied.
Ask for a Video
After publishing, ask: “Create a portrait video of this hand.” If you granted video access, the assistant starts the render and gives you a binked export-page link. Open it while signed in to the same account to check progress and download or share the MP4. Rendering takes a few minutes. The usual video formats and limits apply.
Manage Your Assistant's Access
The approval page lists the access requested: validating and publishing hands, starting video renders, or both. The assistant cannot read your hand history or collections, edit or delete saved hands, or manage your account.
Open Settings → AI agents to see connected apps and their permissions. Select Disconnect to revoke a connection. This does not remove replays already published. Remove the connector in your assistant too if you no longer want to use it. Unused connections expire after 90 days.
If Something Does Not Work
- No binked tools in chat: check the server URL, finish sign-in, and enable the connector in the conversation.
- Sign-in fails or the connection expired: start a fresh connection from your assistant. An old consent link may no longer be valid.
- Hands work but video is unavailable: check the permissions under AI agents. If video access is missing, disconnect and reconnect, approving video access when requested.
- The hand is rejected: review the missing details or inconsistent actions with your assistant, then ask for another preview.
- Your client cannot use sign-in: use a personal token as described below.
Personal Tokens for Scripts and Other Clients
For the HTTP API or clients that cannot use OAuth, open Settings → AI agents and expand Personal access tokens · Advanced. Name and create a token, then copy it into your client's secret configuration. It is shown only once; do not paste it into chat. Tokens allow hand creation and video renders, expire after 90 days, and can be revoked on the same page.
The developer API reference contains configuration examples, hand schemas, tool details and limits.