
Suigar Gaming
io.github.Suigar-GamingPublished by GitHub account Suigar-Gamingv1.0.0-beta.34Updated Nov 11, 2026
AI agent MCP server for Suigar casino game, SweetHouse, NFT, and referral transactions.
Overview
Local MCP server that lets an assistant read Suigar casino, NFT and referral data on Sui and build, dry-run or execute related transactions.
- What you can do
- Read Suigar config, live game metadata, NFT catalogs and wallet balances or coin lists
- Read referral commission and level-up reward amounts, and build unsigned claim transactions
- Build, dry-run or execute transactions for Coinflip, Keno, Limbo, Plinko, Soccer, Wheel, Range and PvP Coinflip
- Build SweetHouse deposit, redeem-request and delayed-claim transactions, plus NFT V1 mints
- Manage a paired browser wallet (login, logout, connection status) or a local session wallet with funding and status
- Show config, game parameters, NFT holdings, referral rewards and transaction details in an MCP App view
- When to use it
- Use it when you want an assistant to inspect Suigar game parameters, balances, NFTs or referral rewards on Sui, or to prepare and optionally submit wagers, mints, pool deposits and claims. It suits users who already hold a Suigar wallet and want agent-driven transaction building with dry-run checks before signing.
- Requirements
- Node.js ^24.0.0 or ^26.0.0, run locally via npx. A Suigar account and either a paired browser wallet (login opens a localhost pairing page) or a session wallet set up through a local page. Optional environment variables SUIGAR_MCP_BRIDGE_WEB_URL, SUIGAR_MCP_BRIDGE_TIMEOUT_MS, SUIGAR_MCP_BRIDGE_MAX_BODY_BYTES and SUIGAR_MCP_SESSION_SETUP_TIMEOUT_MS tune bridge and setup behavior. Network access to Sui mainnet or testnet.
Installation
In SourceWeft
- Open Suigar Gaming in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@suigar/mcp
MCP server for agents working with Suigar's provably fair casino games on Sui, SweetHouse pools, NFTs, and referral claims.
- SDK-backed tools for reading Suigar config and live game metadata
- Referral claimable-amount reads and unsigned claim builders
- Unsigned transaction builders for standard Suigar games, PvP Coinflip, and SweetHouse
build,dry-run, andread-onlymodes- An MCP App inspector for compatible hosts
- Text and structured results for other MCP clients
Transactions are unsigned by default. With mode: "execute", the paired Suigar browser wallet asks the user to approve the transaction. Selecting executionWallet: "session" signs and submits with the local session-wallet key stored in the operating-system keychain. Session execution returns the final transaction digest without an approval URL. Balance reads combine all result pages and format amounts using configured or on-chain coin metadata.
Malformed recovery phrases raise TypeError. Unsupported private-key schemes and oversized bridge requests raise RangeError. Wallet bridges and session setup validate 32-byte hexadecimal state tokens, then compare the decoded bytes with timing-safe equality. Setup pages display the error message. Operational failures, such as expired sessions or unavailable keychain storage, remain generic errors.
Agent skills
The package includes an agent skill that loads full instructions from main in Suigar-Gaming/agent-skills. It fetches references as needed.
Install the full skills with npx skills add Suigar-Gaming/agent-skills.
Install
Requires Node.js ^24.0.0 || ^26.0.0.
Install for all detected coding agents with add-mcp:
Add -y to skip the installer prompts. Restart or reload your MCP client after installation.
Manual configuration
Add the stdio server to your MCP client:
Package installation
Install the package directly when you need to import its programmatic API or run a local copy:
The package is also published on JSR for programmatic imports:
The server registers tools and resources through the MCP server and MCP Apps APIs. It targets MCP 2026-07-28. The server and bundled App use MCP SDK 2 and ext-apps 2 and support MCP Apps 1.x hosts.
Older clients that use initialization are also supported. Call startSuigarMcpServer() to start stdio, or createSuigarMcpServer() to get an McpServer from @modelcontextprotocol/server v2.
Plugins
The package also ships plugin/ manifests for plugin-capable hosts:
plugin/.codex-plugin/plugin.jsonfor Codexplugin/.claude-plugin/plugin.jsonfor Claude Codeplugin/.cursor-plugin/plugin.jsonfor Cursorplugin/plugin.jsonfor Antigravity-style plugin discovery
The Codex, Claude, and Cursor manifests use the bundled .mcp.json MCP config, which registers the npx -y @suigar/mcp@<package-version> stdio server. packages/mcp/package.json supplies the version for plugin manifests, the MCP config package specifier and package-local JSR configs. Run pnpm run codegen:version to sync them; pnpm run changeset:version also runs it.
Repository marketplace catalogs support GitHub installation and local plugin testing:
.agents/plugins/marketplace.jsonfor ChatGPT desktop and Codex.claude-plugin/marketplace.jsonfor Claude Code.cursor-plugin/marketplace.jsonfor Cursor multi-plugin repository discovery
For Codex, install the marketplace from GitHub, then install the suigar-mcp plugin:
For Claude Code, use the equivalent GitHub marketplace flow:
Inside an interactive Claude Code session, use /plugin marketplace add Suigar-Gaming/ts-sdks and /plugin install suigar-mcp@suigar instead. For local development, replace Suigar-Gaming/ts-sdks with . in either marketplace-add command. ChatGPT desktop local testing works by opening the repository, restarting the app, opening the Plugins directory in Work mode or Codex, then installing suigar-mcp from the Suigar source.
For Cursor, the repository includes both the plugin manifest and a root .cursor-plugin/marketplace.json for multi-plugin repository flows. During local development, you can also copy or symlink packages/mcp/plugin into Cursor's local plugin directory and reload Cursor. If you only need MCP tools, configure npx -y @suigar/mcp directly. You do not need a plugin wrapper.
Local development
The package uses the shared strict TypeScript checks with isolatedDeclarations disabled so Zod can infer schema and handler types. Run these commands from the repository root.
This builds the local workspace dependencies, MCP server, and bundled MCP App. Run the generated stdio entrypoint from the repository root for manual client testing.
Tools
setup_session_walletget_session_walletfund_session_walletsuigar_loginsuigar_logoutget_connection_statusread_configread_game_metadatalist_nftsget_wallet_balanceslist_wallet_coinsget_execution_statusget_referral_commissionget_referral_level_up_usd_rewardsbuild_referral_commission_claim_transactionbuild_referral_level_up_usd_rewards_claim_transactionbuild_nft_v1_mint_transactionbuild_sweethouse_deposit_transactionbuild_sweethouse_redeem_request_transactionbuild_sweethouse_claim_own_redeem_request_after_delay_transactionbuild_coinflip_transactionbuild_keno_transactionbuild_limbo_transactionbuild_plinko_transactionbuild_soccer_transactionbuild_wheel_transactionbuild_range_transactionbuild_pvp_coinflip_create_transactionbuild_pvp_coinflip_join_transactionbuild_pvp_coinflip_cancel_transaction
All tools return text in content alongside structuredContent. Known tools return isError: true for invalid inputs and handler failures. Handler errors include text and structured details. An unknown tool name raises a JSON-RPC invalid-params error (-32602).
Hosts that support MCP Apps can display config, live game parameters, the NFT catalog and wallet holdings, referral rewards, SweetHouse plans, and transaction details in the bundled App.
Wallet tools
- Paired browser wallet
suigar_login,suigar_logout, andget_connection_statusmanage the paired browser wallet.suigar_loginandsuigar_logoutstart the same localnpx -y @suigar/mcp ...CLI flows used for command-line wallet management, so the pairing page for mainnet or testnet opens in the default browser without copying and pasting a URL.suigar_loginandsuigar_logoutacceptwebUrl,timeoutMs,maxBodyBytes,open, andnoOpeninputs matching the CLI bridge options.get_wallet_balancesandlist_wallet_coinsread aggregate balances or paginated coin objects. Both also accept an explicit address.get_execution_statuschecks anexecute-mode transaction's browser approval result.
- Local session wallet
setup_session_walletopens a local, one-time setup page to create or recover one persistent session wallet shared by mainnet and testnet.- Set
SUIGAR_MCP_SESSION_SETUP_TIMEOUT_MSto control how long local setup pages remain available. The built-in default is600000. - It does not require a paired browser wallet, and its recovery phrase never passes through MCP.
- The local setup page can also import a standard
suiprivkey...export. It never passes through MCP or the session-wallet JSON file. - Store the signing key in the operating-system keychain without a separate application passphrase. Do not use custom encrypted files. Use a dedicated wallet with a small balance to limit the funds the session can spend.
- MCP keeps one active session wallet. Restarting MCP automatically uses that same keychain entry; importing or recovering another wallet requires explicit replacement confirmation. Keep the original recovery phrase/private-key backup to restore it later.
get_session_walletreturns the public address, formatted balances, and a funding QR code. If a wallet is paired on the selected network, it also returns a prefilled funding URL.fund_session_walletrequires a paired wallet and opens a prefilled mcp-website transfer form. The user chooses an owned coin and amount, then reviews and signs the transfer in their browser.- In an App-capable host, it displays a dedicated Session Wallet view with balances for the selected network, a funding QR code, and a paired-wallet funding link when available. If no wallet exists, the same view provides the local setup link.
- Fund only the amount the user is willing to delegate to the local MCP process.
- For game tools, use
mode: "execute", executionWallet: "session"to make the session wallet the sender and submit immediately.owneris optional in this mode; if supplied, it must match the session-wallet address. Fund it for both the wager and gas. You can set a custom provider URL and partner; custom SDK config overrides are rejected. Before signing, the server verifies that the built transaction calls only the selected Suigar game package.
- Command-line wallet management
- Run
npx -y @suigar/mcp login --network testnet(ormainnet),status,logout, orclean. - Login uses a short-lived, localhost-only browser pairing flow and stores non-secret network-specific metadata in
~/.suigar-mcp/credentials.jsonwith owner-only permissions. statusshows the current connection.logout --alldisconnects every stored network and opens both logout pages when using the default Suigar mainnet and testnet web origins.cleandeletes the local credential file without opening a browser.- Set
SUIGAR_MCP_BRIDGE_WEB_URLor pass--web-urlto use a local or custom connection-page origin. - Set
SUIGAR_MCP_BRIDGE_TIMEOUT_MSor pass--timeout-msto control how long login, logout, and approval bridges wait before expiring. The default is300000. - Set
SUIGAR_MCP_BRIDGE_MAX_BODY_BYTESor pass--max-body-bytesto control the maximum browser callback JSON body size. The default is16384. - Bridge URLs open automatically by default. Pass
--no-openfor CLI login or logout when you only want the URL or URLs printed. - The MCP client discovers tools through the protocol.
- Run
Read tools
read_config,read_game_metadata,list_nfts, wallet balance/coin reads, execution status, and the referral amount reads are read-only.- SDK-backed reads accept shared network, provider, SDK config, and partner inputs.
read_game_metadataalso requiresgame. NFT and referral reads also require anowneraddress or SuiNS name.- Referral reads simulate the SDK's real claim transaction and return
0when it cannot be claimed or simulated. get_referral_commissionaccepts an optionalcoinType(defaulting to configured SUI); level-up USD rewards use configured USDC.
In hosts that support Apps, the NFT view has separate tables for the catalog and owned NFTs. It shows HTTPS NFT images as thumbnails and keeps unavailable or unsupported image URLs as text. Referral reads open a Referral Rewards view showing the referrer, reward type, coin type and simulated claimable amount.
Transaction tools
All transaction tools accept the shared config inputs and support these mode values:
read-only: resolves SDK config and returns the intended Move target, type arguments, required inputs, and notes.build: returns unsigned transaction bytes as base64 plus a transaction summary with resolved shared inputs and game-specificgameInputssuch as coinflipside, KenoconfigIdandpicks, limbotargetMultiplier, plinko/wheelconfigId, and range points.dry-run: simulates the unsigned transaction through Mysten client APIs and returns a JSON-safe rawdryRunresult plus a stabledryRunSummary. Failed dry-runs include anerrorsarray extracted from the failed transaction status.execute: by default opens a paired-wallet approval request. SetexecutionWallet: "session"for game tools to have MCP sign and execute immediately with the local session wallet instead.
Transaction summaries include the configured gas budget as raw MIST plus a SUI display value when gasBudget is provided or present on the built transaction.
Dry-run summaries include:
successanderror- Gas computation, storage, rebate, non-refundable storage fee, and net gas delta as raw base units plus decimal-formatted display values
- Balance changes as raw base units plus decimal-formatted display values
- Decoded event fields when available, including standard
BetResultEventgame details such asplayer_bet,coin_outcome,stake_amount, andoutcome_amount; the MCP App renders all parsed result fields it receives, so non-coinflip games expose their own parsed result keys as well
Shared transaction inputs
For build, dry-run, and paired-wallet execute, provide owner, a raw Sui address, SuiNS name such as name.sui, or SuiNS subname such as sub.name.sui. The server resolves SuiNS owners through the configured network before building or dry-running the unsigned transaction. In session execution (mode: "execute", executionWallet: "session"), MCP uses the local session-wallet address and no owner is required. read-only can be used to inspect a tool's requirements before providing an owner.
coinType defaults to configured SUI. Transaction stake, cashStake, and SweetHouse amount inputs are currency amounts in the chosen coin, not base-unit integers. For example, stake: 1 or amount: 1 means 1 SUI or 1 USDC depending on the resolved coin type. The server converts these amounts to base units using the configured coin decimals before calling the SDK transaction builders.
Set the optional gasBudget in MIST. Bet builders also accept metadata. Use JSON-compatible strings, numbers, or booleans for metadata values and send large integers as strings. Tools that source native SUI coins, including native SUI bets and NFT V1 mint, accept useGasCoin. PvP Coinflip cancel neither creates a bet coin nor writes metadata, so it accepts neither metadata nor useGasCoin.
When betCount is provided for Keno, Limbo, Plinko, Range, Soccer, or Wheel, the MCP server reads the active on-chain parameters and rejects a value above that game's declared maximum. Coinflip does not declare a maximum bet count.
Workflow-specific inputs
Config
network defaults to testnet. Only mainnet and testnet are supported.
Before forwarding config overrides to the SDK, the server skips nested fields set to undefined and keeps concrete values, including zero.
Optional config input follows the public SDK extension override shape:
Game, referral, and core calls use the @suigar/* MVR package names by default. Optional packageIds entries override those package names when needed; nftV1 remains configured by network because it is not resolved from MVR.
Pass the partner wallet address as the top-level partner option. The server forwards it through suigar({ partner }).
Source: packages/mcp/README.md at commit ebabc7b
Tools
0Version history
7- v1.0.0-beta.34LatestNov 11, 2026
- v1.0.0-beta.33Nov 6, 2026
- v1.0.0-beta.32Nov 4, 2026
- v1.0.0-beta.31Oct 22, 2026
- v1.0.0-beta.30Sep 26, 2026
- v1.0.0-beta.29Sep 21, 2026
- v1.0.0-beta.28Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts