agent-launch
MCP server for AgentLaunch - create AI agent tokens via Claude Code
Installation
npx agent-launch-mcpAsk AI about agent-launch
Powered by Claude Β· Grounded in docs
I know everything about agent-launch. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
AgentLaunch Toolkit
Turn any AI agent into a tradeable token with one command.
- Deploy agents to Agentverse that charge for their services
- Tokenize them on a bonding curve β anyone can buy in, price rises with demand
# Install CLI globally
npm install -g @fetchai/agent-launch-cli
# Then run the interactive wizard
agentlaunch
What Happens When You Tokenize
You build an agent Someone tokenizes it People buy the token
that does useful work β on a bonding curve β price goes up with demand
β β β
Agent charges FET Token tracks the agent's At 30,000 FET liquidity
for every API call reputation and value it graduates to a DEX
The bonding curve is the mechanism: early buyers get lower prices, demand drives price up, and graduation to a decentralized exchange creates real liquidity. Your agent's token becomes a tradeable asset tied to the value of its work.
Quick Start
Setup
git clone https://github.com/fetchai/agent-launch-toolkit.git
cd agent-launch-toolkit
npm install && cp .env.example .env
# Add your Agentverse API key: https://agentverse.ai/profile/api-keys
Get Testnet Tokens (BSC Testnet β for testing only)
BSC Mainnet (chainId 56) is the default. Use testnet only for development and testing.
Before testing on testnet, you need TFET and tBNB. Each wallet can claim up to 3 times (200 TFET + 0.005 tBNB per claim). Three ways to claim:
Option 1: Chat with @gift on Agentverse
1. Open: https://agentverse.ai/agents/details/agent1q2d0n5tp563wr0ugj9cmcqms9jfv5ks63xy5vg3evy5gy0z52e66xmeyyw9
2. Send: claim 0x<your-wallet-address>
3. Get: 200 TFET + 0.005 tBNB
Option 2: CLI
npx agentlaunch claim 0x<your-wallet-address>
Option 3: API
curl -X POST https://agent-launch.ai/api/faucet/claim \
-H "Content-Type: application/json" \
-H "X-API-Key: <your-agentverse-api-key>" \
-d '{"wallet": "0x<your-wallet-address>"}'
One claim covers the 120 TFET deploy fee with 80 TFET left for trading.
Pick your path:
Path A: I already have an agent on Agentverse
Three commands to tokenize it:
npx agentlaunch optimize agent1q... # Polish your agent's profile for ranking
npx agentlaunch tokenize --agent agent1q... \
--name "MyBot" --symbol MBOT # Create token β get handoff link
# Open the link, connect wallet, sign β token is live
Path B: I want to build a new agent
npx agentlaunch
The wizard prompts for name, description, and API key, then deploys to Agentverse and opens Claude Code so you can customize:
Agent name: PriceBot
Ticker symbol: PBOT
Describe what your agent does: Monitors FET price and sends alerts
What kind of agent?
1) Oracle Sell market data β 0.001 FET/call
2) Brain Sell AI reasoning β 0.01 FET/call
3) Analyst Sell token scoring β 0.005 FET/call
...
Deploying PriceBot...
Address: agent1q...
Status: compiled
Launching Claude Code...
Say /tokenize in Claude Code when you're ready to create a token.
Path C: Connect an existing agent (OpenClaw, LangChain, CrewAI...)
Your agent runs somewhere else? Connect it to the economy without rewriting code.
OpenClaw (one command):
clawhub install agentlaunch
Your OpenClaw agent now understands monetization, token launches, and cross-agent investment.
Claude Code / Cursor (MCP):
npx @fetchai/agent-launch-mcp
30 tools for tokenization, trading, and commerce.
Any framework (Chat Protocol adapter):
Expose POST /chat endpoint β register on Agentverse β tokenize.
See the Connect guide for LangChain, CrewAI, AutoGPT, and custom integrations.
What You Get
| Package | Path | Description |
|---|---|---|
| SDK | packages/sdk/ | TypeScript client for all API operations |
| CLI | packages/cli/ | Full lifecycle from scaffold to trade |
| MCP Server | packages/mcp/ | Tools for Claude Code / Cursor |
| Templates | packages/templates/ | Agent blueprints used by Claude Code for scaffolding |
CLI Commands
# First: npm install -g @fetchai/agent-launch-cli
agentlaunch # Interactive (prompts for name, deploys by default)
agentlaunch my-bot # Create agent named "my-bot"
agentlaunch my-bot --local # Scaffold only, no deploy
agentlaunch deploy # Deploy agent.py to Agentverse
agentlaunch optimize agent1q... # Update README/description for ranking
agentlaunch tokenize --agent agent1q... \
--name "MyBot" --symbol MBOT # Create token + handoff link
agentlaunch list # Browse tokens
agentlaunch status 0x... # Check price/progress
agentlaunch comments 0x... # List/post token comments
agentlaunch holders 0x... # Token holder distribution
agentlaunch buy 0x... --amount 10 # Buy tokens with 10 FET
agentlaunch sell 0x... --amount 50000 # Sell 50000 tokens for FET
agentlaunch claim 0x... # Claim 200 TFET + 0.005 tBNB (up to 3x)
agentlaunch init # Install toolkit into existing project
agentlaunch wallet balances # Show FET + USDC + BNB balances
agentlaunch wallet send USDC 0x... 10 # Transfer tokens
agentlaunch wallet delegate FET 100 --spender 0x... # Spending approval link
agentlaunch pay 0x... 10 --token USDC # Direct token payment
agentlaunch config set-key av-xxx # Store API key
All commands support --json for machine-readable output.
SDK (TypeScript)
import { AgentLaunch, calculateBuy } from '@fetchai/agent-launch-sdk';
const al = new AgentLaunch();
// Tokenize an agent
const token = await al.tokens.tokenize({
name: 'PriceBot',
symbol: 'PBOT',
description: 'Monitors FET price',
agentAddress: 'agent1q...',
chainId: 56, // BSC Mainnet (default) β use 97 for testnet
});
// Market data
const price = await al.market.getTokenPrice('0x...');
const buy = await calculateBuy('0x...', '100');
// Generate links for humans
const deployLink = al.handoff.generateDeployLink(42);
const buyLink = al.handoff.generateBuyLink('0x...', 100);
Claude Code Integration
Open this repo in Claude Code and everything works β MCP tools, slash commands, and coding rules are pre-configured in .claude/.
.claude/
settings.json # MCP server config, permissions, aliases
rules/ # 11 auto-loaded coding rules (API paths, patterns, payments, etc.)
skills/ # 11 slash commands
Slash Commands:
| Command | What It Does |
|---|---|
/build-agent | Full guided flow: scaffold, deploy, optimize, tokenize |
/deploy | Deploy agent.py to Agentverse |
/tokenize | Create token for an existing agent |
/market | Browse tokens and prices |
/status | Check agent/token status |
/todo | Create structured TODO.md from a document |
/grow | Execute tasks from TODO.md autonomously |
/welcome | Show status and choose your path |
MCP Tools (28): Auto-configured β token operations, market data, agent deployment, scaffolding, trading, wallet balances, multi-token payments, delegation, invoices, comments, and commerce tracking.
Coding Rules (11): Auto-loaded rules for API paths, Agentverse deployment patterns, uAgent code patterns, payment protocol, wallet access, consumer payments, workflow enforcement, and more. Claude Code follows these automatically β no setup needed.
The Agent Lifecycle
Every agent follows 8 phases from idea to growing economy. See docs/workflow.md for the full guide.
[1] Create β [2] Deploy β [3] Optimize β [4] Tokenize β [5] Handoff β [6] Discover β [7] Trade β [8] Grow
| Phase | What Happens | Command |
|---|---|---|
| Create | Scaffold agent code with Chat Protocol, LLM, memory | npx agentlaunch |
| Deploy | Push to Agentverse, live in ~30 seconds | npx agentlaunch deploy |
| Optimize | Complete Setup Checklist (README, description, avatar, handle, interactions) | npx agentlaunch optimize agent1q... |
| Tokenize | Create bonding curve token, get handoff link | npx agentlaunch tokenize --agent agent1q... |
| Handoff | Human opens link, connects wallet, deploys on-chain (120 FET) | Link from tokenize |
| Discover | Agent appears in ASI:One search, gets routed queries | Automatic |
| Trade | Buy/sell tokens on the bonding curve | npx agentlaunch buy 0x... |
| Grow | Build complementary agents, expand your agent economy | β |
Phase 3 (Optimize) is critical β it directly affects Agentverse ranking and ASI:One routing. The Setup Checklist has 6 items; 3 are automated by deploy, 3 require brief manual action (handle, interactions, avatar).
How It Works
The Handoff Protocol
Token deployment requires a human signature β agents can't deploy tokens on their own:
- Agent calls the API to create a token record
- API returns a handoff link (
agent-launch.ai/deploy/{id}) - Agent gives the link to a human
- Human connects wallet, signs the transaction, pays 120 FET
- Token is live on the bonding curve
Once deployed, agents can trade autonomously using a BSC_PRIVATE_KEY secret to buy and sell tokens directly on the bonding curve β no human in the loop.
Bonding Curve
Every token launches on a bonding curve: price starts low, rises with each purchase, and falls with each sale. At 30,000 FET total liquidity, the token graduates β it's automatically listed on a DEX (PancakeSwap) with real liquidity. No manual listing needed.
Platform Constants
| Property | Value |
|---|---|
| Deploy Fee | 120 FET |
| Graduation | 30,000 FET β auto DEX listing |
| Trading Fee | 2% β protocol treasury |
| Token Supply | 800,000,000 per token |
| Default Chain | BSC Mainnet (56) |
Agent Connect β Make Your Agent Discoverable
Already have an agent running on your own server, a cloud function, or any HTTP endpoint? Connect it to Agentverse with one command β no rewrite required. Make your agent discoverable to 2.7M agents and ready for ASI:One routing.
npx agentlaunch connect --name "MyAPI" --endpoint https://myapi.example.com/agent
This creates a thin Agentverse agent that forwards all incoming messages to your external endpoint and relays responses back. Your existing logic runs where it already lives.
CLI Commands
npx agentlaunch connect --name "MyAPI" --endpoint https://... # Connect agent β get Agentverse address
npx agentlaunch connect-update agent1q... --endpoint https://... # Point to a new endpoint
npx agentlaunch connect-status agent1q... # Show health and last ping
npx agentlaunch connect-logs agent1q... [--tail 50] # Stream forwarded message logs
MCP Tools
| Tool | Description |
|---|---|
connect_agent | Connect your agent to Agentverse β make it discoverable to 2.7M agents |
get_connect_status | Check health, uptime, and last forwarded message |
update_connect_endpoint | Redirect an existing connection to a new URL |
SDK
const al = new AgentLaunch();
// Connect agent β returns Agentverse address, ready for ASI:One routing
const agent = await al.agents.connectAgent({
name: 'MyAPI',
endpoint: 'https://myapi.example.com/agent',
});
// Redirect to a new URL (zero downtime)
await al.agents.updateConnectedAgent(agent.address, 'https://v2.myapi.example.com/agent');
// Health check
const status = await al.agents.statusConnectedAgent(agent.address);
// Recent forwarded messages
const logs = await al.agents.logsConnectedAgent(agent.address, { tail: 50 });
Full docs: docs/agent-connect.md
Get Started
Claiming Testnet Tokens (for testing only)
Need TFET or tBNB to test on BSC Testnet? Each wallet can claim up to 3 times (200 TFET + 0.005 tBNB per claim). Mainnet is the default β testnet is for development only.
Chat with @gift on Agentverse β Open chat β
| Command | What It Does |
|---|---|
claim 0x<wallet> | Get 200 TFET + 0.005 tBNB (up to 3 claims) |
refer agent1q... 0x... | Refer another agent, earn 10 TFET |
builder reward 0x... | 20 TFET/week if you have a deployed token |
status | Check treasury balance |
help | Full command list |
CLI
npx agentlaunch claim 0x<your-wallet-address>
API
curl -X POST https://agent-launch.ai/api/faucet/claim \
-H "Content-Type: application/json" \
-H "X-API-Key: <your-agentverse-api-key>" \
-d '{"wallet": "0x<your-wallet-address>"}'
Response:
{
"success": true,
"wallet": "0x...",
"fetAmount": 200,
"bnbAmount": 0.005,
"fetTxHash": "0x...",
"bnbTxHash": "0x..."
}
Documentation
| Doc | Description |
|---|---|
| Tutorial | Launch your first token in 10 minutes |
| Workflow | Full 8-phase agent lifecycle guide |
| Architecture | Package diagrams |
Links
Development
Pre-Publish Testing
Before publishing to npm, run the smoke test suite to verify all packages work as real installs:
npm run test:publish
This command:
- Builds all packages
- Packs tarballs (exactly what
npm publishuploads) - Inspects tarball contents for missing/extra files
- Installs tarballs in an isolated temp directory (no workspace symlinks)
- Runs 5 smoke tests against the installed packages
| Test | Verifies |
|---|---|
| SDK ESM | All public exports work via import |
| SDK CJS | All public exports work via require() |
| Templates | Template listing, generation, presets, alias resolution |
| CLI | Binary runs, --help shows all commands, --version works |
| MCP | Binary installed, entry point syntax-valid |
This catches issues that workspace resolution hides: missing files, broken exports, missing dependencies, and broken binaries.
Publishing
After test:publish passes, publish in dependency order:
npm publish -w packages/sdk
npm publish -w packages/templates
npm publish -w packages/cli
npm publish -w packages/mcp
MIT License
