Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Always-on AI agents: a software factory for Claude Code, or an AI SRE that watches your systems.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
TARESD_URL, TARES_AUTH_TOKENValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"tares": {
"command": "uvx",
"args": [
"tares",
"mcp",
"--transport",
"stdio"
],
"env": {
"TARESD_URL": "your-value",
"TARES_AUTH_TOKEN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add tares --env TARESD_URL=your-value --env TARES_AUTH_TOKEN=your-value -- uvx tares mcp --transport stdioFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"tares": {
"command": "uvx",
"args": [
"tares",
"mcp",
"--transport",
"stdio"
],
"env": {
"TARESD_URL": "your-value",
"TARES_AUTH_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"tares": {
"type": "stdio",
"command": "uvx",
"args": [
"tares",
"mcp",
"--transport",
"stdio"
],
"env": {
"TARESD_URL": "your-value",
"TARES_AUTH_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
TARESD_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain glassflow.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: TARES_AUTH_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.55.1) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The open-source platform for always-on AI agents.
Most agents wait for a prompt and forget everything when the session ends. Tares gives agents a place to work from: events from your systems land on one timeline per thing, agents wake when something happens, and what they decide (findings, plans, tickets, reviews, your answers) is kept for the next reader, human or agent. Works with Claude Code, Cursor, Codex and your own agents over MCP.
Connect anything that emits events: logs, metrics, alerts, deploys, commits, database rows, webhooks. Tares merges them into one time-ordered timeline per service, repo, customer or job, and a trigger wakes an agent the moment something matters, with that timeline already in hand. The agent writes its conclusion back onto the timeline.
One crew of Claude Code sessions on your machine builds every project you hand it. You plan a project with Claude; an orchestrator hands out the tickets, builders open pull requests, a reviewer holds every change to a fixed bar, and builders merge once it passes and CI is green. You talk to one session, and only for decisions that are yours.
→ Software factory, A project, end to end
uv tool install tares # or: brew install glassflow/tap/tares
tares up # daemon + console on http://127.0.0.1:8787 tares mcp --transport streamable-http # in a second terminal: the MCP endpoint, :8788/mcp
Then pick what you came for.
Give an agent your systems. Add a source under Sources → Add source in the console (or start the demo stack to break something on purpose), and connect your agent:
claude mcp add --transport http tares http://localhost:8788/mcp
Ask it: *"Use tares: what happened to api-server in the last 15 minutes?"* → Quickstart
Build software with a crew. Needs Claude Code (signed in, on a plan with background sessions) and gh with write access to your repos:
tares factory crew up # start the crew; the first run asks how far it may go
tares factory spec "what you want to build" # in your repo: plan the project and hand it over tares factory crew attach orchestrator # answer the crew's questions
Watch it on the Crew page of the console. → Software factory
Prefer not to run it yourself? [Tares Cloud](https://console.tares-glassflow.com/) is the managed version, with the MCP endpoint already running.
| Concepts | sources, timelines, triggers, agents and projects |
| Connectors | Prometheus, OTLP, GitHub, Vercel, Postgres, webhooks, Claude Code sessions and more |
| Agents | connect any MCP client, or run Tares agents on a trigger |
| Software factory | the crew, its commands, and a project from spec to merged |
| Deployment | Docker, servers, TLS and auth |
| AI resources | for coding assistants: Markdown endpoints and instructions to paste |
Bug reports and ideas are welcome via GitHub issues or help@glassflow.ai.
MIT. This licence covers everything in this repository except directories named ee, which are under the licence in ee/LICENSE.