A Model Context Protocol (MCP) server that integrates with [Tilt](https://tilt.dev/) to provide programmatic access to Tilt resources and logs
A Model Context Protocol (MCP) server that integrates with Tilt to provide programmatic access to Tilt resources and logs through LLM applications. Exposed over MCP by the tilt mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
The Tilt MCP server allows Large Language Models (LLMs) and AI assistants to interact with your Tilt development environment. It provides tools to:
The server ships on PyPI as tilt-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Everything the assistant can do here goes through one of these:
trigger_resource — Triggers a Tilt resource to rebuild/updateenable_resource — Enables one or more Tilt resourcesdisable_resource — Disables one or more Tilt resourceswait_for_resource — Wait for a resource to reach a specific conditionlist_resources — List all enabled Tilt resources with their statusget_resource_logs — Get logs from a specific resource with optional regex filteringdescribe_resource — Get detailed information about a specific resourceYou will need 2 environment variables: LOG_LEVEL, TILT_HOST. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Tilt MCP's toolset — trigger_resource, enable_resource, disable_resource and 4 more — is a fair guide to whether it matches your workflow. It is maintained by rrmistry; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| trigger_resource | Triggers a Tilt resource to rebuild/update |
| enable_resource | Enables one or more Tilt resources |
| disable_resource | Disables one or more Tilt resources |
| wait_for_resource | Wait for a resource to reach a specific condition |
| list_resources | List all enabled Tilt resources with their status |
| get_resource_logs | Get logs from a specific resource with optional regex filtering |
| describe_resource | Get detailed information about a specific resource |
{
"mcpServers": {
"tilt": {
"command": "tilt-mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LOG_LEVEL | Configuration value read at startup. | Optional |
| TILT_HOST | Endpoint or connection string the server talks to. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.