1ly

The 1ly MCP server enables AI agents to interact with the 1ly.store API marketplace. It lets agents search for APIs, purchase access, and pay with crypto using the x402 protocol, and it also supports sellers who want to create a store, list paid endpoints, and accept payments. In addition, the server can launch and manage tokens on Bags.fm, enabling token trading and fee sharing. The system supports Solana mainnet and Base mainnet, with USDC and the native 1LY token as payment options on Solana. To use paid features, you’ll need a wallet (Solana or EVM) or a Coinbase Agentic Wallet, and you can run the server with DCP for secure signing or with HTTP transport for cloud deployments. The Tools Reference section exposes buyer-facing actions like searching the marketplace or purchasing paid API access, and it also supports listing, pricing, reviews, and usage data for paid resources.

Once running, you can access the MCP server via the command shown in the Quick Start. For a local setup, ensure your wallet path variables are correctly set (absolute paths are required in Claude/Cursor integrations). The server exposes the 1ly_search tool for discovering APIs, and paid calls require a wallet. You can also run the server in HTTP mode for cloud hosting and set environment variables to tailor budgets, networks, and wallet sources to your needs.

Below is a succinct workflow example: first, start the MCP server with your preferred wallet setup (Solana, EVM, or Coinbase Agentic Wallet). Then, use 1ly_search to discover APIs, inspect pricing and usage, and finally purchase access or call paid endpoints. If you’re selling, create a store and list your paid links so agents can discover and buy access automatically.

Prerequisites:

• Node.js (recommended: LTS, v14+ or newer) and npm/yarn installed
• Basic familiarity with shell/terminal
• Optional: DCP tooling for secure signing (dcp) and a local wallet setup

1. Install Node.js and npm

   • Download from https://nodejs.org or use your OS package manager

2. Run the MCP server with npx (no local install required)

   • Using a Solana wallet: ONELY_WALLET_SOLANA_KEY="~/.1ly/wallets/solana.json" npx @1ly/mcp-server

   • Using an EVM wallet: ONELY_WALLET_EVM_KEY="~/.1ly/wallets/evm.key" npx @1ly/mcp-server

   • Using both wallets: ONELY_WALLET_SOLANA_KEY="/.1ly/wallets/solana.json" ONELY_WALLET_EVM_KEY="/.1ly/wallets/evm.key" npx @1ly/mcp-server

   • Using Coinbase Agentic Wallet (Base only): ONELY_WALLET_PROVIDER="coinbase" npx @1ly/mcp-server

3. Optional: Run DCP locally for secure signing

   • Start DCP locally and then run the MCP server: dcp init npx @dcprotocol/server npx @1ly/mcp-server

4. Verify HTTP mode (cloud-ready)

   • Run with HTTP transport: MCP_TRANSPORT=http npx @1ly/mcp-server MCP_TRANSPORT=http MCP_HTTP_HOST=0.0.0.0 MCP_HTTP_PORT=3000 npx @1ly/mcp-server

5. Validate a quick test

   • Example test call assuming wallet is configured: ONELY_WALLET_SOLANA_KEY="~/.1ly/wallets/solana.json" npx @1ly/mcp-server --self-test

Tips and notes:

• Wallets are required only for paid API calls. Free search and details can be performed without a wallet.
• Supported networks: Solana mainnet and Base mainnet. Payment currencies include USDC and 1LY (Solana only).
• Environment variables control budgets per call and per day (ONELY_BUDGET_PER_CALL, ONELY_BUDGET_DAILY) and wallet sources (ONELY_WALLET_SOLANA_KEY, ONELY_WALLET_EVM_KEY, ONELY_WALLET_PROVIDER).
• The MCP can run in multiple transports (stdio by default, HTTP for cloud hosting). Use MCP_TRANSPORT to switch modes.
• If you plan to expose the server publicly, consider enabling proper wallet handling, secure signing with DCP, and restricting endpoints if needed.
• For Claude Desktop and Cursor integrations, remember that absolute paths are required in their config files; tilde (~) expansion is not supported.