Tecton MCP Server

Tecton MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Tecton's Co-Pilot consists of an MCP Server rules for MCP clients such as Cursor and Claude Code. Read this blog to learn much more.

What the assistant can call

Once Tecton MCP is connected, these are the calls the assistant has available:

• query_example_code_snippet_index_tool — Finds relevant Tecton code examples using a vector database. Helpful for finding usage patterns before writing new Tecton code
• query_documentation_index_tool — Retrieves Tecton documentation snippets based on a query. Provides context directly from Tecton's official documentation
• get_full_tecton_sdk_reference_tool — Fetches the complete Tecton SDK reference, including all available classes and functions. Use when a broad overview of the SDK is needed
• query_tecton_sdk_reference_tool — Fetches the Tecton SDK reference for a specified list of classes or functions. Ideal for targeted information on specific SDK components
• query_tecton_metrics_tool — Queries the Tecton Metrics API. Returns point-in-time system metrics in human-readable or raw OpenMetrics format
• Prerequisits — The Prerequisits tool exposed by this server
• Configuration — Navigate to Augment -> Settings -> Tools -> MCP -> Import from JSON, and import the following configuration(updating to the

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need one environment variable: TECTON_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

1. Install the uv package manager:

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Tecton MCP's toolset — query_example_code_snippet_index_tool, query_documentation_index_tool, get_full_tecton_sdk_reference_tool and 4 more — is a fair guide to whether it matches your workflow. It is maintained by tecton-ai; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the tecton mcp mcp server does with a few real requests.