Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
YouTrack with your login and password: the built-in tools plus deletes, sprints, history and reports
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
YOUTRACK_URL, YOUTRACK_LOGIN, YOUTRACK_PASSWORD, YOUTRACK_PROXY, YMCP_TOOLSAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"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"
}
}
}
}Führe das in deinem Terminal aus
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 serveTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"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"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"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"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
YOUTRACK_PROXY envYMCP_TOOLS envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto xlsft bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: YOUTRACK_URL, YOUTRACK_LOGIN, YOUTRACK_PASSWORD
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.27.0) kam vor 8 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Docker auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Apify MCP Server
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
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.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
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 |
Nur der Anfang wird gezeigt; den Rest findest du im Repo