ACR — Agent Composition Records
Hook your agent into Tethral ACR under the TethralAI registry id to log sessions and fetch behavioral lenses for composed assistants.
Overview
TethralAI ACR MCP is a Build-phase MCP server for logging agent interactions and querying behavioral lenses via Agent Composition Records.
What is this MCP server?
- Same ACR product: interaction profiles plus behavioral lens queries
- TethralAI registry entry @tethral/acr-mcp v2.1.1 (stdio)
- Configurable ACR_API_URL with default https://acr.nfkey.ai
- Suited for Claude Code and Cursor MCP manifests
- Repository source: Tethral-Inc/AgentRegistry on GitHub
- MCP server version 2.1.1
- npm package @tethral/acr-mcp
- Website https://acr.nfkey.ai
Community signal: 1 GitHub stars.
What problem does it solve?
Without a composition registry, solo builders cannot reliably reuse or audit how their agents were configured across tools and releases.
Who is it for?
Builders whose MCP config or docs already point at io.github.TethralAI/acr and who want hosted ACR without self-hosting the registry.
Skip if: Teams requiring the newest ACR MCP pin who should prefer the Tethral-Inc listing at v2.4.1, or users avoiding external agent registries.
What do I get? / Deliverables
Installing this MCP entry lets your agent persist interactions to ACR and retrieve lenses so composition intent survives beyond one conversation.
- ACR-backed interaction logs from agent tool calls
- Behavioral lens payloads for prompt and policy alignment
- Documented MCP endpoint matching TethralAI catalog id
Recommended MCP Servers
Journey fit
Composition record tooling lands in build when you wire MCP, but pays off again in operate when you audit how agents behaved in the wild. Agent-tooling subphase catalogs MCP bridges to registries like ACR that are not single-purpose API wrappers.
How it compares
Alternate MCP registry slug for the same ACR service—not a different protocol from Tethral-Inc/acr, and not a local skill file.
Common Questions / FAQ
Who is TethralAI ACR MCP for?
Solo builders linking agents to Tethral ACR when their install path uses the TethralAI GitHub MCP name rather than Tethral-Inc.
When should I use TethralAI ACR MCP?
Use it while building agent integrations and when you need logged interactions and lenses from the hosted ACR API during iteration.
How do I add TethralAI ACR MCP to my agent?
Configure stdio MCP with @tethral/acr-mcp, set ACR_API_URL if needed, add the server block under io.github.TethralAI/acr in your client, and reload.