Installation überspringen. In unter 2 Minuten einsatzbereit.
Starte eine kostenlose Testphase auf cloud.anythingmcp.com, füge OpenProject mit einem Klick hinzu und richte deinen KI-Client (Claude, ChatGPT, Copilot oder Cursor) auf den erzeugten MCP-Endpoint. Kein Docker, kein git clone, keinerlei Entwicklungserfahrung nötig.
Summary
OpenProject: projects, work packages with their activities, versions, time entries, users and statuses, queried with OpenProject's filter grammar. API v3, Basic auth with the literal username `apikey`.
Frag einfach
Beispiel-Prompts für OpenProject
Klick auf einen Prompt, um ihn zu kopieren. In Claude, ChatGPT, Cursor, Gemini, Copilot oder OpenClaw einfügen — und gegen diesen Connector laufen lassen.
Claude ist KI und kann Fehler machen. Bitte Antworten gegenprüfen.
💡 Keine Installation? Nutze cloud.anythingmcp.com direkt. Einloggen, Connectors → OpenProject klicken, Zugangsdaten einfügen, MCP-API-Key erzeugen — fertig. Kein Docker, kein
git clone, kein lokaler Server.
OpenProject
OpenProject: projects, work packages with their activities, versions, time entries, users and statuses, queried with OpenProject's filter grammar. API v3, Basic auth with the literal username apikey.
Einrichtung
Getting a key
- In OpenProject open My Account → Access tokens and generate an API token.
- Set
OPENPROJECT_URLto your instance root (no trailing slash) andOPENPROJECT_API_KEYto the token.
The Basic-auth username is the literal string apikey. Not your login name — the word apikey, with the token as the password. This adapter does it for you, and it is the first thing to check when a token you know is valid returns 401.
Permissions follow the user. The token inherits its owner's project memberships and roles. A project the user is not a member of is simply absent from the results, not an error.
…(continued in the in-app connector instructions)
Voraussetzungen: OPENPROJECT_URL, OPENPROJECT_API_KEY
Connector lokal installieren
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Öffne http://localhost:3000/connectors/store, wähle OpenProject und trage die unter Voraussetzungen aufgelisteten Variablen ein.
Verfügbare Tools
| Tool | What it does |
|---|---|
openproject_get_me | Read the user the API token belongs to, with their name, e-mail, language and admin flag |
openproject_list_projects | List projects with their identifier, name, status, description and active flag |
openproject_list_work_packages | List work packages — tasks, bugs, features, milestones — across all projects, with their type, status, assignee, dates and priority |
openproject_list_project_work_packages | List the work packages inside one project — the usual scope for 'what is open on this project' and much cheaper than filtering globally |
openproject_get_work_package | Read one work package in full: description, type, status, assignee, dates, estimated and spent time, and its custom fields |
openproject_list_work_package_activities | Read the activity stream of one work package: every comment and field change in order, with author and timestamp |
openproject_list_time_entries | List logged time entries with their user, work package, date, hours and comment — the raw data behind any effort report |
openproject_list_versions | List versions (releases and sprints) with their name, status, due date and the project they belong to |
openproject_list_users | List users with their name, e-mail, login and status, to resolve who a work package is assigned to |
openproject_list_statuses | List the work-package statuses this instance defines, with their id, name and whether each counts as closed |
Nächste Schritte
War dieser Guide hilfreich?
