Log inSubmit server
Openproject Ce MCP logo

Openproject Ce MCP

by jtauschl

Connects local MCP clients to OpenProject CE API v3 for scoped project data, guarded writes, and compact typed tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Openproject Ce MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "jtauschl-openproject-ce-mcp": {
      "command": "uvx",
      "args": [
        "openproject-ce-mcp"
      ],
      "env": {
        "OPENPROJECT_READ_PROJECTS": "YOUR_VALUE_HERE",
        "OPENPROJECT_WRITE_PROJECTS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

uvx openproject-ce-mcp

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 7d ago.

Overview

The jtauschl/openproject-ce-mcp MCP server connects local AI agents to OpenProject Community Edition through API v3. It runs as a local stdio subprocess and exposes typed operations for projects, work packages, time tracking, boards, users, wiki content, and related data. Read and write access are constrained by project allowlists, while every write requires a preview followed by explicit confirmation. Reach for it when an agent needs structured OpenProject access without handling raw HAL responses or unrestricted project scope.

Use cases

  • List work packages with structured filters
  • Create and update projects after reviewing previews
  • Log and manage time entries
  • Inspect boards, wiki pages, documents, and notifications
  • Manage users, groups, memberships, and versions

Key features

  • OpenProject API v3 access over MCP stdio
  • Project-scoped read and write allowlists
  • Preview-then-confirm write workflow
  • Typed tools for projects and work packages
  • Compact paginated responses with field selection
  • Community Edition support

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · openproject-ce-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars35Stargazers on the source repository.
Last commit2d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Openproject Ce MCP works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Openproject Ce MCP

jtauschl/openproject-ce-mcp is an MCP server that connects local AI clients to OpenProject Community Edition through API v3. Its main tools manage projects, work packages, time entries, boards, users, groups, wiki content, and related data, with project allowlists and preview-confirmed writes.

Install it with pipx or uv, using `pipx install openproject-ce-mcp` or `uv tool install openproject-ce-mcp`. Then run `openproject-ce-mcp configure` to provide the OpenProject URL, API token, project scope, and client configuration.

Set the read and write project allowlists separately. Read access requires projects in `OPENPROJECT_READ_PROJECTS`; mutations also require projects in `OPENPROJECT_WRITE_PROJECTS`. OpenProject permissions continue to apply alongside these MCP-side restrictions.

Yes, Cursor is one of the clients with a documented setup guide. Configure the local stdio server in Cursor using the client instructions, then restart Cursor and verify access with a supported read request.

Related MCP servers

All in Product Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOpenproject Ce MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/jtauschl-openproject-ce-mcp?style=directory)](https://allmcps.com/mcp/jtauschl-openproject-ce-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/jtauschl-openproject-ce-mcp"><img src="https://allmcps.com/api/badge/jtauschl-openproject-ce-mcp?style=directory" alt="Openproject Ce MCP on AllMCPs" /></a>