pytheum-mcp
MCP server for the pytheum prediction-market context API.
On PyPI as
pytheum-mcp. Source: github.com/pytheum/pytheum-mcp. Docs: github.com/pytheum/pytheum-doc.
Wraps the four public endpoints on api.pytheum.com as MCP tools so AI agents (Claude Desktop, Cursor, anything that speaks MCP over stdio) can ask "which markets does this news article move?" without writing their own retrieval layer.
Install
Two install paths — both run the same Python code. Pick whichever your MCP client makes easier:
Via npm (recommended for Claude Desktop)
# no install needed — npx runs it
npx -y @pytheum/mcp
Claude Desktop ships a Node.js runtime but not Python, so npx is the path of least resistance there. The npm package is a small shim that runs uvx pytheum-mcp under the hood; uv is still required (see the npm README for the install one-liner).
Via PyPI (Python-native)
uvx pytheum-mcp # one-shot
uv tool install pytheum-mcp # permanent
Requires Python 3.11+ and uv.
Configure
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"pytheum": {
"command": "npx",
"args": ["-y", "@pytheum/mcp"],
"env": {
"PYTHEUM_API_BASE": "https://api.pytheum.com"
}
}
}
}
Restart Claude Desktop. The hammer icon in the composer should list pytheum's tools.
Cursor / Windsurf / others
Same config under ~/.cursor/mcp.json (or the client's equivalent). If you already have uv on PATH, you can swap npx -y @pytheum/mcp for uvx pytheum-mcp to skip the Node shim entirely:
{
"mcpServers": {
"pytheum": {
"command": "uvx",
"args": ["pytheum-mcp"],
"env": {
"PYTHEUM_API_BASE": "https://api.pytheum.com"
}
}
}
}
Tools
| Tool | Endpoint | Description |
|---|---|---|
t_find_markets(query, limit?, group_by?) |
GET /v1/markets/relevant-to |
Find markets matching free-text |
t_market_context(market_ref, limit?) |
GET /v1/markets/{ref}/context |
Events paired with a market |
t_bundle_context(bundle_ref, limit?) |
GET /v1/bundles/{ref}/context |
Events paired with any market in a bundle |
t_event_related_markets(event_id, limit?) |
GET /v1/events/{id}/related-markets |
Markets related to a firehose event |
Configuration
| Env var | Default | Purpose |
|---|---|---|
PYTHEUM_API_BASE |
https://api.pytheum.com |
Override to hit staging or a local stub |
Reference
Endpoint schemas, response shapes, errors, and rate limits live in pytheum/pytheum-doc. The machine-readable OpenAPI spec is at openapi.yaml.
License
MIT
Metadata
Release files for pytheum-mcp 0.1.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 | |
|---|---|---|---|---|
| pytheum_mcp-0.1.0.tar.gz | 10.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytheum_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.1 kB
Release files / pytheum_mcp-0.1.0.tar.gz
| Download URL | pytheum_mcp-0.1.0.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
79832f653f90d37c8bcfaa58a6759861d16472259260c629a8d7886d313194f1
|
|
BLAKE2b-256 checksum How to use checksums |
8d565a47e5553fb1c585b3a12718fa6e0ee5e0cc282efbf74af71d8014500470
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Release files / pytheum_mcp-0.1.0-py3-none-any.whl
| Download URL | pytheum_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7b229513a7d2dc55c3978347d124d38304d89e7e9d3d6a9980f0bb44435c5421
|
|
BLAKE2b-256 checksum How to use checksums |
0438857063498fcec03d4780fb70afc51a1d2adc87502698d464aaf13f446ecf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Security for pytheum-mcp 0.1.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.