Mcp Server
Wire your coding agent into 1ly.store to buy paid APIs, sell endpoints, and run Bags.fm token launch and trade flows with USDC and $1LY.
Overview
io.github.1lystore/mcp-server is a Build-phase MCP server that lets agents buy and sell APIs on 1ly.store and launch or trade Bags.fm tokens using configured Solana and EVM wallets.
What is this MCP server?
- stdio npm package @1ly/mcp-server (v0.1.7) for Claude Desktop and other MCP hosts
- Solana keypair and Base EVM key env vars for paid calls, launch, trade, and claim on Bags.fm
- Seller flow: 1ly_create_store persists ONELY_API_KEY for links, stats, withdrawals, and profile tools
- Buy and sell API access on 1ly.store with USDC and $1LY settlement
- Absolute wallet paths required because Claude Desktop does not expand tilde paths
- Published server version 0.1.7 on npm as @1ly/mcp-server
- Stdio transport with three documented secret env vars for wallets and optional seller API key
Community signal: 3 GitHub stars.
What problem does it solve?
You want your agent to call paid APIs or run token launch and trade steps without leaving the IDE, but those flows need wallets, seller keys, and a stable MCP bridge.
Who is it for?
Solo builders monetizing API products on 1ly.store or automating Bags.fm token workflows from Claude Code, Cursor, or Codex with USDC and $1LY.
Skip if: Teams that want traditional card billing only, no crypto wallets, or no interest in API marketplaces and token tooling.
What do I get? / Deliverables
After you register the stdio server and wallet env vars, your agent can invoke 1ly consumer and seller tools and Bags.fm actions as structured MCP calls.
- MCP tools for buying and selling APIs on 1ly.store
- Wallet-backed Bags.fm launch, trade, and claim operations from the agent
- Locally persisted seller API key after store creation for management tools
Recommended MCP Servers
Journey fit
Monetized API and token tooling lands when you are wiring external services into the product, not during idea or launch SEO work. Wallet-backed MCP tools are integration work: register the server, fund keys, and call seller or consumer tools from Claude Code or Cursor.
How it compares
Paid API and token marketplace MCP integration, not a reusable agent skill or local code-review workflow.
Common Questions / FAQ
Who is io.github.1lystore/mcp-server for?
It is for indie builders and API sellers who use MCP-capable agents and need 1ly.store commerce plus Bags.fm token tools with wallet-backed payments.
When should I use io.github.1lystore/mcp-server?
Use it during Build when you are integrating external paid APIs or seller dashboards and want launch, trade, and claim actions callable from your agent.
How do I add io.github.1lystore/mcp-server to my agent?
Install @1ly/mcp-server from npm, add a stdio MCP entry in your client config, set ONELY_WALLET_SOLANA_KEY and ONELY_WALLET_EVM_KEY to absolute paths or inline secrets, and run 1ly_create_store if you need seller tools.