# jtauschl/openproject-ce-mcp [Health: Active]

**Category:** 📋 Product Management  
**Repository:** https://github.com/jtauschl/openproject-ce-mcp  
**GitHub Stars:** 35  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/jtauschl-openproject-ce-mcp

## Description
OpenProject Community Edition over API v3: projects, work packages, time tracking, meetings, boards, wiki and more, with project allowlists and preview-then-confirm writes.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "openproject-ce-mcp": {
    "command": "uvx",
    "args": ["openproject-ce-mcp"],
    "env": {
      "OPENPROJECT_READ_PROJECTS": "",
      "OPENPROJECT_WRITE_PROJECTS": ""
    }
  }
}
```

**Requires environment variables:** `OPENPROJECT_READ_PROJECTS`, `OPENPROJECT_WRITE_PROJECTS` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What jtauschl/openproject-ce-mcp does

The jtauschl/openproject-ce-mcp MCP server gives local AI clients structured access to an OpenProject Community Edition instance. It covers project administration, work packages, memberships, versions, boards, time entries, users, groups, wiki pages, news, documents, notifications, and other supporting data exposed by OpenProject API v3.

The tool interface is organized around common actions such as listing, searching, creating, updating, and deleting resources rather than requiring an agent to construct REST requests or follow HAL links. Responses are bounded, paginated, and shaped for agent context. Optional field selection can make returned records smaller.

This fits the Workplace & Productivity category for teams that want an AI client to inspect or maintain OpenProject data. It is specifically for Community Edition; Enterprise-only features such as portfolios, programs, placeholder users, custom actions, and baseline comparisons are outside its scope.

## How it works

The jtauschl/openproject-ce-mcp MCP server runs locally and communicates with the MCP client over stdio. It does not operate as a remote service and does not maintain persistent storage. The server wraps OpenProject API v3 and returns compact summaries instead of exposing raw HAL payloads directly.

Read tools are available by default, but they cannot access project data until projects are supplied through the read-project allowlist. Core write categories are registered by default, yet writes remain inactive until projects are included in the write-project allowlist. Personal-data and administrative write operations require separate opt-in controls. These MCP-side restrictions add a scope boundary to OpenProject's own permissions.

Write behavior is intentionally staged. A create or update request is first validated and returned as a preview; the operation runs only when the client repeats it with confirmation. Deletes and other simple operations still require confirmation, although they do not use the same form-validation process.

## Setup and configuration

Install the package with `pipx install openproject-ce-mcp`, or use `uv tool install openproject-ce-mcp`. The command-line `configure` flow asks for the OpenProject URL, API token, and project scope, then creates configuration for the selected MCP client. The package also supports a version check through `openproject-ce-mcp --version`.

Treat the API token as a password and keep client configuration out of version control. Configure at least the projects permitted for reading, and separately identify projects permitted for writing if mutations are needed. After changing the client configuration, restart the MCP client and verify access with a current-user or project-list request.

The server's documented client setup includes Claude Desktop, Claude Code, Codex, Cursor, and VS Code/GitHub Copilot. Exact configuration files vary by client.

## Tools and capabilities

The jtauschl/openproject-ce-mcp tool set supports:

- Listing, searching, creating, copying, updating, and deleting projects
- Managing work packages, subtasks, relations, comments, attachments, watchers, and activity logs
- Recording, editing, and removing time entries
- Managing memberships, versions, roles, users, groups, and group membership
- Creating and maintaining saved boards, plus reading views
- Reading wiki pages, updating documents, and creating, editing, or deleting news
- Reading and marking notifications, and inspecting configuration, working days, grids, and custom options

Work package filters and compact field selection help limit the amount of context returned to the model. Attachment reads can inline image and text content for the model.

## Limitations and notes

The jtauschl/openproject-ce-mcp MCP server targets Community Edition only and should not be selected when the required workflow depends on Enterprise Edition features. It cannot bypass the preview-confirmation requirement for writes. Project access also remains unavailable until the relevant allowlists are configured, even when read or write tool categories are registered.

The server exposes comments for work packages but does not provide comment editing or deletion. It is a local stdio integration rather than a hosted, multi-user MCP endpoint. OpenProject's server-side permissions still apply in addition to the MCP allowlists.

_Full upstream README: https://allmcps.com/mcp/jtauschl-openproject-ce-mcp/readme_