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.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 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는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
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, A1RO — Irish employment tools
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도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.
Irish temp worker cost, public holiday pay and holidays, and SafeHandle certificate checks.
제작자의 저장소에서 쓰인 그대로 가져왔어요. 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
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요