vibecoin-mcp
Drafts and deploys a coin from your repo to pump.fun's bonding curve on Solana, with local key management and fee recycling into an agent budget.
README
vibecoin-mcp
Launch your vibe coded app on Solana without leaving Claude Code. This MCP server drafts a coin from your repo, deploys it to pump.fun's bonding curve via the PumpPortal Local Transaction API, and recycles your creator fees into an agent budget — with keys that never leave your machine.
Site: https://vibecoin.fun · Projects: https://vibecoin.fun/projects
Install
Claude Code
claude mcp add vibecoin -- npx github:thetriggeredkid-spec/vibecoin-mcp
Manual (~/.claude.json or .mcp.json)
{
"mcpServers": {
"vibecoin": {
"command": "npx",
"args": ["github:thetriggeredkid-spec/vibecoin-mcp"]
}
}
}
From a clone
git clone https://github.com/thetriggeredkid-spec/vibecoin-mcp.git
cd vibecoin-mcp && npm install && npm run build
claude mcp add vibecoin -- node /absolute/path/to/vibecoin-mcp/dist/index.js
Restart Claude Code after adding it.
One-prompt launch
Open Claude Code in your project and say "launch this as a coin". The flow:
launchreads README.md, package.json and your git remote, then shows a preview: name, ticker, description, image, links, and the full cost breakdown.- You approve (or tweak any field — everything is overridable).
- A wallet is auto-created for this project if none exists. Its encryption password is generated and stored in your macOS Keychain (or a
0600key file elsewhere), so no interactive password step ever blocks the launch — and the password never appears in the chat. - Metadata (JSON + image) is uploaded, PumpPortal builds the unsigned create transaction, it's signed locally with the mint + creator keys, and submitted to your RPC.
- The coin is live on pump.fun; the launch is recorded locally and registered on vibecoin.fun/projects.
Nothing is ever sent without an explicit preview → approve → confirm: true cycle. That applies to launches, transfers, fee claims, swaps and locks alike.
Tools
| Tool | What it does |
|---|---|
wallet |
Create the project's encrypted wallet, check SOL/USDC balances, transfer SOL |
launch |
Draft a coin from the repo and deploy it to pump.fun's bonding curve |
my-coins |
List every coin launched from this machine with live market data |
collect-fees |
Claim accrued pump.fun creator fees (all coins at once) |
fund-agent |
Collect fees → swap SOL→USDC via Jupiter → hold the budget in the agent's wallet |
lock |
Lock a % of your own tokens via Streamflow; returns a shareable proof link |
info |
Fee table, config paths, wallet list, links |
Token metadata field guide
What each field does, where it ends up, and who fills it. The launch preview shows this mapping before anything is sent; your agent can override any field via the tool parameters of the same name.
| Field | Ends up in | Function & limits | Default source |
|---|---|---|---|
name |
on-chain + metadata JSON | Display name everywhere. Hard on-chain limit 32 chars. | README # Title → package.json name → directory name |
symbol |
on-chain + metadata JSON | The $TICKER. Hard on-chain limit 10 chars; 3–8 uppercase is the convention. | Derived from name (initials for 3+ words, blended otherwise) |
description |
metadata JSON | Body text on the pump.fun coin page and aggregators. Keep ≤ ~500 chars. | First real README paragraph → package.json description |
image (image_path param) |
metadata JSON | Coin avatar. Square png/jpg/gif/webp, ≤ 1.5 MB. | logo.png/icon.png/public/logo.png etc., else a bundled placeholder |
website |
metadata JSON | Link box on the coin page — point it at the live app. | package.json homepage |
twitter |
metadata JSON | Optional social link on the coin page. | omitted unless provided |
telegram |
metadata JSON | Optional social link on the coin page. | omitted unless provided |
github |
vibecoin registry + appended to description | pump.fun metadata has no native repo field, so the repo URL lives in the vibecoin.fun registry (and /projects), and is appended to the description for visibility on pump.fun itself. | git remote.origin.url, normalized |
showName |
metadata JSON | Legacy pump.fun display flag; always "true" for compatibility. |
fixed |
createdOn |
metadata JSON | Provenance stamp; coins launched here carry https://vibecoin.fun. |
fixed |
dev_buy_sol |
create transaction | Optional initial buy at the very bottom of the curve (your creator bag). PumpPortal takes 0.5% of it. | 0 |
Fees (verified from official docs, July 2026)
- Creating a coin is free; ~0.025 SOL of network cost puts it on-chain (~0.04 SOL recommended balance incl. buffer).
- Bonding-curve trades cost 1.25%: 0.30% to you, 0.95% to pump.fun.
- After graduation (~85 SOL raised → PumpSwap, LP burned) your share is tiered by market cap: up to 0.95%, floor 0.05% above ~$20M.
- PumpPortal adds 0.5% on trades routed through its API (dev buys included; creation itself is not charged).
fund-agentswaps via Jupiter (2 bps on SOL→USDC) and keeps the USDC in your wallet. It does not auto-pay any provider — Anthropic/OpenAI bill fiat cards only, and OpenRouter crypto top-ups are a manual checkout on their site.lockuses Streamflow: ~0.09–0.16 SOL + 0.19–0.5% of the locked tokens (their on-chain fee oracle sets the exact value).
Security model
- Keypairs are generated locally and stored encrypted (scrypt N=2^15 + AES-256-GCM) under
~/.vibecoin/wallets/with0600permissions. - The encryption password is resolved in order:
VIBECOIN_WALLET_PASSWORDenv → explicitpasswordparam → auto-generated secret in the macOS Keychain (servicevibecoin) or~/.vibecoin/keys/<name>.key(0600). - Auto mode protects the wallet file at rest (a stolen
wallets/*.jsonalone is useless). It does not protect against an attacker with full control of your logged-in user account — setVIBECOIN_WALLET_PASSWORDyourself and delete the stored secret if you want password-only custody. - Transactions are built by PumpPortal/Jupiter as unsigned payloads, signed locally, and submitted to the RPC you configure. Private keys are never transmitted, logged, or included in tool output.
- Every value-moving action requires an explicit user-approved
confirm: truesecond call.dry_runbuilds and simulates without sending. - One fresh wallet per project by default — launches are pseudonymous until you link them.
Environment variables
| Variable | Default | Purpose |
|---|---|---|
SOLANA_RPC_URL |
https://api.mainnet-beta.solana.com |
RPC for submission/balances. Use a paid endpoint (Helius, Triton…) for reliability. |
VIBECOIN_HOME |
~/.vibecoin |
Where wallets/launches live. |
VIBECOIN_WALLET_PASSWORD |
— | Bring-your-own wallet password (skips the stored secret). |
VIBECOIN_DRY_RUN |
— | 1 = every action builds + simulates but never sends. |
PINATA_JWT |
— | Pin metadata to IPFS via your own Pinata account instead of vibecoin.fun's hosted endpoint. |
JUP_API_KEY |
— | Jupiter API key (keyless works at 0.5 req/s). |
VIBECOIN_METADATA_URL |
https://vibecoin.fun/api/metadata |
Hosted metadata endpoint. |
VIBECOIN_REGISTRY_URL |
https://vibecoin.fun/api/registry |
Launch registry endpoint. |
VIBECOIN_NO_KEYCHAIN |
— | 1 = skip macOS Keychain, use key files. |
Notes
- pump.fun and PumpPortal have no devnet —
dry_run(build + mainnet simulation, no send) is the safe rehearsal. - pump.fun's terms restrict commercial transacting on behalf of others; vibecoin is a local tool — you sign for yourself, we never custody anything.
- Not financial advice; launching a token is not an investment contract with your users. Ship something real.
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。
mcp-server-qdrant
这个仓库展示了如何为向量搜索引擎 Qdrant 创建一个 MCP (Managed Control Plane) 服务器的示例。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。