Deep Agentic Core MCP changelog

https://raw.githubusercontent.com/deepagentlabs/mcp-server/HEAD/AGENTS.md

− Keep the remaining local roadmap phases on minor versions. Reserve v1.0 for− one coordinated ecosystem release after each project's acceptance and− compatibility gates pass. Follow the current minor target in ROADMAP.md and− [the shared release policy](https://github.com/DeepAgentLabs/.github/blob/main/profile/RELEASE_POLICY.md).− A documentation-only roadmap update does not bump package metadata or publish− a new package release. Schema versions remain independent of package versions.+ The maintainer authorized 1.0.0 as a coordinated milestone with outstanding+ validation disclosed. Preserve draft/candidate schema labels and track remaining+ acceptance work on the roadmap. Follow the updated+ [shared release policy](https://github.com/DeepAgentLabs/.github/blob/main/profile/RELEASE_POLICY.md).+ Schema versions remain independent of package versions.

version

1.0.0 → 1.0.3

version

0.8.0 → 1.0.0

https://raw.githubusercontent.com/deepagentlabs/mcp-server/HEAD/AGENTS.md

− export) in `0.4.0`. Phase 5 is in progress; its open work is hosted access− control: tool-level permissions, revocation at dispatch, authenticated− stop/revoke, correlated denial evidence and hosted Tower credentials. Unified tools must stay compositions: delegate judgement to the− recipes include Sidecar 0.9.0 for package discovery, with no live runtime bridge.+ export) in `0.4.0`. Phase 5 is complete as of `0.5.0`: per-key tool policies+ are enforced at dispatch (`services/access_policy.py`), the key and policy are+ re-checked after the session lock, and calls leave correlated+ `mcp.access-decision.v1` evidence (`services/access_evidence.py`). Phase 6 (0.6.0) binds hosted Tower credentials per user, bridges live+ Sidecar stop/revoke with independent operator auth and adds the spec-owned+ exploratory access extension. Paired Chaos 0.10 assertions authenticate observations+ with Lens. Read docs/phase6-containment.md before changing these boundaries. Any new hosted dispatch path must go through the authorizer. Unified tools must stay compositions: delegate judgement to the+ The v0.7 integration-readiness milestone adds `core.compatibility` and a packaged+ candidate matrix in `resources/compatibility.json`. Keep it aligned with image+ pins and CI using `tests/test_readiness_matrix.py`. It reports distribution+ metadata only, not imported-source or live-host acceptance. The built-wheel+ stdio protocol smoke runs without optional siblings. See docs/release-readiness.md.+ - Operator console script: `deep-agentic-core-mcp-admin` → `admin.py:main()` (key policies, revocation)+ recipes include Sidecar 0.9.2; a live runtime bridge requires explicit host bindings.+ ## Coordinated major release policy+ Keep the remaining local roadmap phases on minor versions. Reserve v1.0 for+ one coordinated ecosystem release after each project's acceptance and+ compatibility gates pass. Follow the current minor target in ROADMAP.md and+ [the shared release policy](https://github.com/DeepAgentLabs/.github/blob/main/profile/RELEASE_POLICY.md).+ A documentation-only roadmap update does not bump package metadata or publish+ a new package release. Schema versions remain independent of package versions.

version

0.7.0 → 0.8.0

version

0.6.3 → 0.7.0

version

0.4.1 → 0.6.3

https://raw.githubusercontent.com/deepagentlabs/mcp-server/HEAD/AGENTS.md

