Build with AI
Your coding agent can put a game, app or site on crypto with Chain Daddy: find or launch a token, sell items for it, sign players in with their wallet, and check purchases on your server. Give it three things: the plugin (what to do and the mistakes to avoid), the MCP servers (tools), and the docs.
Your agent never needs your private key or seed phrase. Anything that moves money or launches a token, it prepares and you sign.
Install the plugin
The chaindaddy plugin adds skills your agent loads when a task needs them, and connects both MCP servers below. Its source is public at gitlab.com/opencrown/chaindaddy-plugins.
Claude Code
claude plugin marketplace add https://gitlab.com/opencrown/chaindaddy-plugins.git
claude plugin install chaindaddy@chaindaddyCodex
codex plugin marketplace add https://gitlab.com/opencrown/chaindaddy-plugins.git
codex plugin add chaindaddy@chaindaddyCursor: add the remote server below, and copy the skills into ~/.cursor/skills:
git clone --depth 1 https://gitlab.com/opencrown/chaindaddy-plugins.git ~/.chaindaddy-plugins
mkdir -p ~/.cursor/skills && cp -R ~/.chaindaddy-plugins/plugins/chaindaddy/skills/* ~/.cursor/skills/| Skill | Your agent uses it to |
|---|---|
add-crypto-to-your-game | Walk the whole path: token, store, sign-in, server checks, test store first |
sell-items-in-your-app | Run a store: items, orders, delivery, rewards, webhooks |
sign-in-with-chain-daddy | Add Sign in with Chain Daddy to your site or app |
verify-receipts-and-sessions | Verify receipts, session tokens and webhooks on your server |
build-a-crown-app | Build, test and publish an app for token pages |
launch-a-token | Prepare a launch for you to sign |
find-and-check-a-token | Find a token and tell the registered one from copycats |
check-token-health | Read health scores and what keeps a registration |
export-a-listing | Prepare listing-site fields |
In Claude Code the plugin also guards your wallet. It refuses any tool call that carries a recovery phrase, private key or Solana keypair, and it asks you before any command that sends a transaction on a mainnet. /chaindaddy store opens a live pane on your store, your test store first, as orders and webhook deliveries come in. The pane appears once mods are turned on in your Claude Code. Details are in the plugin's README.
Connect the remote MCP server
https://api.chaindaddy.io/mcp gives any AI app Chain Daddy's tools and docs, with no key. It lists about thirty tools (search, tokens and registrations, launch venues, your token's holders, broadcasts, alerts and deals, your apps and store), and find_api_operations reaches every other operation in the API reference. Public reads need nothing; your own data asks you to sign in with Chain Daddy the first time, and changes ask you to allow them. Nothing it does moves money or tokens.
| App | How |
|---|---|
| Claude (web and desktop) | Settings → Connectors → Add custom connector, and paste the URL |
| ChatGPT | Turn on developer mode in settings, then add a plugin with the URL |
| Claude Code | claude mcp add --transport http chaindaddy https://api.chaindaddy.io/mcp |
| Codex | codex mcp add chaindaddy --url https://api.chaindaddy.io/mcp |
| Cursor | {"mcpServers":{"chaindaddy":{"url":"https://api.chaindaddy.io/mcp"}}} in .cursor/mcp.json, or the one-click link in the plugin's README |
The local MCP server, for store work
The npm package @chaindaddy/mcp runs on your machine and has every tool, including the creator store (iap_*: items, orders, test store, keys, drops, webhooks). The plugin starts it for you; on its own:
claude mcp add chaindaddy-local -- npx -y @chaindaddy/mcp # Claude Code
codex mcp add chaindaddy-local -- npx -y @chaindaddy/mcp # Codex{ "mcpServers": { "chaindaddy-local": { "command": "npx", "args": ["-y", "@chaindaddy/mcp"] } } }Each release is built from public source with npm provenance: verify it with npm audit signatures in a project that installs it.
Every tool needs your account key, reads included (a Free key is enough). Set it in your shell, not in a chat:
| Variable | What |
|---|---|
CHAINDADDY_API_KEY | Your cd_live_… key from chaindaddy.io/_api: every call, and opening a store, items, store keys |
CHAINDADDY_IAP_KEY | A cd_iap_… store key, to act as your app server would |
Build against the test store first: orders are paid with one call, and no money moves.
Docs for agents
/llms.txt | An index of every page |
/llms-full.txt | Every page in one file |
/md/{path}.md | Any page as Markdown, e.g. /md/developer/store-and-rewards.md |
/openapi.yaml | The API |
The CLI takes --json --non-interactive on every command, for agents and CI.