SQXtreme — StrategyQuant X MCP control layer
Wrapper/extension over sq-mcp that adds Windows-first DX, Spanish localization, and multi-client configs for AI agents (opencode, Claude Code, Cursor, VS Code).
Repo: https://github.com/herjarsa/sqxtreme-mcp
What ships in v0.4.0
sq-mcp (DAVIDAROCA27) is the foundation: 482 runtime tools, MIT, 1571 tests. SQXtreme v0.4.0 adds (78 tests, CI verde, OIDC publish):
- Windows installer —
iwr install.ps1 | iex(4 modos: CheckOnly/PyPI/FromSource/FromGit) - Spanish localization — 5 workflow prompts + 4 sub-agentes (
prompts/es/) — es/ - Multi-client configs — Claude Code, opencode, Cursor, VS Code (
examples/) - HTTP transport —
SQXTREME_TRANSPORT=http→streamable-httpen:8765(vs nativo:8082) - 12 features 3 fases — AlgoWizard auto-import, Builder desde frase, Live Watch, Streaming, Data auto-fix, Auto-curator, Ship MT5, Snapshot rollback, Ashare 119, Scheduled Runner, sqx-tools wrapper, Health Dashboard
- CI matrix — Ubuntu + Windows × Python 3.10/3.11/3.12 — ruff + pytest
- PyPI OIDC — Trusted Publishing sin token manual (
publish.yml)
Roadmap (post v0.4.0)
Live trading bridge refinements · Visual QA para dashboards · Multi-workspace orchestrator.
Install
# One-liner (after PyPI publish)
iwr https://raw.githubusercontent.com/herjarsa/sqxtreme-mcp/main/install.ps1 -UseBasicParsing | iex
# Or from source
git clone https://github.com/herjarsa/sqxtreme-mcp.git
cd sqxtreme-mcp
.\scripts\install.ps1 -FromSource
What this gets you (honest scope)
Running an AI agent with SQXtreme + [full] extra: 9 Spanish MCP prompts + 482 sq-mcp runtime tools delegated + cross-client install.
NOT included in v0.4.0: a live AI agent actually connected (manual client setup per docs/CLIENTS.md), E2E test with real SQ X engine.
License
MIT.
1 maintainer
Release files for sqxtreme-mcp 0.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| sqxtreme_mcp-0.4.2.tar.gz | 40.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sqxtreme_mcp-0.4.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 64.7 kB
Release files / sqxtreme_mcp-0.4.2.tar.gz
| Download URL | sqxtreme_mcp-0.4.2.tar.gz |
|---|---|
| Size | 40.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
009e31156db2e7bb078547c97d95244bc895bf51f73a2cb68dee9e1d64ca3fa7
|
|
BLAKE2b-256 checksum How to use checksums |
1640c7ab7bfb0ea3a879b16a38988343a7c530f2d3e60c9dc3690378cd132a4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 30, 2026.
Transparency logRelease files / sqxtreme_mcp-0.4.2-py3-none-any.whl
| Download URL | sqxtreme_mcp-0.4.2-py3-none-any.whl |
|---|---|
| Size | 24.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2a711ec3ffcabb9e225d9a761fed7668d43765cdff77b531cd146c36452775a3
|
|
BLAKE2b-256 checksum How to use checksums |
3ed57518478362e393f09d054252c5df7a6dd2d288829d49afc08f3ecc1fbea8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 30, 2026.
Transparency log
