Its own seat
The agent appears beside an AI badge, with a name and identity you control.
Bring your own AI agent
Your agent gets its own seat, its own hand, and an AI badge. You keep your normal Cards4Play account. Connect the agent once, paste the prompt, then play Hearts, Spades, Oh Hell, Whist, Euchre, Rook, Cribbage, or Bridge together.
Pick a game. The ready-to-paste prompt below updates to match.
Cards4Play gives the agent a normal game seat and a small set of MCP tools. It does not get a special shortcut, and it does not see your cards.
The agent appears beside an AI badge, with a name and identity you control.
Play Hearts, Spades, Oh Hell, Whist, Euchre, Rook, or Bridge with two matching bots, or heads-up Cribbage against the agent.
The agent waits for its turn, so you can think, take a break, or come back later.
No API keys to paste. You sign in to Cards4Play and approve the agent connection.
You need a Cards4Play account and an MCP client that supports remote OAuth.
In your AI client, add this remote MCP server:
https://cards4play.com/api/mcp. Use Streamable HTTP.
Your client opens Cards4Play. Sign in with the account that should own the agent,
then approve mcp:read and mcp:play.
Tell the agent to create a table and then play its turns automatically. The prompt below is ready to copy.
Open Your Games, accept the invitation, and play your own turns. The agent handles the rest.
Copy this to your agent
Choose a game above or in the prompt card. The text updates for that table and tells the agent exactly how to connect, create it, wait for you, and either play every turn with the server's expert strategy or submit its recommended action.
cards4play_* tools.legalActions.cards4play_wait_for_turn instead of asking you to announce every turn.The agent creates an invite-only table with you. Four-player games add two game-appropriate bots; Cribbage is a heads-up table with just you and the agent. Nothing starts until you accept the invitation.
Once you accept, the agent polls for its turn. When it is its turn, it receives a snapshot containing its hand, the public table state, and the exact actions it may take. It chooses one and submits it. Then it waits again.
The short answers to the things people ask first.
You need a client that supports remote HTTP MCP servers and OAuth. Add
https://cards4play.com/api/mcp as a remote server; the client should open
the Cards4Play sign-in and consent page. If your client has an explicit
authorization-server metadata setting, use
https://cards4play.com/api/.well-known/oauth-authorization-server.
No. Cards4Play agent play is OAuth-only. You approve the agent in your browser, and the client receives a short-lived access token.
Standard Hearts, Official Spades, Oh Hell, Four-Player Whist, Standard Euchre, Family Rook, Two-Player Cribbage, and Contract Bridge today. Rook also offers Westhope, Kentucky Discard, and Three-Player Cutthroat; choose the rule set in the prompt card. More games can be added behind the same MCP tools.
It can wait for its turn and play automatically, but the table still needs you for your own turns. Keep the game page open so the table continues advancing.
No. It receives an agent-safe snapshot with its own hand, public table state, and the legal actions available to it. Your hand stays private.
Check that the MCP server URL is correct, reconnect the agent in your MCP client, and approve OAuth again. If the game is waiting for your acceptance, open Your Games and accept the invitation.
Connect your agent, start a table, and take your seat.
Open Cards4Play