Repository navigation
Releases
v0.2.0-rc.3
Ada MCP Server 0.2.0-rc.3
RC3 separates the installed skill/plugin entry from the exact Ada MCP runtime
it uses. This remains a Linux/AMD64 Debian Trixie Docker pilot with the same
pinned SDK/ALS and support boundaries. Python/MCP metadata uses 0.2.0rc3;
distribution metadata uses 0.2.0-rc.3. Actual published release assets establish
availability; this source document alone does not.
- Keep a compatible full/local or lightweight entry installed while selecting
another exact verified runtime/binding. Entry package version is independent
of the active server version; compatible updates require no plugin upload. - Require integer workflow contract 1 in authenticated release/runtime metadata.
Missing or unknown contracts need a compatible entry update before activation. - Inspect private pinned selection before using fallback acquisition. Explicit
activation uses no-clobber writes or expected-old-state backups and preserves
the old runtime/image/binding for rollback. Validate record ownership/type/size
on the same opened descriptor that supplies its bytes; reject unchecked swaps. - Return structured invalid results for malformed nested OCI binding metadata
while preserving the active pair. Keep source-only helper validation and
immutable image/source pins. - Retain files and their locator for later sessions. A custom selection path
is not automatically remembered; supply it again or explicitly retain it
through a supported host setting. Report session-only use where unavailable.
Public RC1/RC2 bytes remain immutable legacy baselines. RC2's entry has no
selection support and needs one initial entry update to gain it; its existing
update checker can still announce newer published releases. See the
first-install guide
and approved update/rollback procedure
for actual asset-digest verification, initial setup and activation.
A separate manual post-publication consumer check exercises the public RC2
runtime's actual notice of RC3 through MCP initialization/project results and
a fresh explicit check. Its real evidence must be inspected after publication;
unit fixtures do not establish that outcome. It does not install the target
or mutate a private Cloud plugin. See the
release procedure.
The support matrix
still limits semantic/tool acceptance. Compiler/tests remain separate. Actual
macOS, native Codex/Claude/OpenCode lifecycle and another account's Cloud import
remain development work. Preserve the original MIT and component notices under
licensing.
v0.2.0-rc.2
Ada MCP Server 0.2.0-rc.2
RC2 prepares the public installation and update workflow for this independently
maintained continuation. It retains the Linux/AMD64 Debian Trixie Docker pilot
and the pinned Ada Language Server. Python package metadata and MCP
initialization use 0.2.0rc2; distribution metadata uses 0.2.0-rc.2.
Publication is established by the actual non-draft release and verified assets,
not by this source document alone.
- Install directly from public tooling without a private plugin or Plugin
Creator. Optional local Codex and reader-owned private Cloud skills guide
the same Docker binding and source-bound queries. - Receive available-version advisories in initialization and project results.
Host checks use a private daily cache, a bounded public metadata request,
opt-out and stable/prerelease policy; installed pins never silently move. - Ask for a fresh release check immediately. Explicit checks bypass the local
daily cooldown while respecting actual provider retry deadlines across
channels. Old advisories become stale and expire even in long-running sessions. - Let the skill inspect a real target, ask once and execute an approved update:
verify new artifact pins, stage matching runtime/image/binding/skill/client
configuration, test real project queries and retain operational rollback. - Keep verified helper source bytes through client dispatch and isolated update
fetches. Packaged helpers fail closed on missing declarations; explicit notice
cache paths are validated before query/configuration output is created. - Publish these source-reviewed notes with the exact tested artifacts, without
rebuilding or adding the notes file to the artifact set.
Existing RC1 archives remain immutable and have no update-notice hook. They
need one initial approved upgrade to a published RC2 or later. The
first-install guide
provides a concrete prompt using actual GitHub asset digests, the final release
manifest and exact tag commit. It retains RC1's verified pinned fallback;
never reuse RC1 hashes as RC2 pins. See
approved updates and rollback
for activation and provider limits.
The support matrix
still limits supported semantic queries and diagnostics. Compiler/tests remain
separate. Actual macOS, native Codex/Claude/OpenCode lifecycle and a separate
account's Cloud import remain development work, not inferred acceptance.
The public plugin contains a skill, not native MCP registration or a hosted
service. Publication does not update a private account plugin automatically.
Preserve the original MIT notices and the container components' own terms;
see licensing.
v0.2.0-rc.1
Ada MCP Server 0.2.0-rc.1
This is the first pilot prerelease prepared by the independently maintained
abuild-project continuation of
MDBrothers/ada-mcp-server.
The selected personal fork's history, authorship and MIT notices are retained.
It is an independent distribution and maintenance line, not an upstream release.
The coordinated SemVer is 0.2.0-rc.1; Python package and MCP initialization
metadata report its PEP 440 form 0.2.0rc1. Server, container, host tooling and
lightweight skill use one version. This is a prerelease for pilot acceptance;
pin its immutable source/artifact metadata when evaluating it.
Included workflow
- A standalone Linux/AMD64 Debian Trixie container with GNAT 14, pinned GPRbuild,
Ada Language Server and hash-locked Python dependencies. - Explicit GPR, dependency-search-path and scenario selection across Ada
repositories, preserving the selected ancestor-GPR behavior. - Source-anchored project, symbol, navigation and per-file diagnostic queries
within the documented support scope. - Hash-verified tooling/image acquisition, explicit host bindings and a
read-only, nonroot, network-isolated runtime with private HOME and evidence. - Source/image/version receipts binding release packaging to the exact tested
source, Python distributions and immutable Docker target.
The source and own tooling use MIT; redistributed components keep their own
licenses and corresponding-source obligations. See
licensing.
Acceptance and limits
The release source must pass the complete documented AMD64 Trixie chain,
including tests, coverage, Ruff, strict typing, packaging, documentation and
real ALS/MCP controls. Generated-artifact host acceptance exercises Linux
numeric identities 1000:1000 and 501:20 and confirmed EOF/container removal.
Only a successful CI run at the exact selected main commit supplies the
release artifacts; an earlier candidate's successful run does not certify it.
MCP file diagnostics do not replace compiler, test or coverage CI. The 19-tool
catalog does not promise support for every advertised operation. macOS/Apple
Silicon emulation, Docker Desktop/Colima sharing, native Claude/OpenCode
registration and other unaccepted tools remain in development. Linux numeric
identity tests do not establish actual Mac compatibility.
Public download verification, anonymous registry access and ordinary acquisition
in a fresh managed Cloud task need their own observed evidence. Publication
enables those consumer tests; this source document does not claim they have
already passed. The pilot can be published before the deferred Mac/native-client
acceptance, while preserving those limits.
Artifact availability
GitHub Releases
is the authority for published versions and assets. Generated candidate URLs
are prepared targets until publication succeeds. GitHub Releases and GHCR are
the distribution channels; this release does not publish a PyPI package.
Follow host setup
using the exact published tooling/image hashes
and the recorded registry digest, rather than a mutable latest image tag.
Component sources and license notices
The image includes components under their own licenses. The MIT license for
this project's server and tooling does not replace those terms.
- The release's hash-verified components.json
is provided beside the image archive. For each Debian binary it identifies
the exact source package/version, versionedsources.debian.orgsource tree,
retained copyright file andapt-get source PACKAGE=SOURCE_VERSIONcommand.
Use the versioned source link or a Debian repository with source indexes
enabled for that exact version; do not substitute the current package version. - The bundled Ada Language Server is upstream
2026.3.202607051. Its
source commit,
annotated tag and dependency revisions,
tagged build instructions
and dependency acquisition/build script
provide the upstream source and external dependency acquisition route.
Follow the annotated dependency inventory and build instructions, including
the external repositories and Alire dependencies fetched by the build script.
GitHub's automatic ALS source archive alone does not include those external
checkouts. The component index also links Python package source distributions. - Original notices remain in the image under
/usr/share/doc, the installed
Python distributions and/usr/share/licenses/ada-language-server.
Corresponding sources are offered through these upstream servers with clear
directions beside the object-code download, as permitted by GPL section 6(d).
The abuild-project maintainers remain responsible for keeping the required
source route available; a release checksum identifies bytes and is not a
replacement for source access or license terms.