This project has been archived by its maintainers, and is no longer receiving any updates.
simmer-reactor-mcp
MCP server for Simmer Reactor — real-time whale trade events from Polymarket.
Works with any agent runtime that supports MCP: OpenClaw, Hermes, Claude Code.
Install
pip install simmer-reactor-mcp
Setup
Set your Simmer API key:
export SIMMER_API_KEY=your_api_key
OpenClaw (bundle .mcp.json)
{
"mcpServers": {
"simmer-reactor": {
"command": "simmer-reactor-mcp",
"env": { "SIMMER_API_KEY": "${SIMMER_API_KEY}" }
}
}
}
Hermes (~/.hermes/config.yaml)
mcp_servers:
simmer-reactor:
command: "simmer-reactor-mcp"
env:
SIMMER_API_KEY: "${SIMMER_API_KEY}"
Claude Code (.claude.json)
{
"mcpServers": {
"simmer-reactor": {
"command": "simmer-reactor-mcp",
"env": { "SIMMER_API_KEY": "${SIMMER_API_KEY}" }
}
}
}
Tools
get_whale_events
Returns recent whale trades from tracked Polymarket wallets.
execute_reactive_skill
Runs any installed skill in reactive mode, triggered by a whale event.
Defaults to polymarket-copytrading. Requires the skill installed via ClawHub.
Auto-React Mode
When enabled (default), the MCP server automatically executes reactive skills
when whale events arrive for wallets with auto_copy enabled in your dashboard.
No agent decision needed — trades fire within seconds of the whale's trade.
The circuit breaker pauses auto-react after 3 consecutive failures and falls
back to passive mode (events still buffer for get_whale_events).
Environment Variables
| Variable | Required | Description |
|---|---|---|
SIMMER_API_KEY |
Yes | Your Simmer SDK API key |
SIMMER_API_URL |
No | API base URL (default: https://api.simmer.markets) |
REACTOR_AUTO_REACT |
No | Enable auto-dispatch on auto_copy wallets (default: true) |
REACTOR_VENUE |
No | Trading venue for auto-react (default: sim) |
REACTOR_MAX_USD |
No | Max trade size per auto-react (default: 25) |
REACTOR_SKILL |
No | Skill slug for auto-react (default: polymarket-copytrading) |
SIMMER_COPYTRADING_SKILL_DIR |
No | Path to copytrading skill (auto-detected via clawhub) |
Metadata
Release files for simmer-reactor-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| simmer_reactor_mcp-0.2.0.tar.gz | 6.7 kB | Without provenance | Details for simmer_reactor_mcp-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| simmer_reactor_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for simmer_reactor_mcp-0.2.0-py3-none-any.whl |
Total release size: 15.0 kB
Release files / simmer_reactor_mcp-0.2.0.tar.gz
| Download URL | simmer_reactor_mcp-0.2.0.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
80236b330fc85a5130ca009bd20757a4d51799755dd4f9f1931047e284559171
|
|
BLAKE2b-256 checksum How to use checksums |
32be42491db61cbc7f59047f5e55a18722a521a590badd2907519f966230c22b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.8
|
Release files / simmer_reactor_mcp-0.2.0-py3-none-any.whl
| Download URL | simmer_reactor_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
37d1370ea707de674b7cad8c5ed5668baa4c1330e622ff649e3366ca099718fa
|
|
BLAKE2b-256 checksum How to use checksums |
b024897678ed13fa508e96150514b2864ac8435b40cab1aaf43438943d350076
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.8
|
Security for simmer-reactor-mcp 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.