Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server built into Rillsoft Project 10 for multi-project resource planning (local, Windows)
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.
The maker has not listed install details in the registry. See the maker’s README below.
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 against the domain rillsoft.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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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 (10.0.0) reached the registry 39 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code.
In the same category: Spec Driven Development, Remote Desktop Commander, dotnet-mcp
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.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
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.
Deutsch
Rillsoft AI is the AI gateway to Rillsoft Project, the specialist solution for multi-project resource and capacity planning in mid-sized industrial companies: an MCP server built into Rillsoft Project 10, on top of its scheduling engine – not on top of a task list.
The server runs inside the visible, running Rillsoft Project on Windows and exposes the open project to an AI assistant or a script over the Model Context Protocol: project structure and schedule, roles, people, teams, machines and material, candidate search and staffing assistants, capacity analysis, baselines and plan/actual comparison, progress and status date, the resource pool, undo and redo.
This repository contains documentation, client configuration and the npm launcher (launcher.js, see Install via npx). The server itself is part of the Rillsoft Project 10 desktop application; the launcher only forwards to it, and there is no hosted endpoint.
Full documentation: https://rillsoft.ai/en/mcp/
| Endpoint | http://127.0.0.1:3928/mcp |
| Protocol | MCP over Streamable HTTP, revision 2025-06-18 |
| Reach | 127.0.0.1 only – no cloud service, nothing is sent to Rillsoft |
| Requirement | Rillsoft Project 10 on Windows |
| Access protection | optional API key, read-only mode, browser origins rejected |
| Trade-off | an MCP call carries no user identity and reaches exactly one Rillsoft Project instance |
127.0.0.1 only, inside the open Rillsoft Project. Rillsoft sends nothing; what your AI client sends is governed by its provider's privacy policy.RillPrj.exe /mcp (port 3928) or RillPrj.exe /mcp:8123 (another port) for one session. Check: the status line shows "running on port 3928".clients/generic.json: {
"mcpServers": { "rillsoft-project": { "type": "http", "url": "http://127.0.0.1:3928/mcp" } } }
With an API key set in the settings, use clients/generic-api-key.json (Authorization: Bearer ). Ready-made entries per client:
| Client | File | Where it goes | Verified |
|---|---|---|---|
| Claude Code | claude-code.mcp.json | .mcp.json in the project folder, or claude mcp add --transport http rillsoft-project http://127.0.0.1:3928/mcp | 12 Oct 2026, 2.1.296 |
| Claude Desktop | claude-desktop.json | claude_desktop_config.json (Settings → Developer → Edit Config); bridge mcp-remote needs Node.js | 12 Oct 2026, 2.31226 |
| Codex | codex.toml | ~/.codex/config.toml, or codex mcp add rillsoft-project --url http://127.0.0.1:3928/mcp | 12 Oct 2026, CLI 0.162 |
| VS Code | vscode.mcp.json | .vscode/mcp.json | 12 Oct 2026, 1.117 |
| Cursor | cursor.mcp.json | ~/.cursor/mcp.json | per vendor documentation |
Claude Code and VS Code need Rillsoft Project 10 build 10.0.625 or later. Any other client that speaks MCP over Streamable HTTP uses the address above; its documentation names the field names. Check: the client lists the server's tools – in read-only mode only the read-only ones. /mcp is exact, /mcp/ is a 404.
Every mutating call is one ordinary undo step in Rillsoft Project – you take it back with Ctrl+Z like any of your own edits.
Step by step with success checks: Get started.
For catalogues, registries and clients that only start stdio servers there is an npm package, @rillsoft/rillsoft-project-mcp, built from this repository. It is a launcher, not the server:
http://127.0.0.1:3928/mcp. The address is fixed; there is no environment variable for the address and no API key. If an API key is set in Rillsoft Project, the launcher reports the 401 – use the HTTP configuration above instead. For diagnostics only, RILLSOFT_MCP_LOG= writes the requests and answers of a session to a log file.initialize and tools/list itself from tools-list.json – the same 118 tools as the program – and every tools/call with isError: true and a hint. This is what lets catalogues show the tools on Linux.{
"mcpServers": { "rillsoft-project": { "command": "npx", "args": ["-y", "@rillsoft/rillsoft-project-mcp"] } } }
Requires Node.js 18 or later; real results only on Windows with Rillsoft Project 10 running. Customers do not need the launcher: the configurations above connect directly to the running program.
This repository is also a plugin for Claude Code and Cowork (.claude-plugin/). In Claude Code:
/plugin install rillsoft-project --marketplace rillsoft/rillsoft-project-mcp
What the plugin does on your machine:
node ${CLAUDE_PLUGIN_ROOT}/launcher.js (Node.js 18 or later), the same launcher as the npm package above.http://127.0.0.1:3928/mcp, the MCP endpoint of Rillsoft Project 10 running on the same computer. It sends no data anywhere else, collects no telemetry, needs no account and no API key.tools-list.json from the plugin folder and lists the tools; every tool call then answers with a hint instead of a result.RILLSOFT_MCP_LOG= yourself.Your AI client sends the project data that the tools return to its provider, as with every MCP server. Local plugin servers run in Claude Code and Cowork; the chat in Claude Desktop ignores them – use the configuration under “Set up” there.
| Symptom | Cause and remedy |
|---|---|
400 | session or protocol revision missing – send initialize, then include Mcp-Session-Id and MCP-Protocol-Version: 2025-06-18 |
401 | an API key is set; the client needs Authorization: Bearer |
403 | the request carries an Origin header as browsers send it; use an MCP client, not a browser page |
| no port after a crash | the auto-recovery dialog is waiting; answer it or start RillPrj.exe /mcp |
| server does not listen immediately | it starts a few seconds after the program |
Tool names carry the prefix rillsoft_ and are English in every language build; arguments, result fields, enum values and error codes are stable, messages follow the language of the running Rillsoft Project. How tools/list, schemas, errors, undo, read-only mode and sessions work: Developers: the MCP server contract.
The complete tool catalogue – 118 tools of Rillsoft Project 10.0.626.0 with title, access class, parameters and description – is in TOOLS.md. It is generated from tools/list of the running program by scripts/generate_tools.py, never edited by hand; the raw result, including the output schemas, is in tools-list.json.
ai.rillsoft/rillsoft-project (entry)Rillsoft GmbH, Leonberg, Germany – software for scheduling, resource and multi-project planning. Rillsoft Project is proprietary software; this repository contains its MCP documentation and the launcher.
The documentation and the tool catalogue in this repository are licensed under CC BY 4.0; the launcher code (launcher.js) under the MIT License. Rillsoft Project itself, including its MCP server, is proprietary software of Rillsoft GmbH and is not covered by either license.