Repository navigation
Expand MCP to 31 tools and improve execution reliability - #7
Merged
Merged
Conversation
chris-cpz
marked this pull request as ready for review
September 14, 2026 05:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CPZAI's MCP adapter exposed only the first page of several account and portfolio lists, omitted stop-price input, and could describe a failed or timed-out execution as successful. This change expands the public surface from 21 to 31 tools and makes those outcomes explicit.
Adds data-file discovery and record inspection, individual backtest/order/risk reads, and five middle-office reporting tools through existing scoped REST endpoints. Existing tools gain bounded pagination and validation, historical feed selection, structured results, and request tracing. GET retries are bounded; mutations are never retried, and uncertain outcomes include reconciliation guidance. Failed Python executions and partial portfolio syncs remain errors.
Adds two MCP guide resources, two read-only workflow prompts, browser preflight support, request transport cleanup, and a catalog exported from real MCP discovery with documentation drift checks. Version 1.2.0 retains existing tool names. Time-in-force is restricted to day because legacy broker routes ignore other durations; broker stop support remains documented. Container probes now explicitly use IPv4 to match the listening address.
Validation: all 135 tests pass under the exact CI environment; TypeScript checks and build pass. Native AWS build aquila-mcp-build:35ea113d-5a6b-4033-b6d0-8794683e9718 passed the full suite, Docker build, and runtime health check for source 413bcae. The merged commit has an identical source tree. GitHub Actions itself cannot start because of the account billing lock. Existing dependency advisory counts are unchanged from main.
The corresponding public documentation is deployed and verified. ECS rollout completed on task revision aquila-mcp:5 with two healthy instances using immutable digest sha256:2dbf098671c4939c825923d683617ded46451b804b5ef9d25048f6ef0b0da06b. Live discovery confirms version 1.2.0, all 31 tools, two resources, and two prompts. Both guide reads and prompt retrieval pass; preflight returns 204, missing authentication returns 401, and invalid credentials produce a structured error. Existing tokens and secrets are preserved; rollback configuration is saved. No live trading calls or migrations were performed.
Companion change: https://github.com/CPZ-Lab/cpzai/pull/1602