OpenProject MCP Server

Search, create, update, assign, and comment on OpenProject work packages. The openproject mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 10 defined tools rather than through you.

What it actually does

OpenProject also provides an official MCP server in Professional plans and above. As of July 2026, that server exposes read-only tools. This community project is a good fit when you need write operations, Codex-specific guidance, or support for Community Edition. See the official MCP documentation for the current capabilities of OpenProject's server.

• Broad read and write coverage: — manage projects and work packages, upload
• Community Edition friendly: — it uses the generally available OpenProject
• Codex-native workflow: — tools and guidance are packaged together so Codex
• Runs locally: — credentials stay in a private file on your machine, and

Adding it to your client

openproject-codex-plugin on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Its toolset

Everything the assistant can do here goes through one of these:

• Area — Read tools
• Projects — list_projects, get_project, count_projects
• Attachments — list_work_package_attachments, get_work_package_attachment
• Relations — list_work_package_relations, get_work_package_relation
• Users — get_current_user, list_users, get_user, list_available_assignees
• Watchers — list_work_package_watchers
• Notifications — list_notifications, get_notification
• Boards — list_boards, get_board, list_board_lanes
• Advanced — get_openproject_api
• Windows — Set OPENPROJECT_URL and OPENPROJECT_API_TOKEN, save it, then install:

Configuration

You will need 4 environment variables: OPENPROJECT_URL, OPENPROJECT_API_TOKEN, OPENPROJECT_BASE_URL, OPENPROJECT_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Bun 1.3 or newer - Codex CLI with MCP support - An OpenProject API token with access to the projects you want to manage The plugin and its local MCP server run natively on macOS, Linux, and Windows. It uses stable OpenProject API v3 endpoints and does not require an OpenProject Enterprise add-on. If you use Community Edition, make sure API tokens are enabled in your instance.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch OpenProject.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the openproject mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. OpenProject's toolset — Area, Projects, Attachments and 7 more — is a fair guide to whether it matches your workflow. It is maintained by alex13slem; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.