Summary

Feature code written against the real SDK, not a recollection.

The two indexes do most of the work — find a usage pattern, then confirm the signature — so the assistant writes Tecton code the way the docs say rather than the way it remembers. The metrics tool only appears once an API key is configured.

What it is

A retrieval layer over Tecton's own material for coding assistants: an example-code index, a documentation index, the SDK reference whole or by symbol, and a live metrics query.

What you get

Tecton code examples found by vector search, for the pattern you are about to write
Documentation snippets retrieved for a question, straight from the official docs
The complete Tecton SDK reference, all classes and functions
The reference for a named list of classes or functions
Point-in-time system metrics, human-readable or as raw OpenMetrics

Requirements

A Tecton feature repository to work in. Setting an API key in the server's environment registers the API-backed tools, including the metrics query.

Setup effort

One command plus a key — claude mcp add-json tecton-mcp '{ "command": "uv", "args": [ "--directory", "<path-to-local-clone>", "run", "mcp", "run", "src/tecton_mcp/mcp_server/server.py" ] }', then supply credentials