Skip to main content
Glama
dev-in-black

OpenProject MCP Server

by dev-in-black
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPENPROJECT_URLYesThe URL of your OpenProject instance (e.g., https://your-instance.openproject.com)
OPENPROJECT_API_KEYYesYour OpenProject API key for authentication. Get this from My Account > Access tokens > + API in your OpenProject instance.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
create_work_packageA

Create a new work package in a project.

Args:
    project_id: Project identifier or ID
    subject: Work package title (required)
    description: Work package description in markdown format
    type_id: Type ID (default: 1 for Task)
    status_id: Status ID (optional, uses project default if not provided)
    priority_id: Priority ID (optional, uses default if not provided)
    assignee_id: User ID to assign the work package to
    notify: Whether to send notifications (default: True)
get_work_packageC

Get detailed information about a work package.

Args:
    work_package_id: Work package ID
update_work_packageB

Update an existing work package.

Args:
    work_package_id: Work package ID
    lock_version: Current lock version (get from work package first)
    subject: New subject/title
    description: New description in markdown
    status_id: New status ID
    priority_id: New priority ID
    assignee_id: New assignee user ID (use 0 to unassign)
    notify: Whether to send notifications (default: True)
list_work_packagesB

List work packages with optional filtering and pagination.

Args:
    project_id: Optional project ID to filter work packages
    filters: Optional JSON filter string
    page: Page number (default: 1)
    page_size: Items per page (default: 20)
delete_work_packageB

Permanently delete a work package.

Args:
    work_package_id: Work package ID to delete
get_available_assigneesB

Get list of users who can be assigned to work packages in a project.

Args:
    project_id: Project identifier or ID
add_watcherC

Add a user as a watcher to a work package.

Args:
    work_package_id: Work package ID
    user_id: User ID to add as watcher
remove_watcherB

Remove a user from work package watchers.

Args:
    work_package_id: Work package ID
    user_id: User ID to remove from watchers
get_work_package_schemaC

Get the schema for creating/updating work packages.

Args:
    project_id: Project identifier or ID
    type_id: Optional type ID to get type-specific schema
set_parent_work_packageA

Set or remove the parent of a work package.

Args:
    work_package_id: Child work package ID
    parent_id: Parent work package ID (use None to remove parent)
    lock_version: Current lock version (get from work package first)
    notify: Whether to send notifications (default: True)
get_work_package_activitiesB

Retrieve all activities and comments for a work package.

Args:
    work_package_id: Work package ID
    page: Page number (default: 1)
    page_size: Items per page (default: 20)
create_commentB

Add a comment to a work package.

Args:
    work_package_id: Work package ID
    comment: Comment text in markdown format
    internal: Whether the comment is internal (default: False)
get_activityC

Get details of a specific activity.

Args:
    activity_id: Activity ID
update_commentB

Update an existing comment.

Args:
    activity_id: Activity ID of the comment to update
    comment: New comment text in markdown format
    lock_version: Current lock version (get from activity first)
get_projectB

Get detailed information about a project.

Args:
    project_id: Project identifier or ID
list_projectsB

List all accessible projects with optional filtering and pagination.

Args:
    filters: Optional JSON filter string
    page: Page number (default: 1)
    page_size: Items per page (default: 20)
update_projectB

Update an existing project.

Args:
    project_id: Project identifier or ID
    lock_version: Current lock version (get from project first)
    name: New project name
    description: New project description in markdown
    public: Whether project is public
    active: Whether project is active
list_work_package_relationsC

Get all relations for a work package.

Args:
    work_package_id: Work package ID
create_relationB

Create a relation between two work packages.

Args:
    from_id: Source work package ID
    to_id: Target work package ID
    relation_type: Type of relation (relates, duplicates, blocks, precedes, follows, includes, partof, requires)
    lag: Optional lag in days for precedes/follows relations
get_relationC

Get details of a specific relation.

Args:
    relation_id: Relation ID
delete_relationB

Remove a relation between work packages.

Args:
    relation_id: Relation ID to delete

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 21 tools

Disambiguation5/5

Every tool has a clearly distinct purpose focused on specific resources and actions in the OpenProject domain. Tools are well-separated by resource type (work packages, projects, relations, comments, watchers) and operation (create, get, list, update, delete), with no apparent overlap that would cause confusion.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern throughout, using clear action verbs (create, get, list, update, delete, add, remove, set) followed by specific resource nouns. The naming is predictable and follows the same convention across all 21 tools.

Tool Count4/5

With 21 tools, the count is slightly high but reasonable for a comprehensive project management system. The tools cover multiple resource types (work packages, projects, relations, comments, watchers, activities) with full CRUD operations, making the count justifiable though bordering on the heavy side.

Completeness5/5

The tool surface provides complete coverage for the OpenProject domain with full CRUD operations for all major resources (work packages, projects, relations, comments). It includes specialized operations like watcher management, parent-child relationships, schema retrieval, and activity tracking, leaving no obvious gaps for agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources