MCP tool catalog
Generated from crates/versionx-mcp/src/tools/. Workflow-shaped; tool count capped at ~10.
Summary
| Tool | Mutating | Purpose |
|---|---|---|
bump_propose | no | Propose version bumps |
changelog_draft | yes | Draft a voice-aware changelog section |
config_read | no | Read versionx.toml |
policy_check | no | Evaluate policies |
release_apply | yes | Apply an approved release plan |
release_propose | yes | Propose a release plan |
state_read | no | Read persisted state |
workspace_graph | no | Dependency graph |
workspace_list | no | List workspace components |
workspace_status | no | Workspace change state |
Per-tool detail
bump_propose
Propose version bumps
Compute per-component bump levels from content-hash deltas vs. the lockfile baselines. Does not mutate disk. Use release_propose for the fuller plan artifact.
- Kind: Read-only
- Source:
crates/versionx-mcp/src/tools/bump_propose.rs
changelog_draft
Draft a voice-aware changelog section
Use a configured BYO-API-key provider to draft a CHANGELOG section for the next release, matching the repo's prior voice. Does not commit — the draft is returned + written to .versionx/mcp/.
- Kind: Mutating
- Source:
crates/versionx-mcp/src/tools/changelog_draft.rs
config_read
Read versionx.toml
Return the contents of the workspace's versionx.toml. Treated as trusted (first-party config), but still fenced to keep downstream models consistent about provenance.
- Kind: Read-only
- Source:
crates/versionx-mcp/src/tools/config_read.rs
policy_check
Evaluate policies
Load every policy under .versionx/policies/ and evaluate against the current workspace state. Returns findings grouped by severity with waiver hits resolved.
- Kind: Read-only
- Source:
crates/versionx-mcp/src/tools/policy_check.rs
release_apply
Apply an approved release plan
Apply a previously-proposed plan: write versions to manifests, refresh the lockfile, create release commit + tags. Requires an explicit plan_id — no auto-select. Set approve = true to approve in-place if the plan isn't yet approved.
- Kind: Mutating
- Source:
crates/versionx-mcp/src/tools/release_apply.rs
release_propose
Propose a release plan
Build a release plan from content-hash diffs + optional commit messages. Persists to .versionx/plans/<id>.toml. Unapproved — must be approved by a human (or the release_apply caller) before landing.
- Kind: Mutating
- Source:
crates/versionx-mcp/src/tools/release_propose.rs
state_read
Read persisted state
Summarize the workspace's on-disk state: lockfile, release plans, policy lockfile. Returns paths + parsed contents for the files that exist.
- Kind: Read-only
- Source:
crates/versionx-mcp/src/tools/state_read.rs
workspace_graph
Dependency graph
Intra-workspace dependency DAG. Returns every node, every edge (from → to), and a topological order (leaves first) safe for release iteration.
- Kind: Read-only
- Source:
crates/versionx-mcp/src/tools/workspace_graph.rs
workspace_list
List workspace components
Discover every component (Node package, Rust crate, Python project, declared asset bundle, …) under the workspace root. Returns ids, kinds, versions, and intra-workspace dependency edges.
- Kind: Read-only
- Source:
crates/versionx-mcp/src/tools/workspace_list.rs
workspace_status
Workspace change state
For every component, compute the BLAKE3 content hash and compare to the last-released hash in versionx.lock. Returns dirty/clean + transitive cascade of dependents that would need to re-release.
- Kind: Read-only
- Source:
crates/versionx-mcp/src/tools/workspace_status.rs
See also
- MCP server overview
- Plan / apply cookbook — the safety contract every mutating tool participates in.