− routing and rule-cited conformance) is complete as of `0.3.3`. The next major− work is Phase 4: unified observability-plus-chaos workflows and the first− Control Tower connector. Changes here should strengthen composition and interoperability, not−   checks, PyPI publication, GitHub Release, MCP Registry publication, and AWS−   deployment. AWS depends on successful PyPI publication and deploys the tagged−   source using an immutable image. Infrastructure changes use the operator flow.− - deploys the tagged source to AWS after PyPI publication succeeds+ routing and rule-cited conformance) is complete as of `0.3.3`. Phase 4 is+ complete: the local Control Tower connector shipped in `0.3.6` and the unified+ `core.*` workflow tools (fail-closed release check, incident summary, report+ export) in `0.4.0`. Phase 5 is in progress; its open work is hosted access+ control: tool-level permissions, revocation at dispatch, authenticated+ stop/revoke, correlated denial evidence and hosted Tower credentials. Unified tools must stay compositions: delegate judgement to the+ sibling that owns it (Evals gate, Lens comparison, Chaos report) and fail+ closed on missing or invalid evidence. Changes here should strengthen composition and interoperability, not+   checks, PyPI publication, GitHub Release, MCP Registry publication. AWS deployment is manual from 0.4.1. Infrastructure changes use the operator flow.+ - leaves AWS deployment to an explicit manual operator action+ ## Release pipeline from 0.4.1+ Tag releases validate, publish PyPI/GitHub Release and publish the MCP Registry.+ Automatic AWS deployment is removed from GitHub Actions. Existing AWS build and+ operator deployment scripts remain available for an explicit manual deployment;+ publishing a package does not update the running AWS service. Standalone image+ recipes include Sidecar 0.9.0 for package discovery, with no live runtime bridge.

version

0.3.14 → 0.4.1

version

0.3.13 → 0.3.14

version

0.3.11 → 0.3.13

version

0.3.9 → 0.3.11

version

0.3.7 → 0.3.9

version

0.3.5 → 0.3.7

https://raw.githubusercontent.com/deepagentlabs/mcp-server/HEAD/AGENTS.md

− The next major work is provenance verification on `lens.analyze_workflow`,− multi-version AIOS schema support, and more unified observability-plus-chaos− workflows. Changes here should strengthen composition and interoperability, not+ Phase 3 (lens provenance, chaos AIOS export and script policy, spec_version+ routing and rule-cited conformance) is complete as of `0.3.3`. The next major+ work is Phase 4: unified observability-plus-chaos workflows and the first+ Control Tower connector. Changes here should strengthen composition and interoperability, not

version

0.3.4 → 0.3.5

version

0.3.2 → 0.3.4

version

0.3.1 → 0.3.2

version

0.3.0 → 0.3.1

https://raw.githubusercontent.com/deepagentlabs/mcp-server/HEAD/AGENTS.md

− - Server boot: `run_server()` → `stdio_server()` → `server.run()`− `CHANGELOG.md` (a dated release section under `[Unreleased]`). Commit as+ - Local server boot: `run_server()` → `stdio_server()` → `server.run()`+ - HTTP console script: `deep-agentic-core-mcp-http` → `transport_http.py:main()`+ - Hosted signup and key lifecycle: `signup.py`, backed by DynamoDB+ ## Local and Hosted Deployment Contract+ Maintain both transports in this repository. The base PyPI package provides+ local stdio; the optional `http` extra adds hosted Streamable HTTP dependencies.+ HTTP/signup support is included from `0.3.0`; PyPI `0.2.0` provides local stdio.+ HTTP requires bearer authentication and Redis-backed user-scoped workflow state.+ The AWS deployment uses DynamoDB for user records and hashed keys. HTTP always+ rejects `chaos.run_experiment`; local stdio retains trusted local execution.+ Test transport-specific authorization and state isolation when changing dispatch.+ - Pull requests, pushes to `main`, and manual CI runs perform checks and package+   builds without deploying AWS or publishing to PyPI.+ - Pushing a `v*` tag runs `release-pypi.yml`: the full test matrix and packaging+   checks, PyPI publication, GitHub Release, MCP Registry publication, and AWS+   deployment. AWS depends on successful PyPI publication and deploys the tagged+   source using an immutable image. Infrastructure changes use the operator flow.+ - Prepare matching versions in `pyproject.toml`, `__init__.py`, `server.json`,+   and `uv.lock`, plus dated changelog notes, before pushing the release tag.+ - Keep Docker files under `deploy/docker/` and infrastructure under `deploy/aws/`.+   Keep credentials and local deployment state out of Git. Document configuration+   in [deploy/aws/CI-CD.md](deploy/aws/CI-CD.md) and client behavior in+   [docs/user-guide.md](docs/user-guide.md).+ `server.json`, `uv.lock`, and `CHANGELOG.md` (a dated release section under+ `[Unreleased]`). Commit as+ - deploys the tagged source to AWS after PyPI publication succeeds

version

0.2.0 → 0.3.0