OpenProject

io.github.alex13slemPublished by GitHub account alex13slemv0.5.0Updated Oct 24, 2026

Manage OpenProject projects, work packages, files, relations, boards, users, and notifications.

VerifiedSTDIODesktop onlyProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Write-capable MCP server for OpenProject API v3, letting an assistant manage projects, work packages, attachments, relations, boards, users and notifications.

What you can do
  • Create, read, update and delete projects, with counts, filters, sorting and pagination
  • Search and manage work packages, including comments, activity history, scheduling, estimates, progress, hierarchy, assignees, priorities, statuses and versions
  • List, read, upload and delete work-package attachments, with text files returned directly and binaries as embedded resources
  • Manage relations and watchers, and look up the current user, search users and list permission-aware assignees
  • Inspect in-app notifications and Kanban-style boards, and discover statuses, priorities, types and versions
  • Make restricted GET-only passthrough calls to uncovered paths under the API v3 root
When to use it
Useful when an assistant should work directly inside a self-hosted or hosted OpenProject instance: triaging and updating work packages, uploading files to tasks, managing relations and watchers, or checking boards and notifications without switching to the web UI.
Requirements
Runs locally over stdio, typically launched with npx, so Node.js is needed. Requires the root URL of the OpenProject instance in OPENPROJECT_URL and an API token in OPENPROJECT_API_TOKEN. Optional settings cover page size, request timeout, auth mode (basic or bearer) and allowed upload directories. Network access to the OpenProject instance is required.
Before you install
The server is explicitly write-capable and includes destructive tools such as attachment deletion, so changes to real project data are possible; read, write and destructive tools are annotated for client confirmation policies. It needs an API token, which should be scoped to only the permissions required and never committed or shown in logs and screenshots. Upload tools can read local files from the configured allowed directories, which default to the working directory.

Installation

In SourceWeft

  1. Open OpenProject in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

OpenProject MCP server

A comprehensive, write-capable Model Context Protocol server for OpenProject API v3. Its 41 focused tools cover projects, work packages, attachments, relations, boards, users, watchers, notifications, and reference data.

Attachment tools can list files on a work package and fetch their content. Text-based files are returned directly; binary files are returned as embedded MCP resources. Uploads and downloads are size-limited per request.

The package is maintained as part of OpenProject for Codex, which also includes Codex workflow guidance and portable installers.

Run with an MCP client

Configure these environment variables:

  • OPENPROJECT_URL: the root URL of your OpenProject instance;
  • OPENPROJECT_API_TOKEN: an API token with only the permissions you need.

OPENPROJECT_BASE_URL and OPENPROJECT_API_KEY are accepted as compatibility aliases for existing MCP configurations.

Optional settings:

  • OPENPROJECT_PAGE_SIZE: default collection page size from 1 to 100 (default 25);
  • OPENPROJECT_TIMEOUT_MS: request timeout from 1000 to 300000 milliseconds (default 30000);
  • OPENPROJECT_AUTH_MODE: basic for broad compatibility (default), or bearer for OpenProject 17.2 and newer.
  • OPENPROJECT_ALLOWED_UPLOAD_DIRS: platform-separated directories from which upload tools may read files (default: current working directory).

Then launch the stdio server with:

bash
npx -y openproject-codex-plugin

Example MCP configuration:

json
{  "mcpServers": {    "openproject": {      "command": "npx",      "args": ["-y", "openproject-codex-plugin"],      "env": {        "OPENPROJECT_URL": "https://tasks.example.com",        "OPENPROJECT_API_TOKEN": "your-api-token"      }    }  }}

Never commit API tokens or include them in public logs and screenshots.

Capabilities

  • Project CRUD, counts, native filters, sorting, and pagination.
  • Work-package search, CRUD, comments, activity history, scheduling, estimates, progress, hierarchy, assignees, responsible users, priorities, statuses, and versions.
  • Attachment listing, authenticated reads, local-file uploads, and deletion.
  • Relations and watcher management.
  • Current-user lookup, user search, and permission-aware available assignees.
  • In-app notifications and Kanban-style board inspection.
  • Status, priority, type, and version discovery.
  • Restricted GET-only passthrough for uncovered paths under /api/v3.

Read, write, and destructive tools carry MCP annotations so compatible clients can apply appropriate confirmation policies. Collection responses include total, count, offset, pageSize, and hasMore metadata.

License

MIT

Source: plugins/openproject/README.md at commit c45c46a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.5.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts