Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者による説明(英語の原文)
Trade prediction markets with AI agents — skill discovery, autoresearch, and execution.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
SIMMER_API_KEY, SIMMER_MCP_ALLOW_LIVE「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"simmer": {
"command": "npx",
"args": [
"-y",
"simmer-mcp"
],
"env": {
"SIMMER_API_KEY": "your-value",
"SIMMER_MCP_ALLOW_LIVE": "your-value"
}
}
}
}ターミナルでこれを実行します
claude mcp add simmer --env SIMMER_API_KEY=your-value --env SIMMER_MCP_ALLOW_LIVE=your-value -- npx -y simmer-mcp動かす前に、空欄の値を入力してください。
プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"simmer": {
"command": "npx",
"args": [
"-y",
"simmer-mcp"
],
"env": {
"SIMMER_API_KEY": "your-value",
"SIMMER_MCP_ALLOW_LIVE": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"simmer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"simmer-mcp"
],
"env": {
"SIMMER_API_KEY": "your-value",
"SIMMER_MCP_ALLOW_LIVE": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
SIMMER_MCP_ALLOW_LIVE envこの設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月8日にチェック
公開者(adlai88)がリポジトリの所有者(SpartanLabsXyz)ではありません。別の人が登録した可能性があります
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち0項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:SIMMER_API_KEY
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(3.3.2)がレジストリに届いたのは6 か月前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.jsも必要です。
同じカテゴリには:Spec Driven Development, Remote Desktop Commander, Filesystem MCP
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Filesystem MCP server for AI assistants.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
Simmer is the leading prediction market harness for AI agents. Autonomous agents place trades on venues like Polymarket, Kalshi and Hyperliquid through a unified API — with self-custody wallets, safety rails, and smart context.
skills/ | 28 skills an agent installs and runs. skills/simmer/SKILL.md is the canonical source for simmer.markets/skill.md. |
mcp/ | MCP server, published to npm as simmer-mcp. |
simmer_sdk/ | Python SDK, published to PyPI as simmer-sdk. |
pip install simmer-sdk
Get your API key from simmer.markets/dashboard.
Most Simmer users run trading skills inside OpenClaw. The standard pattern uses a lazy singleton client and reads config from environment variables:
import os
from simmer_sdk import SimmerClient
SKILL_SLUG = "my-skill-slug" # Must match your ClawHub slug TRADE_SOURCE = f"sdk:{SKILL_SLUG}"
_client = None def get_client(live: bool = False): global _client if _client is None: venue = os.environ.get("TRADING_VENUE", "sim")
live controls paper vs real execution and is a constructor arg, not a_client = SimmerClient(api_key=os.environ["SIMMER_API_KEY"], venue=venue, live=live) return _client
def run(live: bool = False): client = get_client(live)
markets = client.get_markets(status="active", sort="volume", limit=20)
ctx = client.get_market_context(markets[0].id)
if not ctx.conflict and ctx.recommended_action != "hold": result = client.trade( market_id=markets[0].id, side="yes", amount=10.0, source=TRADE_SOURCE, skill_slug=SKILL_SLUG, reasoning="Signal detected — buying YES" ) print(f"{'PAPER: ' if not live else ''}Bought {result.shares_bought:.2f} shares")
if name == "main": import sys run(live="--live" in sys.argv)
Set environment variables:
export SIMMER_API_KEY=sk_live_...
export TRADING_VENUE=sim # sim | polymarket | kalshi export WALLET_PRIVATE_KEY=0x... # Required for Polymarket self-custody
Default to dry-run. Skills should require
--liveto execute real trades. Paper-trade with$SIMuntil your edge is consistent, then graduate to real money.
For developers building custom integrations:
from simmer_sdk import SimmerClient
client = SimmerClient(api_key="sk_live_...")
markets = client.get_markets(sort="volume", limit=10) for m in markets: print(f"{m.question}: {m.current_probability:.1%}")
result = client.trade(market_id=markets[0].id, side="yes", amount=10.0) print(f"Bought {result.shares_bought:.2f} shares for ${result.cost:.2f}")
for p in client.get_positions(): print(f"{p.question[:50]}: P&L ${p.pnl:.2f}")
| Venue | Currency | Description |
|---|---|---|
sim | $SIM (virtual) | Default. Paper trading on Simmer's LMSR markets. |
polymarket | USDC.e (real) | Real trades on Polymarket (Polygon). Requires WALLET_PRIVATE_KEY. |
kalshi | USDC (real) | Real trades on Kalshi. Requires Pro plan. |
# Paper trading (default)
client = SimmerClient(api_key="sk_live_...", venue="sim")
client = SimmerClient(api_key="sk_live_...", venue="polymarket", live=True)
client = SimmerClient.readonly(api_key="sk_live_...", venue="polymarket")
client.trade(market_id, side="yes", amount=10.0, venue="polymarket")
TRADING_VENUE environment variable is read at client init — OpenClaw skills use this to select venue at startup without code changes.
Constructor side effect: for live Polymarket clients with
WALLET_PRIVATE_KEYorOWS_WALLET, regularSimmerClient(...)construction checks pending risk alerts and may submit stop-loss/take-profit exit orders. This is intentional for self-custody safety: Simmer's server cannot sign those exits. Passprocess_risk_alerts=Falseto skip this constructor check for dry runs. UseSimmerClient.readonly(...)for API-key validation, preflight/status checks, and other non-trading paths.
Spread caveat: $SIM fills instantly (AMM, no spread). Real venues have orderbook spreads of 2–5%. Target edges >5% in $SIM before graduating to real money.
Polymarket order types: omit
order_typefor the SDK/server smart default: buys useFAK(fill what is available immediately), sells useGTC(rest on the book to improve fill rate on thin books). For structurally thin markets or maker-style limit entries, passorder_type="GTC"and an explicitprice.
Protocol V2 markets use PositionManager positions and the ExchangeV3 signing domain, version "3". This is separate from the April V2 order format selected by SIMMER_POLYMARKET_EXCHANGE_VERSION. Raw-key EOA signing and both raw-key and OWS deposit-wallet signing support these markets. OWS EOA signing remains legacy-only and rejects Protocol V2 metadata.
trade() reads the selected outcome's protocol from the Simmer market detail response. The server must return these fields on market detail and discovery responses before routing Protocol V2 markets through this SDK:
| Field | Current markets | Protocol V2 markets |
|---|---|---|
polymarket_protocol_version | Absent or "v1" | "v2" |
polymarket_position_id | Absent or null | YES position ID as a decimal uint256 string |
polymarket_no_position_id | Absent or null | NO position ID as a decimal uint256 string |
polymarket_neg_risk | Existing boolean | true for the neg-risk module, false for binary |
For current markets, polymarket_token_id and polymarket_no_token_id remain the signing IDs. For Protocol V2, the position ID becomes the signed tokenId; legacy token IDs are not required. The server must obtain the protocol and IDs from authoritative market metadata. The SDK does not infer them from dates, IDs, or the neg-risk flag. Unknown or null protocol markers and incomplete V2 metadata raise ValueError. The SDK caches market detail for the client session.
Market.polymarket_yes_protocol and Market.polymarket_no_protocol expose validated MarketProtocol values. Direct signing callers can pass market_protocol=MarketProtocol("v2", position_id) to build_and_sign_order, importing MarketProtocol from simmer_sdk.polymarket_contracts. The frozen value requires a position ID for V2 and forbids one for V1. Both signing paths consume the same value. build_and_sign_order rejects Protocol V2 with the legacy exchange flag.
client.ensure_approvals(protocol_v2=True) checks the existing approvals plus pUSD allowance and PositionManager operator approval for ExchangeV3. client.check_approvals(protocol_v2=True) requests GET /api/polymarket/allowances/{address}?protocol_v2=1. The server must return boolean entries in allowances named pusd_ and position_manager_ , using the full lowercase ExchangeV3 address:
pusd_0xe3333700ca9d93003f00f0f71f8515005f6c00aa is true when pUSD allowance(owner, ExchangeV3) >= (2**256 - 1) // 2, PolyNode's readiness threshold.position_manager_0xe3333700ca9d93003f00f0f71f8515005f6c00aa is the result of PositionManager isApprovedForAll(owner, ExchangeV3).Missing entries mean unapproved, even if an older server reports all_set=true.
With protocol_v2=True and a locally configured wallet, default-address check_approvals(), ensure_approvals(), and set_approvals() require activation status from GET /api/sdk/agents/me:
per_agent_wallet_address is present, per_agent_dw_active must be a boolean. When true, approval checks use per_agent_deposit_wallet_address.wallet_uses_deposit_wallet must be a boolean. When true, approval checks use deposit_wallet_address.When the applicable flag is false, approval checks use the configured EOA address. These calls fail closed: missing, null, or non-boolean activation status raises, and identity lookup errors propagate. An active DW without its address also causes approval checks to raise. Passing an explicit address to check_approvals() skips activation discovery and checks that address directly, including with protocol_v2=True.
For an EOA, client.set_approvals(protocol_v2=True) can submit the missing approvals. Deposit-wallet users must use the dashboard's Activate Trading flow, whose server implementation must also grant both approvals from the deposit wallet. The SDK does not submit EOA approvals for a deposit wallet. The default approval methods retain their existing scope. Managed wallets without a local address cannot confirm Protocol V2 readiness through this SDK.
Pass live=False to simulate trades with real market prices — no wallet or USDC required. For Polymarket, fills model the CLOB bid-ask spread for realistic P&L. Resolved markets auto-settle (winning shares pay $1, losers $0).
client = SimmerClient(
api_key="sk_live_...", venue="polymarket", live=False, # Simulate fills, no real money starting_balance=10_000.0 # Virtual capital (default: 10,000) )
result = client.trade(market_id=markets[0].id, side="yes", amount=50.0, reasoning="Testing strategy") print(f"Filled {result.shares_bought:.2f} shares (simulated)")
summary = client.get_paper_summary() print(f"Balance: ${summary['balance']:.2f}, P&L: ${summary['total_pnl']:.2f}")
Graduation path: sim (instant fills, no spread) → polymarket + live=False (real prices, spread modeled) → polymarket live (real USDC).
The three modes above are all *live-forward*. To test a strategy on historical data before risking capital, backtest the skill bundle:
pip install 'simmer-sdk[backtest]'
simmer backtest --demo
simmer backtest ./my-skill --entrypoint run.py \ --t0 2026-03-01 --t1 2026-03-08 --cadence 12h --out report.json
simmer backtest ./my-skill --entrypoint run.py --window 30d simmer backtest ./my-skill --entrypoint run.py --tape ./slice --t0 2026-03-01 --t1 2026-03-08
冒頭だけを表示しています。続きはリポジトリで読めます