Manifold Markets

io.github.jbeshirPublished by GitHub account jbeshirv1.0.2Updated Oct 29, 2026

Search, read, bet on, create, and resolve prediction markets on Manifold.

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

Manifold Markets MCP server that lets an assistant search, read, bet on, create and resolve prediction markets using a Manifold account.

What you can do
  • Search markets by keyword and filters, and read market details, answers, descriptions and comments
  • Look up user profiles, the authenticated account, bets and positions
  • Place bets and limit orders (with a dry-run option), sell shares and cancel pending orders
  • Create, resolve and close markets, add comments and add mana liquidity
  • Send mana to other users and review portfolio P&L with 24h changes and baseline probabilities
When to use it
Useful when you want an assistant to research prediction markets on Manifold, simulate or execute trades, manage markets you created, or review your portfolio performance without leaving the chat client.
Requirements
Runs locally over stdio as a prebuilt binary, from source with Go 1.27.3+, or in Docker. Requires a Manifold Markets API key supplied in the MANIFOLD_API_KEY environment variable; an optional MANIFOLD_API_URL overrides the default API endpoint. Needs network access to the Manifold API.
Before you install
The API key in MANIFOLD_API_KEY grants access to your Manifold account and should be kept private. Several tools move real platform currency: place_bet, sell_shares, add_liquidity and send_mana spend or transfer mana, and create_market, resolve_market, close_market, add_comment and cancel_bet change data on the platform. Prefer the dry-run option when testing bets, and note that market data and account activity are sent to the Manifold API.

Installation

In SourceWeft

  1. Open Manifold Markets in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Manifold Markets MCP Server

An MCP server for interacting with Manifold Markets, a prediction market platform. Provides 18 tools covering market discovery, trading (bets and limit orders), market management (creation, resolution, comments, liquidity), and portfolio analytics. Communicates over stdio and works with any MCP-compatible client such as Claude Desktop or Claude Code.

Getting Started

Requirements

Configuration

VariableRequiredDescription
MANIFOLD_API_KEYYesYour Manifold Markets API key
MANIFOLD_API_URLNoCustom API URL (default: https://api.manifold.markets)

Install from source

Requires Go 1.27.3+.

go install github.com/jbeshir/mcp-servers/manifold/cmd/manifold-mcp@latest

Pre-built binaries

Download from Releases.

Docker

docker build -t manifold-mcp ./manifolddocker run -e MANIFOLD_API_KEY=<your-key> manifold-mcp

Claude Desktop

json
{  "mcpServers": {    "manifold": {      "command": "/path/to/manifold-mcp",      "env": { "MANIFOLD_API_KEY": "<your-key>" }    }  }}

Claude Code

claude mcp add manifold -- env MANIFOLD_API_KEY=<your-key> /path/to/manifold-mcp

Tools

Read operations

ToolDescription
search_marketsSearch markets by keyword and filters
get_marketGet full market details including answers and description
get_userGet a user's profile by username
get_meGet the authenticated user's profile
list_betsList bets with optional filters
get_commentsGet comments on markets
get_positionsGet user positions for a specific market

Trading

ToolDescription
place_betPlace a bet or limit order (supports dryRun)
sell_sharesSell shares in a market
cancel_betCancel a pending limit order

Market management

ToolDescription
create_marketCreate a new market (binary, multiple choice, or numeric)
resolve_marketResolve a market you created
close_marketClose a market or change its closing time
add_commentComment on a market
add_liquidityAdd mana liquidity to a market
send_manaSend mana to other users

Analytics

ToolDescription
get_baselineGet deterministic baseline probability for a market at a past time (default: 24h)
get_portfolio_pnlGet full portfolio P&L summary with 24h changes for all positions

Key Concepts

  • Markets -- Questions that users trade on. Each market has a type (binary yes/no, multiple choice, pseudo-numeric, etc.), a probability or set of answer probabilities, and a closing time after which no new bets are accepted.
  • Mana -- The platform currency used for betting and trading. Users receive mana through deposits, trading profits, and transfers from other users. Mana is also used to add liquidity to markets or to send to other users.
  • Bets and shares -- Placing a bet on an outcome buys shares in that outcome. The price per share reflects the market's current probability. Shares can be sold back at any time before resolution.
  • Limit orders -- Instead of buying at the current price, a limit order specifies a probability threshold. The order stays open until it fills, expires, or is cancelled. Use place_bet with a limitProb parameter to create one.
  • Positions -- A user's current holdings in a market: which outcomes they hold shares in, how many, and their profit/loss.
  • Resolution -- The market creator decides the outcome (YES, NO, MKT for partial, or CANCEL). For multiple choice markets, a specific answer ID is resolved. Resolution triggers payouts to shareholders.
  • Liquidity -- Mana added to a market's pool to reduce slippage (the price impact of large bets). Higher liquidity means prices move less per bet.
  • Market types -- BINARY (yes/no), MULTIPLE_CHOICE (several named answers), FREE_RESPONSE (open-ended answers), PSEUDO_NUMERIC (numeric range mapped to a probability), BOUNTY, POLL, and NUMBER.
  • Dry runs -- The place_bet tool supports dryRun=true to simulate a bet without executing it, showing what the outcome and cost would be.

Architecture Overview

mermaid
graph LR    Client["MCP Client<br/>(Claude Desktop, Claude Code)"]    Server["manifold-mcp<br/>MCP Server"]    HTTP["HTTP Client"]    API["Manifold Markets<br/>REST API"]
    Client -- "JSON-RPC over stdio" --> Server    Server --> HTTP    HTTP -- "HTTPS + API key auth" --> API

The server has three internal layers:

  • cmd/manifold-mcp -- Entry point. Reads configuration from environment variables, creates the HTTP client and MCP server, and starts the stdio transport.
  • internal/server -- Registers all 18 MCP tools, routes incoming requests to handlers, and formats responses. Tool definitions are split across tools.go (read operations), tools_trading.go (trading), and tools_manage.go (market management).
  • internal/client -- REST client for the Manifold Markets API. Handles authentication (API key in the Authorization header), JSON serialization, and error handling.

Data Flow

A typical trading workflow: search for a market, inspect it, simulate a bet, then execute.

mermaid
sequenceDiagram    participant C as MCP Client    participant S as manifold-mcp    participant A as Manifold API
    C->>S: search_markets(term: "AI")    S->>A: GET /v0/search-markets?term=AI    A-->>S: Market list    S-->>C: Formatted results
    C->>S: get_market(marketId: "abc123")    S->>A: GET /v0/market/abc123    A-->>S: Full market details    S-->>C: Question, probability, answers
    C->>S: place_bet(contractId, amount, outcome, dryRun: true)    S->>A: POST /v0/bet (dryRun)    A-->>S: Simulated bet result    S-->>C: Expected shares, probability change
    C->>S: place_bet(contractId, amount, outcome)    S->>A: POST /v0/bet    A-->>S: Executed bet    S-->>C: Bet confirmation

Source: manifold/README.md at commit 27dc1b2

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.2LatestOct 29, 2026
  2. v1.0.1Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts