Official description๐ ๐ ๐ ๐ช ๐ง - Model Context Protocol server that integrates with Tilt to provide programmatic access to Tilt resources, logs, and management operations for Kubernetes development environments.
Config template (adjust for your client)
claude mcp add tilt-mcp -- npx -y tilt-mcp
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
6 โ ยท rrmistry/tilt-mcp ยท read from the repository page ยท (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list ยท type: MCP server
Harvest history
first seen 2026-10-09 ยท last seen 2026-10-16 ยท seen 32ร ยท listed by 10 sources
Score
score 1,003 ยท 6 โ ยท 10 sources ยท mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP ๆๅก. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository rrmistry/tilt-mcp๏ผfirst catalogued 2026-10-09๏ผlast seen 2026-10-16ใThere is no official certification or quality rating here โ we record sources and dates only.
A Model Context Protocol (MCP) server that integrates with Tilt to provide programmatic access to Tilt resources and logs through LLM applications. Why use a Tilt MCP server? Imagine prompting like this: > Please work on {some LLM request} and then check tilt MCP for "backend-api" resource logs for compile status. Make sure that "backend-tests" resource is successful with your changes. The key insight is you no longer need to tell your LLM _how_ to build and deploy your code. Instead, you can simply ask it to _what_ to build and deploy. Tilt is a powerful tool for working with Docker/Kubernetes workloads. With the Tilt MCP server, you can integrate Tilt's features directly into your workflow using Large Language Models (LLMs) like Claude Code / Codex / Gemini / VS Code Copilot / etc. This saves significant LLM tokens (and so โฑ๏ธ+๐ฐ), both by avoiding to give extra context to your LLM on how to build/deploy, and also by avoiding LLMs actually doing the build/deploy. All the LLM needs to know is to make code changes then call the tilt MCP server to get real-time feedback. Overview The Tilt MCP server allows Large Language Models (LLMs) and AI assistants to interact with your Tilt development environment. It provides tools to: - List all enabled Tilt resources - Fetch logs from specific resources - Monitor resource status and health - Enable and disable resources dynamically - Get detailed information about resources - Trigger resource rebuilds - Wait for resources to reach specific conditions This enables AI-powered development workflows, debugging assistance, automated monitoring, and intelligent resource management of your Tilt-managed services. Available MCP Capabilities The Tilt MCP server follows the Model Context Protocol specification and exposes three types of capabilities: ๐ Resources (Read-Only Data) Resources provide read-only access to Tilt data. They're automatically discovered by MCP clients and can be accessed via their URI. | Resource URI | Description | |--------------|-------------| | tilt://resources/all{?tilt_port} | List of all enabled Tilt resources with their current status | | tilt://resources/{resource_name}/logs{?tail,filter,tilt_port} | Logs from a specific resource with optional regex filtering (case-insensitive by default) | | tilt://resources/{resource_name}/describe{?tilt_port} | Detailed information about a specific resource | All resources support an optional tilt_port parameter (default: 10350) to query different Tilt instances. **Example URIs:** - tilt://resources/all - Get all resources from default port (10350) - tilt://resources/all?tilt_port=10351 - Get all resources from port 10351 - tilt://resources/frontend/logs - Get last 1000 lines from frontend (default) - tilt://resources/frontend/logs?tail=100&tilt_port=10351 - Get last 100 lines from frontend on port 10351 - tilt://resources/backend/logs?filter=error - Filter logs for errors (case-insensitive) - tilt://resources/backend/logs?filter=X-Request-Id:%20abc123 - Filter by request ID - tilt://resources/backend/describe - Get detailed info about backend ๐ ๏ธ Tools (Actions with Side Effects) Tools enable LLMs to perform actions that modify the state of your Tilt environment. | Tool | Description | Parameters | |------|-------------|------------| | trigger_resource | Triggers a Tilt resource to rebuild/update | resource_name (required), tilt_port (optional, default: '10350') | | enable_resource | Enables one or more Tilt resources | resource_names (required, list), enable_only (optional, default: false), tilt_port (optional, default: '10350') | | disable_resource | Disables one or more Tilt resources | resource_names (required, list), tilt_port (optional, default: '10350') | | wait_for_resource | Wait for a resource to reach a specific condition | resource_name (required), condition (optional, default: 'Ready', valid values: 'Ready' or 'UpToDate'), timeout_seconds (optional, default: 30), tilt_port (optional, default: '10350') | **Read-Only Tools** (for clients that don't support MCP Resources): | Tool | Description | Parameters | |------|-------------|------------| | list_resources | List all enabled Tilt resources with their status | tilt_port (optional, default: '10350') |