home / mcp / 1ly mcp server

1ly MCP Server

Enables AI agents to discover, pay for, and sell APIs using crypto across Solana and Base networks.

Installation
Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "1lystore-1ly-mcp-server": {
      "command": "npx",
      "args": [
        "@1ly/mcp-server"
      ],
      "env": {
        "ONELY_API_KEY": "<ONELY_API_KEY>",
        "ONELY_NETWORK": "solana",
        "ONELY_API_BASE": "https://1ly.store",
        "ONELY_BUDGET_DAILY": "50.00",
        "ONELY_SOLANA_DRY_RUN": "<ONELY_SOLANA_DRY_RUN>",
        "ONELY_SOLANA_RPC_URL": "https://api.mainnet-beta.solana.com",
        "ONELY_WALLET_EVM_KEY": "<ONELY_WALLET_EVM_KEY>",
        "ONELY_BUDGET_PER_CALL": "1.00",
        "ONELY_WALLET_PROVIDER": "coinbase",
        "ONELY_BUDGET_STATE_FILE": "~/.1ly-mcp-budget.json",
        "ONELY_WALLET_SOLANA_KEY": "~/.1ly/wallets/solana.json"
      }
    }
  }
}

You can run and use the MCP server to let AI agents search, discover, and pay for APIs or resources with automated crypto payments. It supports creating stores, listing paid links, and launching tokens, enabling seamless commerce between agents and API providers across Solana and Base networks.

How to use

This MCP server is designed to be used with an MCP client or client-like automation. You can run it locally with a wallet, or use a wallet provider for Base. The server enables three core flows: (1) pay for and call paid APIs automatically, (2) create and manage a store of paid links, and (3) launch and manage tokens on Bags.fm and claim fee shares.

How to install

Prerequisites: you need Node.js and npm installed on your machine. You will run the MCP server using a local npx command so ensure you have network access and a compatible shell.

Choose a wallet integration method and then install and run the MCP server using one of the following configurations.

# Option A: Raw Solana or Base wallet (default) - Solana wallet path and/or Base/EVM wallet path
ONELY_WALLET_SOLANA_KEY="~/.1ly/wallets/solana.json" npx @1ly/mcp-server

# OR Base/EVM wallet
ONELY_WALLET_EVM_KEY="~/.1ly/wallets/evm.key" npx @1ly/mcp-server

# OR both wallets
ONELY_WALLET_SOLANA_KEY="~/.1ly/wallets/solana.json" \
ONELY_WALLET_EVM_KEY="~/.1ly/wallets/evm.key" \
npx @1ly/mcp-server

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

> If you use Agentic Wallet, do not pass raw private keys. Ensure the Coinbase Agentic Wallet app is running and authenticated.

Additional configuration and startup checks

After starting, you can verify your setup with a self-test to ensure the server launches correctly and can process paid calls if you have wallet access.

ONELY_WALLET_SOLANA_KEY="~/.1ly/wallets/solana.json" npx @1ly/mcp-server --self-test

# If you are using the Coinbase Agentic Wallet, start with the wallet Provider option and confirm the agent is running.

Configuration

You can customize several environment variables to control budgets, networks, and API access. The following variables are supported in MCP client configurations.

- ONELY_WALLET_SOLANA_KEY: Path to Solana keypair JSON file, or inline JSON array - ONELY_WALLET_EVM_KEY: Path to EVM private key file, or inline hex key (with or without 0x) - ONELY_API_KEY: API key for seller tools, auto-loaded after creating a store - ONELY_BUDGET_PER_CALL: Max USD per API call (default: 1.00) - ONELY_BUDGET_DAILY: Daily USD spending limit (default: 50.00) - ONELY_BUDGET_STATE_FILE: Path to local budget state file (default: ~/.1ly-mcp-budget.json) - ONELY_NETWORK: Preferred network: solana or base (default: solana) - ONELY_SOLANA_RPC_URL: Solana RPC URL (default: https://api.mainnet-beta.solana.com) - ONELY_API_BASE: API base URL (default: https://1ly.store) - ONELY_WALLET_PROVIDER: raw (default) or coinbase (Agentic Wallet, Base-only) - ONELY_SOLANA_DRY_RUN: Set to 1 to simulate Solana transactions without broadcasting *A wallet is required only for paid calls. For free search/details you can run without a wallet.* Use one of: ONELY_WALLET_SOLANA_KEY, ONELY_WALLET_EVM_KEY, or ONELY_WALLET_PROVIDER=coinbase.

Security and best practices

- Wallet keys stay local and are never sent to 1ly servers. Keep your private keys secure within your device.

- Budget limits prevent runaway spending on paid APIs and tokens.

- The MCP server is open source, allowing you to audit the code and verify security properties.

Error handling and troubleshooting

All responses indicate success or error with a structured payload. Common issues include missing wallet configurations, wallet not running, store creation requirements, and insufficient funds. Ensure you provide the correct wallet configuration when you attempt paid calls and verify your network and API key setup if you encounter authentication or access errors.

Examples and workflows

Pay for an API workflow: search for an API, view details, call the API, then optionally leave a review after the purchase.

Create a store and list paid APIs: launch a store, create paid links, and observe statistics over a chosen period.

Notes on tokens and Bags.fm (optional)

If you plan to launch tokens on Bags.fm, you will use dedicated token tooling to create tokens, list them, claim fees, and trade tokens. This requires a Solana wallet and knowledge of token mint addresses and related metadata.

Available tools

1ly_search

Search the 1ly.store marketplace for APIs and resources with optional filters like type and price range.

1ly_get_details

Retrieve detailed information about a specific API link, including pricing, currency, and payment networks.

1ly_call

Purchase and call a paid API with automatic crypto payment; receives a response and purchase metadata.

1ly_review

Submit a review for a purchased API with a purchase ID and review token.

1ly_create_store

Create a new seller store and obtain an API key for managing links and payments.

1ly_create_link

Create a new paid or free API link with title, URL, pricing, and metadata.

1ly_list_links

List all API links owned by your store, with status and pricing details.

1ly_update_link

Update properties of an existing API link such as price, URL, or visibility.

1ly_delete_link

Delete an existing API link from your store.

1ly_get_stats

Fetch store or link statistics over a chosen time period.

1ly_list_keys

List all API keys associated with your store.

1ly_create_key

Create a new API key to manage store access.

1ly_revoke_key

Revoke an API key to disable its access.

1ly_update_profile

Update basic profile fields such as username, display name, and bio.

1ly_update_socials

Replace the socials list for your store.

1ly_update_avatar

Update the store avatar using a public URL or base64 image.

1ly_withdraw

Request a withdrawal of funds to a Solana wallet address.

1ly_list_withdrawals

List recent withdrawal requests.

1ly_launch_token

Launch a token on Bags.fm and set up sharing rules and fee claimer providers.

1ly_list_tokens

List tokens launched by a wallet, with optional filtering by creator.

1ly_claim_fees

Claim Bags fee shares for a specific token.

1ly_trade_token

Trade tokens on Bags using quotes and swap flows.

1ly_trade_quote

Get a Bags trade quote without executing a swap.