The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Tetrees AI listing page.
Public integration kit for using, growing, buying, and publishing Tetrees AI Packs through the hosted Tetrees Agent MCP and API.
Explore Tetrees AI Packs · Connect through MCP · Publish an AI Pack
This repository is the public @tetrees/mcp product (ai.tetrees/mcp): the stdio MCP server, clients, configuration examples, and safe extension samples. It does not contain Tetrees Agent internals, private Pack intelligence, Agent AVCP scoring, service prompts, storage, moderation, or exchange infrastructure.
| Path | Use this kit to |
|---|---|
| Buyer / operator | Search Packs, inspect the public Agent AVCP report, quote a run, try a Pack with Tetrees Points, acquire a free Pack, and download an owned .taip release. |
| Builder | Connect an auditioned Pack to a user-owned HTTPS API, nested MCP server, or no-shell local skill while keeping credentials local. |
| Seller | Create a listing, upload an immutable .taip version and images, inspect readiness, run Agent AVCP, read private repair feedback, and publish a passing release. |
Tetrees-hosted work needs no local GPU. Model-funded runs are quoted in Tetrees Points before execution; an owned Pack can also use a supported provider key supplied to the local MCP process.
Requirements: Node.js 20+ and a revocable API token from Tetrees Account.
Add this to your MCP client's configuration:
Restart the MCP client, then ask it to:
Do not put provider keys in a Pack, prompt, source file, or shared MCP config. Optional BYOK keys belong only in the local MCP process environment. See examples/mcp/mcp-config.jsonc.
The inspector launches the official hosted MCP package, lists its public tools and resources, checks the expected buyer/builder/seller surface, and exits without spending Points or changing account state.
The v=2.2.1 suffix is intentional: it prevents npx from reusing an older MCP tarball cached under the same URL. Change it only when Tetrees publishes a newer MCP contract. The npm identity for the same package is @tetrees/mcp@2.2.1.
Copy .env.example values into your shell; this project deliberately does not auto-load secret files.
The CLI redacts secret-shaped response fields and reports Tetrees error codes, HTTP status, and Retry-After. It does not retry a mutation automatically.
Run the documented read-only example:
A published Pack may declare client extensions that passed Agent AVCP. The actual binding and credentials remain on the user's machine.
Supported binding patterns:
https_api: fixed HTTPS base URL, declared methods, environment-backed headers.mcp: a nested MCP server started without a shell and mapped to declared tool names.local_skill: a no-shell child process receiving one JSON request and returning one JSON result.Start with:
examples/extensions/client-extensions.example.jsonexamples/extensions/local-skill/issue-summary.mjsdocs/BUILDER_GUIDE.mdTetrees hosting never inherits these local permissions. A write method needs the exact per-call phrase APPROVE extensionId.methodId.
The supported publisher path is intentionally contract-driven:
Then use the hosted MCP tools or Tetrees API reference to submit, quote Agent AVCP, run it after confirming the exact Point amount, inspect the private report, and publish only the passing digest.
See docs/SELLER_GUIDE.md and examples/seller/pack-listing.example.json.
This repository does not contain:
The examples operate only through the documented public, authenticated contract. Review SECURITY.md and docs/PUBLIC_BOUNDARY.md before contributing.
The client examples and documentation in this repository are MIT licensed. Tetrees, Tetrees Agent, Tetrees AI Pack, TAIP, and Agent AVCP names and service marks remain the property of Tetrees EX. The license does not grant access to, or rights in, the hosted service or private Pack intelligence.