#MCP Endpoint
#Quick Start Config
If your client supports direct remote MCP URLs, use the endpoint directly. If not, use mcp-remote bridge config.
Remote URL
url
https://mcp.wazabi.ai/mcpmcp-remote (public / no auth)
json
{
"mcpServers": {
"wazabi": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.wazabi.ai/mcp"
]
}
}
}mcp-remote (API key / bearer)
json
{
"mcpServers": {
"wazabi": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.wazabi.ai/mcp",
"--header",
"Authorization: Bearer YOUR_MCP_API_KEY"
]
}
}
}#How-To By Client
Claude
- 1Open Claude settings and go to Connectors / MCP.
- 2Add custom connector URL: https://mcp.wazabi.ai/mcp.
- 3If prompted, complete OAuth or provide bearer token as required by your server mode.
- 4Verify tools are listed, then run quote_launch_fee.
ChatGPT
- 1Open Connectors / Developer mode and add a custom MCP connector.
- 2Use endpoint https://mcp.wazabi.ai/mcp.
- 3Complete auth flow if enabled on server.
- 4Validate by listing tools then executing list_launches.
Cursor
- 1Open Cursor MCP settings.
- 2Paste the JSON config (public or API-key variant from above).
- 3Save, reload MCP servers, and confirm Wazabi tools appear.
- 4Run get_creator_proof_message as sanity check.
Replit
- 1Open Replit MCP integration settings for your workspace/agent.
- 2Add Wazabi MCP using direct URL or mcp-remote JSON.
- 3If using auth, store key as secret and inject into config.
- 4Test with quote_launch_fee on desired chain.
Codex
- 1Open Codex MCP configuration.
- 2Add a server entry using the same mcp-remote JSON format.
- 3Reload MCP runtime and check tool discovery.
- 4Run prepare_mint_bundle only after fee quote is valid.
Windsurf
- 1Open Windsurf MCP settings.
- 2Add Wazabi MCP using direct URL or mcp-remote JSON config.
- 3If using auth, configure bearer token in settings.
- 4Run list_launches to verify connection.
OpenClaw
- 1Open OpenClaw MCP settings.
- 2Add Wazabi MCP via mcp-remote JSON config.
- 3If server is protected, set bearer header in args.
- 4Confirm tool calls by running get_token_info.
#Canonical Launch Flow
Mint first, then LP lock. Default supply is 1,000,000,000 tokens. Creator allocation is 3–10% depending on lock tier.
| Step | Tool | What it does |
|---|---|---|
| 1 | get_creator_proof_message | Generate creator ownership message for wallet signature. |
| 2 | quote_launch_fee | Create a $5 fee intent quote per selected chain. |
| 3 | prepare_mint_bundle | Prepare mint transaction bundle + signing URL. |
| 4 | finalize_mint | Verify mint on-chain and persist indexed state. |
| 5 | prepare_lp_lock_bundle | Prepare LP add + lock bundle (7/14/30/90 day tiers). |
| 6 | finalize_lp_lock | Verify LP lock on-chain and complete launch record. |
#Troubleshooting
| Issue | Fix |
|---|---|
| 401 Unauthorized | Use OAuth login or set bearer token in connector config. |
| 429 Rate limit | Wait for retry window and avoid repeated high-cost tool bursts. |
| Finalize says pending missing | Pass tx hash/signature explicitly to recovery-aware finalize calls. |
| Logo upload slow/failing | Use smaller image or first run upload_logo and reuse logo_ref. |
| Tool not discovered | Check /tools endpoint and reconnect MCP client. |
Ready to connect?
Point Claude, Cursor, Codex, Windsurf, or any MCP-compatible client at the Wazabi server and start launching tokens onchain.
Open MCP Server