Utilizes Python as the runtime environment with specific version requirements (>=3.10)
Tecton MCP Server & Cursor Rules
Tecton's Co-Pilot consists of an MCP Server and Cursor rules. Read this blog to learn much more.
ℹ️ Info: This guide will walk you through setting up the Tecton MCP server with this repository and configuring your feature repository to use it while developing features with Tecton.
Table of Contents
- Quick Start
- Tecton MCP Tools
- Architecture
- Setup Tecton with Cursor
- How to Use Specific Tecton SDK Version
- Troubleshooting
- Resources
Quick Start
- Clone this repository to your local machine:Note: The path to the directory where you just cloned the repository will be referred to as
<path-to-your-local-clone>
in the following steps. Thepwd
command in the end will tell you what the full path is. - Install the uv package manager:
- Verify your installation by running the following command. Replace
<path-to-your-local-clone>
with the path where you cloned the repository in step 1:The command should exit without any errors and print a message similar toMCP_SMOKE_TEST is set. Exiting after initialization.
. This confirms that your local setup works correctly—Cursor will automatically spawn the MCP server as a subprocess when needed. - Configure Cursor (or any other MCP client) with the MCP server (see below)
- Log into your Tecton cluster:
- Launch Cursor and start developing features with Tecton's Co-Pilot in Cursor!
Tecton MCP Tools
The Tecton MCP server exposes the following tools that can be used by an MCP client (like Cursor):
Tool Name | Description |
---|---|
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. |
Architecture
The Tecton MCP integrates with LLM-powered editors like Cursor to provide tool-based context and assistance for feature engineering:
The overall flow for building features with Tecton MCP looks like:
Setup Tecton with Cursor
The following is tested with Cursor 0.48 and above
Configure the Tecton MCP Server in Cursor
Navigate to Cursor Settings -> MCP and click the "Add new global MCP server" button, which will edit Cursor's mcp.json
file.
Add Tecton as an MCP server. You can use the following config as a starting point - make sure you modify the path <path-to-your-local-clone>
to match the directory where you cloned the repository:
Add Cursor rules
Copy the cursorrules from this repository's .cursor/rules
folder into the .cursor/rules
folder of your feature repository:
Tecton Login
Log into your Tecton cluster:
Recommended LLM
As of April 17th, the following is the stack ranked list of best performing Tecton feature engineering LLMs in Cursor:
- OpenAI o3
- Gemini 2.5 pro exp (03-25)
- Sonnet 3.7
Verify that the Cursor <> Tecton MCP Integration is working as expected
To make sure that your integration works as expected, ask the Cursor Agent a question like the following and make sure it's properly invoking your Tecton MCP tools:
Query Tecton's Examples Index and tell me something about BatchFeatureViews and how they differ from StreamFeatureViews. Also look at the SDK Reference.
Start AI-Assisted Feature Engineering :-)
Now you can go to your Feature Repository in Cursor and start using Tecton's Co-Pilot - directly integrated in Cursor.
View this Loom to see how you can use the integration to build new features: https://www.loom.com/share/3658f665668a41d2b0ea2355b433c616
How to Use Specific Tecton SDK Version
By default, this tool provides guidance for the latest pre-release of the Tecton SDK. If you need the tools to align with a specific released version of Tecton (for example 1.0.34
or 1.1.10
), follow these steps:
- Pin the version in
pyproject.toml
. Openpyproject.toml
and replace the existing dependency line
with the exact version you want, e.g.
- Remove the existing lock-file. Because
uv.lock
records the dependency graph, you must delete it so thatuv
can resolve the new Tecton version:
- Re-generate the lock-file by re-running Step 3 (the
MCP_SMOKE_TEST=1 uv --directory
command) of the Quick Start section. (This will download the pinned version into an isolated environment for MCP and re-createuv.lock
.) - Restart Cursor so that the new Tecton version is loaded into the MCP virtual environment.
Supported versions: The tools currently support Tecton ≥ 1.0.0. Code examples are not versioned yet – they always use the latest stable SDK – however the documentation and SDK reference indices will now match the version you've pinned.
Troubleshooting
Cursor <-> Tecton MCP Server integration
Make sure that Cursor shows "tecton" as an "Enabled" MCP server in "Cursor Settings -> MCP". If you don't see a "green dot", run the MCP server in Diagnostics mode (see below)
Run MCP in Diagnostics Mode
To debug the Tecton MCP Server you can run the following command. Replace <path-to-your-local-clone>
with the actual path where you cloned the repository:
Note: Launching Tecton's MCP Server will take a few seconds because it's loading an embedding model into memory that it uses to search for relevant code snippets.
Wait a few seconds until the stdout tells you that the MCP Inspector is up and running and then access it at the printed URL (something like http://localhost:5173)
Click "Connect" and then list tools. You should see the Tecton MCP Server tools and be able to query them.
Resources
License
This project is licensed under the MIT License.
This server cannot be installed
hybrid server
The server is able to function both locally and remotely, depending on the configuration or use case.
Provides a set of tools to interact with Tecton clusters, manage feature stores, and execute Tecton CLI commands through the Mission Control Protocol.
- Table of Contents
- Quick Start
- Tecton MCP Tools
- Architecture
- Setup Tecton with Cursor
- How to Use Specific Tecton SDK Version
- Troubleshooting
- Resources
- License
Related Resources
Related MCP Servers
- -securityFlicense-qualityThe cosense-mcp-server facilitates the integration with Claude Desktop by serving as a middleware command pipeline server, allowing for interaction with projects in cosense.Last updated -73TypeScript
- AsecurityFlicenseAqualityA powerful Model Context Protocol (MCP) server enabling seamless Vercel project management, including deployments, domains, environment variables, and team configurations through Cursor's Composer or Codeium's Cascade.Last updated -6517TypeScript
- -securityAlicense-quality🌍 Terraform Model Context Protocol (MCP) Tool - An experimental CLI tool that enables AI assistants to manage and operate Terraform environments. Supports reading Terraform configurations, analyzing plans, applying configurations, and managing state with Claude Desktop integration. ⚡️Last updated -292RustMIT License
- AsecurityFlicenseAqualityExposes Salesforce CLI functionality to LLM tools like Claude Desktop, allowing AI agents to execute Salesforce commands, manage orgs, deploy code, and query data through natural language.Last updated -57228JavaScript