# Give coding agents the same contract as developers

Give a coding agent version-matched Kam guidance for an AgentCore project. Local read-only MCP tools do not become deployed agent tools or a Gateway integration.

Status: Merged · local only. Prelaunch; not a live service guarantee.
Native toolkit 0.1.0 is merged into the backend (PR #176) and qualified in CI as a network-disabled Linux x64 artifact. No public binary release, macOS/Windows distribution, or live AWS connection is offered here.

Reviewed: 2026-10-14.
Backend source: e16b81b4a637acec91f3aed8a71cf5b0f42f0c19.
Native toolkit: merged in PR #176, reviewed at e16b81b4a637acec91f3aed8a71cf5b0f42f0c19.
HTML: /docs/agent-tooling

## In short

Give a coding agent the same Kam contract a developer reads when building an AgentCore application. Version-matched guides and five local read-only MCP tools explain State and its limits. Connecting those development tools does not register tools with the deployed agent.

**Available today:** Website Markdown is available. Local MCP tools are part of the merged toolkit; managed AgentCore integration and public distribution remain separate.

> Help coding agents build an AgentCore State integration using the same documented contract.

## Give the coding agent the right tools

- **Read the same contract** — Use version-matched Markdown when planning the AgentCore State integration.
- **Inspect locally** — The documented MCP tools read bounded local evidence; they do not execute agents.
- **Authorize remote reads separately** — History access needs its own approved identity and service connection.

## Five tools, not a shell proxy

The server uses stdio with initialization and bounded framing, not a public TCP endpoint. Unknown, null, cross-tool, write, shell, and arbitrary-path arguments fail before project reads.

1. **kam_project_status** — Local configuration and generated-file drift. No live account or IAM check.

2. **kam_view_manifest** — A normalized manifest and configuration fingerprint, not deployed authority.

3. **kam_replay_fixture** — Re-evaluate supplied synthetic scenarios with the real Rust engine, without executing an agent.

4. **kam_reference_atlas** — Selected-reference JSON bytes and explicit omissions, not model-token counts.

5. **kam_docs** — Bundled version-matched documentation.

## Generated instructions are reviewable local files

Generation produces versioned Markdown, llms.txt, llms-full.txt, skills, and a managed AGENTS.md block. Surrounding customer instructions are preserved. Edits to managed content and concurrent source changes are detected.

Generating guidance does not install packages, activate an agent configuration, or register a GitHub workflow. The customer reviews the proposed artifacts and explicitly chooses integration steps.

## Read these website guides as Markdown

Each public guide has a Markdown equivalent generated from the same typed content as the HTML page. The documentation manifest lists both addresses. Availability labels and reviewed source identities are included; unpublished tools are not presented as installed services.

[Agent-readable index](/llms.txt)

[All guides in one document](/llms-full.txt)