Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
YouTrack with your login and password: the built-in tools plus deletes, sprints, history and reports
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.
YOUTRACK_URL, YOUTRACK_LOGIN, YOUTRACK_PASSWORD, YOUTRACK_PROXY, YMCP_TOOLSValues 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": {
"ymcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"YOUTRACK_URL",
"-e",
"YOUTRACK_LOGIN",
"-e",
"YOUTRACK_PASSWORD",
"-e",
"YOUTRACK_PROXY",
"-e",
"YMCP_TOOLS",
"docker.io/xlsoftware/ymcp:0.27.0",
"serve"
],
"env": {
"YOUTRACK_URL": "your-value",
"YOUTRACK_LOGIN": "your-value",
"YOUTRACK_PASSWORD": "your-value",
"YOUTRACK_PROXY": "your-value",
"YMCP_TOOLS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add ymcp --env YOUTRACK_URL=your-value --env YOUTRACK_LOGIN=your-value --env YOUTRACK_PASSWORD=your-value --env YOUTRACK_PROXY=your-value --env YMCP_TOOLS=your-value -- docker run -i --rm -e YOUTRACK_URL -e YOUTRACK_LOGIN -e YOUTRACK_PASSWORD -e YOUTRACK_PROXY -e YMCP_TOOLS docker.io/xlsoftware/ymcp:0.27.0 serveFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ymcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"YOUTRACK_URL",
"-e",
"YOUTRACK_LOGIN",
"-e",
"YOUTRACK_PASSWORD",
"-e",
"YOUTRACK_PROXY",
"-e",
"YMCP_TOOLS",
"docker.io/xlsoftware/ymcp:0.27.0",
"serve"
],
"env": {
"YOUTRACK_URL": "your-value",
"YOUTRACK_LOGIN": "your-value",
"YOUTRACK_PASSWORD": "your-value",
"YOUTRACK_PROXY": "your-value",
"YMCP_TOOLS": "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": {
"ymcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"YOUTRACK_URL",
"-e",
"YOUTRACK_LOGIN",
"-e",
"YOUTRACK_PASSWORD",
"-e",
"YOUTRACK_PROXY",
"-e",
"YMCP_TOOLS",
"docker.io/xlsoftware/ymcp:0.27.0",
"serve"
],
"env": {
"YOUTRACK_URL": "your-value",
"YOUTRACK_LOGIN": "your-value",
"YOUTRACK_PASSWORD": "your-value",
"YOUTRACK_PROXY": "your-value",
"YMCP_TOOLS": "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.
YOUTRACK_PROXY envYMCP_TOOLS 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 6, 2026
The registry name was verified with the GitHub account xlsft, which owns the repo
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: YOUTRACK_URL, YOUTRACK_LOGIN, YOUTRACK_PASSWORD
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 (0.27.0) reached the registry 8 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, topo^alpin
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.
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
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.
ymcp is a local toolchain for project work in YouTrack, including self-hosted instances behind a VPN. It has two parts: an MCP server for any AI client, and pipelines that hand issues to coding agents.
The MCP server speaks for you with your login and password, ships every tool of YouTrack’s built-in MCP server under the same names, and adds the ones it lacks: deleting things, sprints, attachments, history, time reports, commands and more.
ymcp update built inPipelines take the issues a YouTrack search finds and give each one to a coding agent on its own branch.
macOS / Linux:
curl -fsSL https://raw.githubusercontent.com/xlsft/ymcp/main/install.sh | sh
Windows (PowerShell):
irm https://raw.githubusercontent.com/xlsft/ymcp/main/install.ps1 | iex
A given release instead of the latest, say to go back to it:
curl -fsSL https://raw.githubusercontent.com/xlsft/ymcp/main/install.sh | sh -s -- -v 0.22.0
& ([scriptblock]::Create((irm https://raw.githubusercontent.com/xlsft/ymcp/main/install.ps1))) -Version 0.22.0
Or with a package manager, then run ymcp setup:
brew install xlsft/tap/ymcp # macOS, Linux
scoop bucket add xlsft https://github.com/xlsft/scoop-bucket; scoop install ymcp # Windows
Package-managed copies update through their manager (brew upgrade ymcp and so on); ymcp update says so. Either way, ymcp update lists what each release since yours changed, and links the changelog.
The installer downloads the latest release and checks its SHA-256. It then runs ymcp setup, a TUI in the look of ymcp pipeline. With no profile yet it opens a new one, in three steps:
youtrack by default, and your YouTrack URL, login and password, signed in to as you type; nothing is saved until they work;Run ymcp setup again at any time to edit a profile, add or remove clients, or add another YouTrack.
An agent setting ymcp up for you (Cline and the like) has its own steps in llms-install.md.
Each YouTrack instance is a profile, and each profile is its own MCP server. The profile's display name gives the server name: YouTrack (work) becomes youtrack-work, youtrack-acme stays as it is. A repeated ymcp setup lists your profiles with their tools and clients: enter edits one (a rename moves its client entries along), n adds a profile and d removes one. Clients run ymcp --profile , so every instance shows up next to the others with its own tools.
Releases are signed keylessly with Sigstore by this repository's release workflow: checksums.txt has a checksums.txt.sigstore.json bundle, and each archive an SPDX SBOM (*.sbom.json).
cosign verify-blob checksums.txt --bundle checksums.txt.sigstore.json \
--certificate-identity-regexp '^https://github.com/xlsft/ymcp/\.github/workflows/' \ --certificate-oidc-issuer https://token.actions.githubusercontent.com sha256sum --ignore-missing -c checksums.txt
Each release also has SLSA build provenance for every file in checksums.txt, kept by GitHub and attached as ymcp.intoto.jsonl:
gh attestation verify ymcp_linux_amd64.tar.gz --repo xlsft/ymcp
The Docker image is signed the same way and carries SBOM and provenance attestations:
cosign verify xlsoftware/ymcp:latest \
--certificate-identity-regexp '^https://github.com/xlsft/ymcp/\.github/workflows/' \ --certificate-oidc-issuer https://token.actions.githubusercontent.com
docs/reference.md has the full reference: every command, every tool and prompt with its inputs and outputs, and every field of the pipeline file.
| Command | ||
|---|---|---|
ymcp / ymcp serve | Run the MCP server over stdio (what clients launch). --transport http serves Streamable HTTP, see HTTP | |
ymcp setup | The profiles TUI: add or edit a profile, sign in, pick its tools, confirmations and MCP clients. For scripts, --clients cursor,zed or --all with --name, --tools, `--confirm on\ | off and --reauth, or --remove`, skip the TUI |
ymcp auth | Set or replace the URL, login and password of a profile. --url, --login, --proxy, --password-stdin for scripts | |
ymcp check | Sign in and print who you are | |
ymcp call ' ' | Call one tool, exactly as a client would, e.g. ymcp call count_issues '{"query":"#Unresolved"}' | |
ymcp health | Check that a running HTTP server answers (--url, default http://127.0.0.1:8090) | |
ymcp logs | Show what the server did; -f follows the log live, -n 200 shows more lines | |
ymcp pipeline | Open the pipelines TUI; ymcp pipeline --help lists new, run, check, answer and the rest, see Pipelines | |
ymcp update | Replace the binary with the latest release and show what changed since your version (--check only reports) | |
ymcp version | Print the version |
| Area | Tools |
|---|---|
| Issues | search_issues, get_issue, create_issue, create_draft_issue, update_issue, change_issue_assignee, get_issue_fields_schema |
| Comments, tags, links, time | add_issue_comment, get_issue_comments, manage_issue_tags, link_issues, log_work, get_saved_issue_searches |
| Knowledge base | search_articles, get_article, create_article, update_article |
| Projects and people | find_projects, get_project, find_user, get_current_user, find_user_groups, get_user_group_members |
Custom fields are set by their display name, e.g. {"State": "In Progress", "Fix versions": ["2.1"]}. ymcp looks up the field type and checks the value against the project before sending it. That includes the allowed assignees, so a wrong value comes back with the list of valid ones.
| Area | Tools |
|---|---|
| Delete and undo | delete_issue, delete_issue_comment, restore_issue_comment, delete_article, delete_work_item, unlink_issues |
| Agile boards and sprints | find_agile_boards, get_agile_board, get_sprint, create_sprint, update_sprint, add_issue_to_sprint, remove_issue_from_sprint, delete_sprint |
| History and reports | get_issue_activities, count_issues, get_time_report, get_issue_work_items |
| Bulk changes | apply_command: any command from the YouTrack command dialog, on issues or a query (up to 100), validated first, with dryRun |
| Attachments | Of issues and knowledge base articles: get_issue_attachments, get_attachment (text inline, images as images, other files saved locally), add_attachment (several files at once), delete_attachment |
| Comments | update_issue_comment |
| Partial text edits | edit_issue_description, edit_article_content: find-and-replace in a description or article, exact or by regular expression with capture groups, so a small change doesn't resend the whole text |
| VCS | get_issue_vcs_changes: commits and pull requests from GitHub, GitLab, Bitbucket, Gitea or TeamCity integrations |
| Tags and saved searches | find_tags, create_tag, update_tag, delete_tag, create_saved_search, update_saved_search, delete_saved_search |
| Escape hatch | call_api: any YouTrack or Hub REST endpoint as you, for whatever the other tools don't cover |
Every command takes --profile (or YMCP_PROFILE) to pick the YouTrack instance, e.g. ymcp --profile youtrack-acme check. Without it ymcp uses the youtrack profile, or the only one there is.
Tools that delete or bulk-change data are marked with destructiveHint, so clients ask before running them.
Errors tell the model what to do next. ymcp's own checks list what is allowed (value "X" is not allowed; allowed: Critical, Major, …), and errors from YouTrack get a hint by status: which tool finds the right ID after a 404, that a 403 needs a permission rather than a retry, that a 401 needs ymcp auth. HTML error pages from proxies are cut down to their title.
Clients that support MCP prompts list these as slash commands. Each one tells the model which tools to use and in what order, and they never change YouTrack without asking:
| Prompt | |
|---|---|
standup | What I did since the last working day (Friday on a Monday), what's next, what blocks me. days looks further back |
triage | Untriaged issues of a project with proposed type, priority, assignee and duplicates; applies only what you approve |
sprint_report | A sprint of a board: done and open work, who has what, scope changes, time logged, risks |
issue_brief | Catch up on an issue: TL;DR, state, decisions, open questions, next steps |
A prompt is offered only when the tools it needs are served (see below).
All 58 tools take room in the model's context. A profile can serve only some of them: pick groups or single tools in ymcp setup, or pass --tools (or YMCP_TOOLS) to serve, which wins over the profile.
| Group |
Only the beginning is shown; read the rest in the repo