Skip to content

FlashGate MCP 0.3.0

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 25 Oct 21:52
fa4082c

FlashGate MCP 0.3.0

This is the first public prerelease of FlashGate MCP. It includes the cumulative changes recorded for product versions 0.1.0, 0.2.0, and 0.3.0. Versions 0.1.0 and 0.2.0 were earlier repository version milestones, not separately published GitHub releases. The sections below reproduce the version history from the CHANGELOG.md frozen at tag v0.3.0; they do not include the Unreleased section.

[0.3.0] - 2026-10-23

Public prerelease scope

  • The local STDIO server supports MCP 2025-11-25 with the eight existing filesystem tools: list_directory, read_file, get_path_info, write_file, create_directory, delete_path, copy_path, and move_path. Access remains subject to the configured root, path restrictions, read-only mode, and hard resource limits.
  • The existing release-artifact formats target Windows and Linux x64/ARM64. Search, managed processes, system-service operation, and public activation of MCP 2026-07-28 are not part of this prerelease.

Added

  • Implemented an internal MCP 2026-07-28 stateless adapter candidate with per-request metadata validation, server/discover, revision-specific errors and results, and conservative private cache hints. The existing 2025-11-25 initialization path remains the production default. The new path is not publicly enabled or advertised; activation awaits BL-204, BL-212, and BL-219.

[0.2.0]

Changed

  • Expected registered filesystem-tool failures now return MCP isError:true with compact category/message text JSON and no structuredContent. Request errors and unavailable tools remain JSON-RPC; unexpected failures use generic Internal error. Success output schemas and results are unchanged.

[0.1.0]

Added

  • Established root VERSION as the sole editable product SemVer source (0.1.0 seed), with exact release-tag parity and generated notes audited from this changelog. This entry does not mark 0.1.0 as released.
  • Added explicit MCP 2025-11-25 discovery annotations for all eight filesystem tools. The exact annotation matrix includes explicit false members; annotations do not grant authorization or change server-side checks.
  • Added task-bound scratch routing for PowerShell and Python validation producers, with explicit working roots, fail-closed path validation, and portable Windows/Linux checks.
  • Added deterministic Windows and Linux shell-script validation, including PowerShell parsing, Bash syntax, encoding, line-ending, bounded-process, and cleanup checks.
  • Added canonical build identity, embedded build manifests, Windows resources, Linux build metadata, and deterministic Windows ZIP and Linux TAR.GZ release artifacts for x64 and ARM64. Release validation checks contents, hashes, reproducibility, and host/credential leakage.
  • Added Go coverage reports and separate Windows/Linux coverage gates, plus resource, latency, payload, catalog, and token-efficiency benchmarks.
  • Added MCP CallToolResult wrapping and structuredContent for successful filesystem tool results, with runtime outputSchema for all eight tools.
  • Added strict startup root validation and a read-only activation/rollback guide for local STDIO clients.
  • Established a public, self-contained repository boundary for build, test, release, contribution, and product documentation.

Changed

  • Switched coverage to the deterministic production-server package graph and raised the separate Windows/Linux hard gates to 90.0%, with an exact unrounded threshold check and package inventories.
  • Converged public documentation and the documentation gate around current filesystem capabilities, Version 1.0 targets, portable contributor guidance, and durable repository-boundary checks.
  • Kept the current MCP runtime at 2025-11-25; Version 1.0 planning targets a separate 2026-07-28 path without advertising it before implementation and compatibility tests.
  • Maintained the eight-tool filesystem baseline: list_directory, read_file, get_path_info, write_file, create_directory, delete_path, copy_path, and move_path.
  • Clarified the Version 1.0 boundary: Planned tasks are required for the initial stable release, while Later tasks are accepted post-Version-1.0 work.
  • Kept source and build tooling in the public checkout without requiring a private development control plane.

Planning

  • Planned reusable content identities under BL-048 as non-authorizing evidence, Version 1.0 compare_paths/verify_paths under BL-346, and post-Version-1.0 conditional retrieval and optional transparent caches under BL-217.
  • Planned Version 1.0 named-root discovery, command discovery, bounded search, managed processes, typed command execution, system information, safe capability profiles, payload-efficient results, and service-account-root operation.
  • Documented future Platform Adapter and Native Tool Adapter boundaries, cloud/placeholder storage behavior, transparent path compression/encryption, content compression, extended metadata, and one optional portable FlashGate agent skill.
  • Kept cloud/placeholder storage, conditional retrieval, transparent path compression/encryption, and the portable agent skill post-Version-1.0.
  • Planned one canonical product-version source under BL-245 so feature merges carry their SemVer change in the same product change; documented post-merge closure of superseded PRs and safe obsolete-branch cleanup without deleting historical merged PR records.
  • Moved BL-260 and BL-245 from the final release-gate sprint to the start of SPR-048 and bound the prerequisite order BL-260 -> BL-245 -> BL-203, so product-code coverage and canonical versioning are established before further functional implementation.

Fixed

  • Corrected successful tool responses to use MCP CallToolResult after strict clients rejected unwrapped domain objects.
  • Improved root confinement, traversal and reparse handling, JSON-RPC validation, hard limits, redacted diagnostics, and read-only tool registration.
  • Corrected coverage summary status on failed thresholds and kept benchmark soft-budget messages out of general warnings.

Security

  • Startup rejects missing, relative, nonexistent, or disallowed roots before tool registration; development use of the current directory requires explicit opt-in.
  • Filesystem access remains root-confined, with hidden, UNC, symlink, junction, and reparse policies enforced server-side. Standard output remains reserved for JSON-RPC.