Limitless MCP Server

What Limitless MCP Server does

Limitless MCP Server MCP server gives MCP-compatible clients access to Limitless Exchange prediction markets on Base. Its tools cover account creation, wallet handling, market data, trading, positions, portfolio history, and token transfers. The server supports both newly generated Base wallets and imported wallets, including encrypted wallet storage.

Market tools can list active markets with pagination, search markets semantically, retrieve market details and venues, inspect bids and asks, view historical prices, and browse categories. Trading tools support limit orders, single-order cancellation, cancellation of all orders in a market, order listing, fill-price estimates, token approval checks, approval setup, and locked USDC reporting.

Position tools provide active positions with profit and loss, trade history, portfolio history, and position synchronization. Wallet tools report addresses, wallet type, balances, deposit addresses, and wallet status. ETH and USDC can be sent to another address through the transfer tools.

How it works

The server exposes MCP over a /mcp endpoint. Requests use JSON-RPC, and authenticated calls include an x-api-key header. The README provides a Cursor configuration using a hosted HTTPS endpoint, but the project can also be built and run as a self-hosted Node.js service.

Account setup can begin with limitless_signup, which creates an account and a fresh Base wallet. Other tools generate or import wallets, retrieve import instructions, and import a private key directly. Limit orders use EIP-712 signed authentication, while token approval tools handle USDC and CTF permissions.

The Limitless MCP Server MCP server uses PostgreSQL for application data and a Base RPC endpoint for blockchain access. Its API configuration points to the Limitless Exchange API. A health endpoint is available at /health, and HTTP market routes are documented for active markets, search, market details, and order books.

Setup and configuration

Self-hosting requires Node.js 20 or later, PostgreSQL 15 or later, and Base RPC access. The documented installation flow is:

1. Clone the repository and install npm dependencies.
2. Copy .env.example to .env.
3. Set the database, encryption, blockchain, API, server, and admin key values.
4. Run npx prisma generate and npx prisma db push.
5. Build and start the application with npm run build and npm start.

The main settings are DATABASE_URL, ENCRYPTION_KEY, BASE_RPC_URL, LIMITLESS_API_URL, PORT, NODE_ENV, and ADMIN_API_KEY. BOT_SIGNING_SECRET is documented as optional. Docker and Railway deployment examples are also included. The encryption and admin keys should be generated with secure random values as shown in the README.

For a hosted MCP connection, configure the client with the server URL and an API key in the request headers. For a local deployment, use the address and port of the running service.

Limitations and notes

The repository notice says Quantish is winding down and that the team will no longer maintain or update the project. The server is described as self-hosted and intended to continue working independently, but users should account for the lack of ongoing maintenance when evaluating it.

This toolset can create wallets, import private keys, place orders, and transfer assets. Those operations require careful handling of API keys, encrypted wallet data, private keys, approvals, and destination addresses.

The README advertises 34 tools, while the supplied tool inventory lists the wallet, market, trading, position, and transfer operations directly. Verify the tool list exposed by the deployed instance before relying on any additional account or API-key management tools.