Enables AI agents to hire KOL crews and launch tokens on Pump.fun, Bags.fm, Zora, and Clanker with non-custodial, unsigned transactions.
Also known as fxams/crew, crew, crewpay-mcp
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.2.14
- Last commit
- Nov 11, 2026
- License
- MIT
What is CrewPay MCP?
CrewPay enables AI agents to hire KOL crews and launch tokens on Pump.fun, Bags.fm, Zora, and Clanker with non-custodial, unsigned transactions.
Summary generated from the project's README
About CrewPay MCP server
CrewPay provides a specialized infrastructure for AI agents to manage token launches and marketing coordination. The server enables agents to hire KOL crews and launch tokens on platforms including Pump.fun, Bags.fm, Zora, and Clanker on the Base network. It operates using a non-custodial model where the server never holds the launcher key, instead utilizing unsigned transactions that require a human approval link or a final signing step.
Developers can deploy this via a local MCP environment using the crewpay-mcp package. Setup requires a CREWPAY_API_KEY and a dedicated low-SOL CREW_LAUNCHER_KEY stored locally. The system manages on-chain creator fee-shares, typically splitting revenue between the KOL crew, the launching agent, and a treasury. It also supports x402 USDC payments on Base and Solana for specific actions like autohiring or launching. This tool is designed for crypto agents that need to automate narrative-matched marketing and token deployment while maintaining security through dry-run capabilities.
What you can do with it
- 1Automated KOL recruitmentAn AI agent can automatically find and hire a marketing crew that matches a specific token narrative.
- 2Secure token deploymentAgents can prepare token launches on multiple platforms using unsigned transactions to ensure non-custodial security.
Written from the project's README. Every use case is checked against a quote from it.
How to install CrewPay MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall CrewPay MCP in Claude Code
$ claude mcp add --env 'CREW_AGENT_API_KEY=<YOUR_CREW_AGENT_API_KEY>' --env 'CREW_LAUNCHER_KEY=<YOUR_CREW_LAUNCHER_KEY>' --env 'X402_EVM_PRIVATE_KEY=<YOUR_X402_EVM_PRIVATE_KEY>' crew -- npx -y crewpay-mcpInstall CrewPay MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"crew": {
"command": "npx",
"args": [
"-y",
"crewpay-mcp"
],
"env": {
"CREW_AGENT_API_KEY": "<YOUR_CREW_AGENT_API_KEY>",
"CREW_LAUNCHER_KEY": "<YOUR_CREW_LAUNCHER_KEY>",
"X402_EVM_PRIVATE_KEY": "<YOUR_X402_EVM_PRIVATE_KEY>"
}
}
}
}Install CrewPay MCP in VS Code
.vscode/mcp.json
{
"servers": {
"crew": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"crewpay-mcp"
],
"env": {
"CREW_AGENT_API_KEY": "<YOUR_CREW_AGENT_API_KEY>",
"CREW_LAUNCHER_KEY": "<YOUR_CREW_LAUNCHER_KEY>",
"X402_EVM_PRIVATE_KEY": "<YOUR_X402_EVM_PRIVATE_KEY>"
}
}
}
}Install CrewPay MCP in VS Code CLI
$ code --add-mcp '{"name":"crew","type":"stdio","command":"npx","args":["-y","crewpay-mcp"],"env":{"CREW_AGENT_API_KEY":"<YOUR_CREW_AGENT_API_KEY>","CREW_LAUNCHER_KEY":"<YOUR_CREW_LAUNCHER_KEY>","X402_EVM_PRIVATE_KEY":"<YOUR_X402_EVM_PRIVATE_KEY>"}}'Install CrewPay MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"crew": {
"command": "npx",
"args": [
"-y",
"crewpay-mcp"
],
"env": {
"CREW_AGENT_API_KEY": "<YOUR_CREW_AGENT_API_KEY>",
"CREW_LAUNCHER_KEY": "<YOUR_CREW_LAUNCHER_KEY>",
"X402_EVM_PRIVATE_KEY": "<YOUR_X402_EVM_PRIVATE_KEY>"
}
}
}
}Install CrewPay MCP in Codex
$ codex mcp add crew --env 'CREW_AGENT_API_KEY=<YOUR_CREW_AGENT_API_KEY>' --env 'CREW_LAUNCHER_KEY=<YOUR_CREW_LAUNCHER_KEY>' --env 'X402_EVM_PRIVATE_KEY=<YOUR_X402_EVM_PRIVATE_KEY>' -- npx -y crewpay-mcpInstall CrewPay MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.crew] command = "npx" args = ["-y", "crewpay-mcp"] [mcp_servers.crew.env] CREW_AGENT_API_KEY = "<YOUR_CREW_AGENT_API_KEY>" CREW_LAUNCHER_KEY = "<YOUR_CREW_LAUNCHER_KEY>" X402_EVM_PRIVATE_KEY = "<YOUR_X402_EVM_PRIVATE_KEY>"
Install CrewPay MCP in Gemini CLI
$ gemini mcp add -s user -e 'CREW_AGENT_API_KEY=<YOUR_CREW_AGENT_API_KEY>' -e 'CREW_LAUNCHER_KEY=<YOUR_CREW_LAUNCHER_KEY>' -e 'X402_EVM_PRIVATE_KEY=<YOUR_X402_EVM_PRIVATE_KEY>' crew npx -- -y crewpay-mcpInstall CrewPay MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"crew": {
"command": "npx",
"args": [
"-y",
"crewpay-mcp"
],
"env": {
"CREW_AGENT_API_KEY": "<YOUR_CREW_AGENT_API_KEY>",
"CREW_LAUNCHER_KEY": "<YOUR_CREW_LAUNCHER_KEY>",
"X402_EVM_PRIVATE_KEY": "<YOUR_X402_EVM_PRIVATE_KEY>"
}
}
}
}Configuration
CREW_AGENT_API_KEYRequiredSecretcrew_ak_… from crew_claim_key / POST /api/agent/keys/claim, or operator key
CREW_LAUNCHER_KEYSecretDedicated low-SOL burner Solana secret for launch/wire/lock (local env only — never a tool arg). Not used by hosted remote.
X402_EVM_PRIVATE_KEYSecretOptional hex private key for Base USDC x402 pay-per-call (alternative to CREW_AGENT_API_KEY). Local env only — never a tool arg. Not used by hosted remote.
CREWPAY_REFERRAL_CODEOptional KOL referral code used by crew_claim_key when referral_code arg omitted
CREW_API_URLAPI base URL (default https://api.crewpay.dev)
| Name | Description | |
|---|---|---|
| CREW_AGENT_API_KEY | crew_ak_… from crew_claim_key / POST /api/agent/keys/claim, or operator key | RequiredSecret |
| CREW_LAUNCHER_KEY | Dedicated low-SOL burner Solana secret for launch/wire/lock (local env only — never a tool arg). Not used by hosted remote. | Secret |
| X402_EVM_PRIVATE_KEY | Optional hex private key for Base USDC x402 pay-per-call (alternative to CREW_AGENT_API_KEY). Local env only — never a tool arg. Not used by hosted remote. | Secret |
| CREWPAY_REFERRAL_CODE | Optional KOL referral code used by crew_claim_key when referral_code arg omitted | |
| CREW_API_URL | API base URL (default https://api.crewpay.dev) |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSPass
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubCREW / CrewPay
AI agents hire KOLs. Humans get paid. Launch coins on Pump.fun, Bags.fm, Zora, and Clanker (Base) with on-chain creator fee-shares (60% KOL crew / 15% launching agent / 25% treasury, or 60/15/5/20 when the agent claimed a key with a KOL referral code).
Live: crewpay.dev · API api.crewpay.dev · MCP mcp.crewpay.dev/mcp
Features
- Auto-hire a KOL crew (narrative match; prefer registered / opt-in KOLs)
- Non-custodial unsigned launches — CrewPay never holds the launcher key
- Dry-run plus a human approval link (
dryRunId+approvalUrl) - KOL sign-up / opt-in at
/registerand referral codes (/r/<code>). KOLs add a Solana payout wallet for Pump.fun / Bags.fm crews and an optional Base (0x) wallet on the desk for Clanker / Zora crews and Base referral payouts (signed with the Solana desk wallet). - Per-coin pages (
/coin/{mint}) with a milestone timeline - Live coins (home) and All coins with live market data
- Proof tape (including paid content-job receipts)
- Jobs — paid content briefs (thread / meme / post). Agent picks the winner. Test/devnet only.
- Agents earn — launching agents get 15% of creator fees onchain (fees follow volume and can be zero)
- MCP:
crewpay-mcp@1.2.14on npm · hostedmcp.crewpay.dev/mcp - REST API +
llms.txt - OpenClaw skill:
openclaw skills install @fxams/crewpay - Official MCP Registry (
io.github.fxams/crewpay-mcp) and Glama - x402 USDC on Base and Solana (when
X402_SOLANA_PAY_TOis set) — Autohire $0.02, launch family $0.10 — listed on x402scan - Virtuals ACP offerings on Base (
8453): Autohire $0.25, launch with crew $1.00 - Jobs + escrow: testnet only (
JOBS_ENABLED; production templates API is off). Paid content jobs reuse the same rails — no new escrow program, no mainnet.
For AI / crypto agents
GET https://api.crewpay.dev/api/agent
GET https://crewpay.dev/llms.txt
GET https://mcp.crewpay.dev/.well-known/mcp.json
Safe flow: discover → list_kols / autohire → build_unsigned (mintPubkey required for Pump) → signAllTransactions → submit_signed. Fees lock at launch. crew_wire_fees is repair-only. Custodial alternate: dry-run → launch. Prefer MCP:
npx -y crewpay-mcp@1.2.14
Env: CREWPAY_API_KEY (or CREW_AGENT_API_KEY) + dedicated low-SOL CREW_LAUNCHER_KEY in local MCP env — never as tool arguments or chat paste. Hosted: https://mcp.crewpay.dev/mcp
OpenClaw / ClawHub skill: skills/crewpay — openclaw skills install @fxams/crewpay — hire KOLs, dry-run first, open approvalUrl, then launch with dryRunId. Fee split 60/15/25 or 60/15/5/20 with a KOL referral.
Legacy alias: skills/crewpay-crypto-agent
Discovery runbook: DISCOVERY.md · Framework plugins: packages/
Publish to ClawHub (maintainers)
npm i -g clawhub
clawhub login # GitHub device login — you do this interactively
clawhub skill publish ./skills/crewpay \
--slug crewpay \
--name "CrewPay" \
--version 1.1.6 \
--changelog "Venues Pump.fun / Bags / Zora / Clanker; x402 Base + Solana" \
--categories integrations,finance,agents \
--topics "solana,pump-fun,kol,fee-share,mcp" \
--dry-run
# When dry-run looks good, drop --dry-run to publish.
Official MCP Registry
See docs/mcp-registry-publish.md. Live name: io.github.fxams/crewpay-mcp (crewpay-mcp@1.2.14).
x402
Pay-per-call x402 v2 on Base mainnet USDC (eip155:8453) and optional Solana mainnet USDC (solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp when X402_SOLANA_PAY_TO is set). Alternative to x-crew-api-key. Hosted MCP is not an x402 resource server.
Discovery
Listed on x402scan.
Paid routes (live prices)
| Method | Path | Price |
|---|---|---|
| POST | /api/agent/autohire |
$0.02 |
| POST | /api/agent/launch/unsigned |
$0.10 |
| POST | /api/agent/launch/submit |
$0.10 |
| POST | /api/agent/launch/dry-run |
$0.10 |
| POST | /api/agent/launch |
$0.10 |
Desk (humans)
cd agent/crew
npm install
npm run dev
See agent/crew/DEPLOY.md · agent/crew/PRODUCT.md.
Packages
| Path | Role |
|---|---|
agent/crew |
Vite desk UI |
agent/crew-api |
Agent API + proof |
agent/crew-mcp |
MCP server (crewpay-mcp) |
services/acp-provider |
Virtuals ACP v2 provider worker (no-op unless ACP_ENABLED=1) |
Virtuals ACP (agents hire CrewPay)
Live: GET https://api.crewpay.dev/api/platforms reports acp.enabled and x402.enabled. Production ACP is Base mainnet (chainId 8453). Listener: set ACP_INPROCESS=1 on crewpay-api or run services/acp-provider. Paying agent wallet = identity. Fee map unchanged. Launch jobs stay non-custodial (unsigned txs + crew_submit_signed). Hire UI: app.virtuals.io/acp.
This repo does not register an ACP agent, generate keys, or move funds.
Offerings
[
{
"name": "crewpay_autohire_kol_crew",
"description": "Hire a KOL crew for an existing token via CrewPay Autohire. Deliverable is crew list JSON.",
"priceUsd": 0.25,
"requirements": { "required": ["mint", "platform", "budget"] }
},
{
"name": "crewpay_launch_with_crew",
"description": "Unsigned launch txs (crew_build_unsigned) plus crew_submit_signed instructions. Non-custodial.",
"priceUsd": 1.00,
"requirements": { "required": ["name", "ticker"] }
}
]
Operator setup
- Register a provider on app.virtuals.io/acp/new.
- Signers → + Add Signer. Put the Privy P-256 authorization key in
ACP_SIGNER_KEY, the wallet id inACP_WALLET_ID, and the 0x agent wallet inACP_WALLET_ADDRESS(never logs, never commit). The signer is not a 32-byte hex key and does not derive the wallet. - Add the two offerings (full JSON in
services/acp-provider/README.md). ACP_ENABLED=1ACP_CHAIN_ID=8453and eitherACP_INPROCESS=1on crewpay-api, ornpm start --prefix services/acp-provider.
CrewPay MCP questions
How do I add CrewPay MCP to Claude Code?
Run claude mcp add --env 'CREW_AGENT_API_KEY=<YOUR_CREW_AGENT_API_KEY>' --env 'CREW_LAUNCHER_KEY=<YOUR_CREW_LAUNCHER_KEY>' --env 'X402_EVM_PRIVATE_KEY=<YOUR_X402_EVM_PRIVATE_KEY>' crew -- npx -y crewpay-mcp in your terminal. Add --scope user to make it available in every project.
How do I add CrewPay MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How does CrewPay handle token launches?
It uses non-custodial unsigned launches where the CrewPay service never holds the launcher's private key.
Is there a way to test the launch process before committing?
Yes, the server supports a dry-run mode that provides a dryRunId and an approvalUrl for human verification.