fix: validate MCP Toolbox and add Codex marketplace#3
Merged
Conversation
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
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.
What changed
uvx toolbox-coreconfiguration with the supported@toolbox-sdk/server --stdio --configcommand in Claude, Gemini, and shared MCP configuration.Why
toolbox-coreis a Python library rather than an MCP server CLI. The previous configuration could not start Toolbox. The corrected package and arguments complete an MCP stdio initialization and expose the expected tools.Impact
Codex can discover the plugin through the local marketplace, and configured agents can launch the Toolbox database MCP server with a supplied
tools.yaml.Validation
make gate— passed: 17 skill contracts, packaging for Claude/Antigravity/Codex/Kimi, Mermaid, 100 links, and 136 smoke tests.Freshness note
make checkcompleted with 9 fresh and 96 drifted source hashes, with zero fetch errors. This is a pre-existing repository-wide documentation freshness backlog outside this configuration-focused change; the affected Toolbox source was manually reviewed against the current official CLI documentation.