Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for OpenProject Community Edition with guarded read/write support.
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.
OPENPROJECT_BASE_URL, OPENPROJECT_API_TOKEN, OPENPROJECT_READ_PROJECTS, OPENPROJECT_WRITE_PROJECTSValues 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": {
"openproject-ce": {
"command": "uvx",
"args": [
"openproject-ce-mcp"
],
"env": {
"OPENPROJECT_BASE_URL": "your-value",
"OPENPROJECT_API_TOKEN": "your-value",
"OPENPROJECT_READ_PROJECTS": "your-value",
"OPENPROJECT_WRITE_PROJECTS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add openproject-ce --env OPENPROJECT_BASE_URL=your-value --env OPENPROJECT_API_TOKEN=your-value --env OPENPROJECT_READ_PROJECTS=your-value --env OPENPROJECT_WRITE_PROJECTS=your-value -- uvx openproject-ce-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"openproject-ce": {
"command": "uvx",
"args": [
"openproject-ce-mcp"
],
"env": {
"OPENPROJECT_BASE_URL": "your-value",
"OPENPROJECT_API_TOKEN": "your-value",
"OPENPROJECT_READ_PROJECTS": "your-value",
"OPENPROJECT_WRITE_PROJECTS": "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": {
"openproject-ce": {
"type": "stdio",
"command": "uvx",
"args": [
"openproject-ce-mcp"
],
"env": {
"OPENPROJECT_BASE_URL": "your-value",
"OPENPROJECT_API_TOKEN": "your-value",
"OPENPROJECT_READ_PROJECTS": "your-value",
"OPENPROJECT_WRITE_PROJECTS": "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.
OPENPROJECT_READ_PROJECTS envOPENPROJECT_WRITE_PROJECTS 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 with the GitHub account jtauschl, 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: OPENPROJECT_BASE_URL, OPENPROJECT_API_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 (0.4.4) reached the registry 10 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, Tool Guardian
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.
Too many MCP servers eating your context? A router that loads each tool's schema only when needed.
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.
An MCP server for OpenProject that lets local AI agents read and manage project data through structured, guarded tools.
The server runs as a local subprocess of your MCP client over stdio. It wraps OpenProject API v3 and exposes typed tools for projects, work packages, memberships, versions, boards, meetings, time entries, and more.
Reading this on PyPI? All links below point to the GitHub repository —
the
docs/pages and images ship in the git repo and source distribution,
not in the installed package itself.
select; see Context efficiency for the full numbers.Projects
Work packages
Boards and views
Meetings
Administration and schedules (opt-in)
Supporting data
All write operations follow a preview-then-confirm pattern: call a tool once to get a validated preview, then again with confirm=true to execute. There is no way to bypass this.
This MCP server targets OpenProject Community Edition only. It does not support Enterprise Edition features such as:
Note: OpenProject Enterprise Edition includes its own MCP server. If you have an Enterprise license, use the official Enterprise MCP instead of this one.
OPENPROJECT_READ_PROJECTS lists a project, only project-independent tools such as list_statuses, list_types and get_current_user are registered. Personal, admin, user-schedule, and extended metadata tools are opt-inOPENPROJECT_READ_PROJECTS and OPENPROJECT_WRITE_PROJECTS list a project, and a write reaches only projects in both. The allowlists, not the category flags, are the real gate. Personal-data, admin, and user-schedule writes are opt-inA core reason to use this MCP instead of calling the OpenProject REST API directly: it returns context-frugal responses instead of raw HAL payloads — and not just for listing. The numbers below are measured against the same three representative work packages (real tiktoken counts, not a bytes/4 approximation); read/search/write/batch calls all land in the same −85% to −98% range. For the full per-call-type breakdown, the tool-catalog size numbers, and how to reproduce them, see Context efficiency.
| Response | Tokens | vs. raw API |
|---|---|---|
| Raw OpenProject REST API v3 (HAL) | ~9,992 | baseline |
list_work_packages (MCP) | ~861 | −91% |
list_work_packages with select (5 fields) | ~174 | −98% |
This quickstart requires pipx; see Installation if it isn't installed yet.
pipx install openproject-ce-mcp
openproject-ce-mcp configure openproject-ce-mcp --version
Already use uv? uv tool install openproject-ce-mcp works the same way. See Installation for when plain pip install is appropriate instead, and for uvx (a zero-install, run-on-demand alternative to installing at all).
configure collects your OpenProject URL, API token, and project scope, then writes the config for the MCP client(s) you choose. Project-scoped is recommended: the server is then available only in the current project. Global makes it available everywhere. Restart your MCP client afterward, then ask it to call get_current_user or list_projects to verify.
See Installation for requirements, updating, source installs, and uninstalling, and Clients for per-client setup guides.
Full documentation lives in docs/, starting at the documentation hub:
Your client config (.mcp.json, .codex/config.toml, or .vscode/mcp.json) contains your API token — treat it like a password and keep it out of version control; choose your client-specific guide from Clients for the exact .gitignore step. configure writes a minimal config: only the values that differ from a safe default. The core read groups and the project-scoped write categories are enabled by default, but their project-bound tools are registered, and project access is granted, only once you list projects in OPENPROJECT_READ_PROJECTS (and, for writes, in OPENPROJECT_WRITE_PROJECTS too); that allowlist pair, not the category flags, is the real gate.
See Configuration for the full environment variable reference and what configure --quick vs. --advanced ask.
User-provided text (work-package descriptions, comments, news, wiki content) is marked with tags and flagged in server instructions as untrusted. Agents should treat this content as data, not as instructions.
See SECURITY.md for the full security model, including prompt injection mitigations, reporting procedures, and supported versions.
Ask questions in GitHub Discussions. Report bugs and request features in GitHub Issues. Report security vulnerabilities privately as described in SECURITY.md.
main is a frozen snapshot of the last release, not the active development branch. See CONTRIBUTING.md for which branch to clone (active development vs. bugfixes) and the full test suite (unit, integration, and Docker test instances).
MIT — see LICENSE. A single top-level license file covers the whole project; individual source files don't carry per-file copyright headers, matching common practice for MIT-licensed Python packages.