Log inSubmit server
CrewPay logo

CrewPay

by CREW

Solana MCP server for hiring KOL crews and preparing non-custodial Pump.fun launches with creator fee shares.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install CrewPay

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "crew-crewpay": {
      "command": "npx",
      "args": [
        "-y",
        "crewpay-mcp@1.2.8"
      ],
      "env": {
        "CREWPAY_API_KEY": "YOUR_VALUE_HERE",
        "CREW_AGENT_API_KEY": "YOUR_VALUE_HERE",
        "CREW_LAUNCHER_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 15 tools correctly (Today).

Overview

CREW / CrewPay MCP server connects AI agents to CrewPay for KOL autohire and Solana Pump.fun token launches. It supports a staged flow of discovery, hiring, dry-run approval, and launch, with unsigned transactions submitted after human confirmation. Use it when an agent needs to arrange fee-sharing crews or prepare a non-custodial token launch. The hosted MCP endpoint is available at mcp.crewpay.dev/mcp, or the server can run locally through the crewpay-mcp package.

Use cases

  • Hire KOL crews for existing Solana tokens
  • Prepare Pump.fun launches with creator fee shares
  • Run a dry-run approval flow before signing
  • Build unsigned launch transactions for human signing

Key features

  • KOL autohire workflow
  • Pump.fun launch preparation
  • Unsigned transaction building
  • Signed transaction submission
  • Referral-based fee splits
  • Hosted and local MCP access

Tools15

What CrewPay lets your agent do. Expand a tool for its parameters.

Verified live~3.7k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

5/5 checks healthy over the last 17d

What it can do

From the 15 tools this server returned when we ran it; 15 declare their own safety hints.

Can delete or modify data · 5Handles credentials · 2Makes network requests · 15Read-only tools · 10
Network at startup3 connections
Files written at startupNone
Install scriptsprepare
npm provenanceNot published
Package age26 days
Maintainers1

Observed 2026-11-04 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · crewpay-mcp@1.2.8 (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads3.8kPackage downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed15Callable tools this server registers over MCP.

How CrewPay works

What CREW / CrewPay does

CREW / CrewPay coordinates AI-agent requests to hire KOL crews and launch Solana Pump.fun coins with creator fee shares. The default split is 60% for the KOL crew, 15% for the launching agent, and 25% for the treasury. When an agent has claimed a key using a KOL referral code, the split becomes 60/15/5/20.

The service is intended for a controlled workflow rather than an immediate launch. An agent can discover available information, autohire a crew, perform a dry run, obtain human approval, and then proceed with the launch.

How it works

The CREW / CrewPay MCP server can run locally with the published crewpay-mcp package or through the hosted endpoint at https://mcp.crewpay.dev/mcp. The associated API is available at https://api.crewpay.dev, with agent discovery information exposed through /api/agent. The project also publishes MCP discovery metadata at /.well-known/mcp.json on the MCP host.

Launches remain non-custodial. The launch process builds unsigned transactions, and the signed result is submitted through crew_submit_signed. The repository describes crew_build_unsigned as the operation for preparing those transactions. A human should review the dry-run result and approval URL before the launch is continued with its dryRunId.

Setup and configuration

For a local MCP process, install or run the package with:

Terminal
npx -y crewpay-mcp@1.2.8

Configure the API credential with CREWPAY_API_KEY, or use the documented alias CREW_AGENT_API_KEY. Set CREW_LAUNCHER_KEY to a dedicated wallet with low SOL for launching. These values belong in the local MCP environment; they should not be passed as tool arguments or pasted into chat.

A hosted deployment is available, so local installation is not required when the client can connect to the streamable MCP endpoint.

Tools and capabilities

The documented workflow supports:

  • Discovering CrewPay and agent-related information.
  • Hiring a KOL crew for an existing token through the autohire flow.
  • Running a launch dry run before approval.
  • Building unsigned launch transactions with crew_build_unsigned.
  • Submitting signed transactions with crew_submit_signed.
  • Launching Pump.fun coins with the documented creator fee-share arrangements.

The related autohire offering requires a mint, platform, and budget. The launch offering requires a name and ticker. The repository also describes a CrewPay OpenClaw skill for hiring, dry runs, approval-URL handling, and launch continuation.

Limitations and notes

CREW / CrewPay does not custody the launch transaction flow: agents or operators must handle signing before submission. The launcher key must be kept in the MCP environment and treated as sensitive.

Virtuals ACP and x402 support are disabled unless their respective environment settings are enabled. ACP is otherwise a no-op, and this repository does not register an ACP agent, generate keys, or move funds. ACP launch jobs remain non-custodial and use unsigned transactions.

The fee split depends on whether a qualifying KOL referral code was used, so integrations should not assume every launch uses the default 60/15/25 allocation.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about CrewPay

CREW / CrewPay is an MCP server that connects AI agents to CrewPay’s KOL autohire and Solana Pump.fun launch workflows. Its main tools support discovery, crew hiring, dry runs, unsigned transaction building with crew_build_unsigned, and signed submission with crew_submit_signed. Launches use documented creator fee-share splits and remain non-custodial.

Run `npx -y crewpay-mcp@1.2.8` to start the local MCP package. Set the API key and dedicated launcher key in the local MCP environment, or connect directly to the hosted endpoint at `https://mcp.crewpay.dev/mcp`.

Set `CREWPAY_API_KEY` or its documented alias `CREW_AGENT_API_KEY`, together with `CREW_LAUNCHER_KEY`. Keep these values in the local MCP environment and do not provide them as tool arguments or paste them into chat.

Yes. The launch flow builds unsigned transactions with `crew_build_unsigned`, then uses `crew_submit_signed` after the transaction has been signed. The documented workflow recommends a dry run and human approval before launch.

No. The available workflow covers KOL autohire, fee-share configuration, dry runs, and non-custodial launch transactions.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG Preview CrewPay AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/crew-crewpay?style=directory)](https://allmcps.com/mcp/crew-crewpay)
HTML Embed
<a href="https://allmcps.com/mcp/crew-crewpay"><img src="https://allmcps.com/api/badge/crew-crewpay?style=directory" alt=" CrewPay on AllMCPs" /></a>