Piper Agent Kit — MCP

Autonomous operator tools over the Piper Partner API.

npm: @piper-partner/mcp (bin: piper-mcp)

npm i -g @piper-partner/mcp
# or: npx -y @piper-partner/mcp

Minimum env

PIPER_PARTNER_KEY=piper_…
PIPER_BOUND_WALLET_PRIVATE_KEY=0x…   # wallet that requested the key (launch only)
PIPER_API_BASE=https://api.testsback.com/api/v1/partner
# optional
PIPER_AGENT_HOME=~/.piper-agent
PIPER_VAULT_PASS=…                  # encrypts trade wallets
PIPER_RPC_URL_9009=https://…
PIPER_AGENT_RUNTIME=local_mcp       # or cloud_chatbot

Cursor mcp.json

{
  "mcpServers": {
    "piper": {
      "command": "npx",
      "args": ["-y", "@piper-partner/mcp"],
      "env": {
        "PIPER_PARTNER_KEY": "piper_…",
        "PIPER_BOUND_WALLET_PRIVATE_KEY": "0x…",
        "PIPER_API_BASE": "https://api.testsback.com/api/v1/partner"
      }
    }
  }
}

First messages (agent MUST)

1. piper_bootstrap (reads playbook resource)
2. piper_onboard_questions → user answers once → piper_onboard_save → piper_risk_ack
3. piper_workflow_map + piper_dashboard_write
4. If buyOtherMemes: trade_wallet_create / import + fund
5. Steady: piper_monitor_tick → decide → piper_trade_execute / launch / piper_share_bundle

Wallets

| Role | Key | |------|-----| | Launch / partner binding | PIPER_BOUND_WALLET_PRIVATE_KEY | | Buys of other memes | Encrypted vault via trade_wallet_* |

Telegram (optional)

Not required. If the user wants push alerts/marketing and opts in, guide with piper_setup_guide id=telegram_ops_bot. Otherwise skip and keep operating (dashboard/ledger/inbox/chat).

# optional only
TELEGRAM_BOT_TOKEN=
TELEGRAM_CHAT_ID=
TELEGRAM_NOTIFY_ENABLED=true

Cloud chatbots

See agent/CLOUD_AUTONOMOUS.md. Same tools; secrets in vendor panel; heartbeat tick loop.

Resources

• piper://playbook
• piper://workflow-map

Share / Token Card

piper_share_card / piper_share_bundle return the Graduation Token Card PNG using server Agent Kit capabilities:

GET {ASSET_ORIGIN}/api/share/token/:address/card.png?chainId=…

Legacy social OG (…/og.png) is unchanged for crawlers. Card route validates address/chainId, rate-limits per IP, and only fetches logos from allowlisted HTTPS origins.

Agent Kit notices (live updates)

GET /api/v1/partner/health and GET /api/v1/partner/agent-kit publish capabilities + notices.
piper_bootstrap / piper_monitor_tick refresh them into agentKit so agents adopt URL/behavior changes without a human messenger.

Ops runbook (how to publish the next update):
docs/agent-kit/UPDATES.md