⚠️ This is an early-stage project. Do not use it productively – contributions welcome!

OpenProject MCP Server

A Model Context Protocol (MCP) server that provides seamless integration with OpenProject API v3. This server enables LLM applications to interact with OpenProject for project management, work package tracking, and task creation.

Features

• 🔌 Full OpenProject API v3 Integration

• 📋 Project Management: List and filter projects

• 📝 Work Package Management: Create, list, and filter work packages

• 🏷️ Type Management: List available work package types

• 🔐 Secure Authentication: API key-based authentication

• 🌐 Proxy Support: Optional HTTP proxy configuration

• 🚀 Async Operations: Built with modern async/await patterns

• 📊 Comprehensive Logging: Configurable logging levels

Related MCP server: OpenProject MCP Server

Prerequisites

• Python 3.10 or higher

• uv (fast Python package manager)

• An OpenProject instance (cloud or self-hosted)

• OpenProject API key (generated from your user profile)

Installation

1. Install uv (if not already installed)

macOS/Linux:

curl -LsSf https://astral.sh/uv/install.sh | sh

Windows:

powershell -c "irm https://astral.sh/uv/install.ps1 | iex"

Alternative (using pip):

pip install uv

2. Clone and Setup the Project

git clone https://github.com/yourusername/openproject-mcp.git
cd openproject-mcp

3. Create Virtual Environment and Install Dependencies

# Create virtual environment and install dependencies in one command
uv sync

Alternative (manual steps):

# Create virtual environment
uv venv

# Install dependencies
uv pip install -r requirements.txt

4. Configure Environment

# Copy the environment template
cp env_example.txt .env

Edit .env and add your OpenProject configuration:

OPENPROJECT_URL=https://your-instance.openproject.com
OPENPROJECT_API_KEY=your-api-key-here

Configuration

Environment Variables

Getting an API Key

1. Log in to your OpenProject instance

2. Go to My account (click your avatar)

3. Navigate to Access tokens

4. Click + Add to create a new token

5. Give it a name and copy the generated token

Usage

Deployment Options

This MCP server can be deployed in two ways:

1. Local (stdio): Run on your local machine for personal use

2. Cloud (SSE): Deploy to FastMCP Cloud for team/organization access

Option 1: Local Deployment (stdio)

Running the Server

Using uv (recommended):

uv run python openproject-mcp-fastmcp.py

Alternative (manual activation):

# Activate virtual environment
source .venv/bin/activate  # On Windows: .venv\Scripts\activate

# Run the server
python openproject-mcp-fastmcp.py

File Structure:

• openproject-mcp-fastmcp.py - Stdio transport (for local Claude Desktop)

• openproject-mcp-sse.py - SSE transport (for FastMCP Cloud)

• src/ - Core implementation using FastMCP framework

  • src/server.py - FastMCP server initialization

  • src/client.py - OpenProject API client

  • src/tools/ - All 40+ MCP tools organized by category

Integration with Claude Desktop

Quick Install Using CLI (Recommended):

This command works for both Claude Desktop and Claude Code (VSCode extension).

# Windows - Replace <YOUR_PROJECT_PATH> with your actual path
claude mcp add openproject-fastmcp "<YOUR_PROJECT_PATH>\.venv\Scripts\python.exe" "<YOUR_PROJECT_PATH>\openproject-mcp-fastmcp.py" -e "PYTHONPATH=<YOUR_PROJECT_PATH>" -e "OPENPROJECT_URL=https://your-instance.com" -e "OPENPROJECT_API_KEY=your-api-key"

# macOS/Linux - Replace <YOUR_PROJECT_PATH> with your actual path
claude mcp add openproject-fastmcp "<YOUR_PROJECT_PATH>/.venv/bin/python" "<YOUR_PROJECT_PATH>/openproject-mcp-fastmcp.py" -e "PYTHONPATH=<YOUR_PROJECT_PATH>" -e "OPENPROJECT_URL=https://your-instance.com" -e "OPENPROJECT_API_KEY=your-api-key"

Example (Windows):

# If you cloned the project to C:\Users\YourName\openproject-mcp-server
claude mcp add openproject-fastmcp "C:\Users\YourName\openproject-mcp-server\.venv\Scripts\python.exe" "C:\Users\YourName\openproject-mcp-server\openproject-mcp-fastmcp.py" -e "PYTHONPATH=C:\Users\YourName\openproject-mcp-server" -e "OPENPROJECT_URL=https://manage.example.com" -e "OPENPROJECT_API_KEY=abc123xyz456"

Example (macOS/Linux):

# If you cloned the project to /home/yourname/openproject-mcp-server
claude mcp add openproject-fastmcp "/home/yourname/openproject-mcp-server/.venv/bin/python" "/home/yourname/openproject-mcp-server/openproject-mcp-fastmcp.py" -e "PYTHONPATH=/home/yourname/openproject-mcp-server" -e "OPENPROJECT_URL=https://manage.example.com" -e "OPENPROJECT_API_KEY=abc123xyz456"

Important: Replace the following values:

• <YOUR_PROJECT_PATH> with your actual installation directory

• https://your-instance.com with your OpenProject URL

• your-api-key with your API key from Account Settings

Verify Installation:

claude mcp list

You should see:

openproject-fastmcp: ... - ✓ Connected

After running the command, restart Claude Desktop or reload VSCode window.

Manual Configuration:

Add this configuration to your Claude Desktop config file:

Config file locations:

• Windows: %APPDATA%\Claude\claude_desktop_config.json

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

• Linux: ~/.config/Claude/claude_desktop_config.json

Windows Configuration:

{
  "mcpServers": {
    "openproject-fastmcp": {
      "command": "D:\\Promete\\Project\\mcp-openproject\\openproject-mcp-server\\.venv\\Scripts\\python.exe",
      "args": ["D:\\Promete\\Project\\mcp-openproject\\openproject-mcp-server\\openproject-mcp-fastmcp.py"],
      "env": {
        "PYTHONPATH": "D:\\Promete\\Project\\mcp-openproject\\openproject-mcp-server",
        "OPENPROJECT_URL": "https://your-instance.com",
        "OPENPROJECT_API_KEY": "your-api-key"
      }
    }
  }
}

macOS/Linux Configuration:

{
  "mcpServers": {
    "openproject-fastmcp": {
      "command": "/path/to/project/.venv/bin/python",
      "args": ["/path/to/project/openproject-mcp-fastmcp.py"],
      "env": {
        "PYTHONPATH": "/path/to/project",
        "OPENPROJECT_URL": "https://your-instance.com",
        "OPENPROJECT_API_KEY": "your-api-key"
      }
    }
  }
}

Note: Using environment variables in config is more secure than storing credentials in .env file.

Verification:

Check if the server is connected:

claude mcp list

You should see:

openproject-fastmcp: ... - ✓ Connected

If you see ✗ Failed to connect, check:

1. Python path is correct

2. openproject-mcp-fastmcp.py file exists

3. Environment variables are set correctly

4. Restart Claude Desktop after configuration changes

Option 2: Cloud Deployment (FastMCP Cloud) ☁️

Deploy to FastMCP Cloud for centralized access across your organization. This eliminates the need for each user to install Python and run the server locally.

Benefits:

• No local installation required for end users

• Centralized API key and configuration management

• Access from anywhere with internet

• Automatic scaling and monitoring

• Team collaboration features

Quick Start:

1. Ensure you have the SSE entry point:

   # The project includes openproject-mcp-sse.py for cloud deployment
   ls openproject-mcp-sse.py

2. Create/update .fastmcp.yaml config:

   name: openproject-mcp
   version: "1.0.0"
   description: "OpenProject MCP Server for Claude Desktop"
   
   entry_point: openproject-mcp-sse.py
   
   runtime:
     python_version: "3.11"
   
   environment:
     - OPENPROJECT_URL
     - OPENPROJECT_API_KEY
     - OPENPROJECT_PROXY

3. Deploy to FastMCP Cloud:

   # Install FastMCP CLI (if not installed)
   pip install fastmcp
   
   # Login to FastMCP Cloud
   fastmcp login
   
   # Deploy your server
   fastmcp deploy

4. Configure environment variables on FastMCP Cloud dashboard:

   • OPENPROJECT_URL: Your OpenProject instance URL

   • OPENPROJECT_API_KEY: Your API key

   • OPENPROJECT_PROXY: (Optional) Proxy URL if needed

5. Users connect via Claude Desktop with SSE transport:

   {
     "mcpServers": {
       "openproject": {
         "url": "https://mcp.fastmcp.com/sse/openproject-mcp",
         "transport": "sse"
       }
     }
   }

📚 Detailed Documentation:

• Quick Start Guide - Fast setup in 5 minutes

• FastMCP Cloud Deployment Guide (English) - Comprehensive guide

• Hướng dẫn kết nối Cloud (Tiếng Việt) - Vietnamese guide

For comprehensive deployment instructions, troubleshooting, and best practices, see the guides above.

Available Tools

1. test_connection

Test the connection to your OpenProject instance.

Example:

Test the OpenProject connection

2. list_projects

List all projects you have access to.

Parameters:

• active_only (boolean, optional): Show only active projects (default: true)

Example:

List all active projects

3. list_work_packages ⭐ ENHANCED

List work packages with advanced filtering capabilities - the most powerful search tool.

Basic Parameters:

• project_id (integer, optional): Filter by project

• assignee_id (integer, optional): Filter by assignee

• active_only (boolean, optional): Only open tasks (default: true)

• offset (integer, optional): Pagination offset (default: 0)

• page_size (integer, optional): Results per page (default: 20, max: 100)

Advanced Filters (NEW - 18 parameters):

• priority_ids (string, optional): Comma-separated priority IDs (e.g., "3,4")

• type_ids (string, optional): Comma-separated type IDs (e.g., "1,2")

• status_ids (string, optional): Comma-separated status IDs (overrides active_only)

• version_ids (string, optional): Comma-separated version/sprint IDs

• due_before (string, optional): Due before date (YYYY-MM-DD)

• due_after (string, optional): Due after date (YYYY-MM-DD)

• created_after (string, optional): Created after date (YYYY-MM-DD)

• updated_after (string, optional): Updated after date (YYYY-MM-DD)

• unassigned_only (boolean, optional): Only unassigned tasks

• overdue_only (boolean, optional): Only overdue tasks

• percentage_done_min (integer, optional): Min completion % (0-100)

• percentage_done_max (integer, optional): Max completion % (0-100)

• author_id (integer, optional): Filter by task creator

• parent_id (integer, optional): Child tasks of parent

• no_parent_only (boolean, optional): Only top-level tasks

Features:

• 23 total parameters for ultimate flexibility

• All filters use AND logic

• 100% backward compatible

• Smart filter priority (e.g., status_ids > active_only)

Examples:

Find high-priority bugs due this week in project 5

Find overdue unassigned tasks

Show tasks 50-80% complete

4. search_work_packages

Search work packages by subject or ID using server-side filtering.

Parameters:

• query (string, required): Search text to match against work package subject or ID

• project_id (integer, optional): Limit search to a specific project

• active_only (boolean, optional): Search only open work packages (default: true)

• offset (integer, optional): Starting index for pagination (default: 0)

• page_size (integer, optional): Number of results per page (default: 20, max: 100)

Example:

Search for tasks containing "login"

Search for work package by ID: "123"

Note: This tool provides fast search without needing to paginate through all tasks. Use this when you need to find specific tasks by name or ID.

5. list_types

List available work package types.

Parameters:

• project_id (integer, optional): Filter types by project

Example:

List all work package types

6. create_work_package

Create a new work package.

Parameters:

• project_id (integer, required): The project ID

• subject (string, required): Work package title

• type_id (integer, required): Type ID (e.g., 1 for Task)

• description (string, optional): Description in Markdown format

• priority_id (integer, optional): Priority ID

• assignee_id (integer, optional): User ID to assign to

Example:

Create a new task in project 5 titled "Update documentation" with type ID 1

7. list_users

List all users in the OpenProject instance.

Parameters:

• active_only (boolean, optional): Show only active users (default: true)

8. get_user

Get detailed information about a specific user.

Parameters:

• user_id (integer, required): User ID

9. list_memberships

List project memberships showing users and their roles.

Parameters:

• project_id (integer, optional): Filter by specific project

• user_id (integer, optional): Filter by specific user

10. list_statuses

List all available work package statuses.

11. list_priorities

List all available work package priorities.

12. get_work_package

Get detailed information about a specific work package.

Parameters:

• work_package_id (integer, required): Work package ID

13. update_work_package

Update an existing work package.

Parameters:

• work_package_id (integer, required): Work package ID

• subject (string, optional): Work package title

• description (string, optional): Description in Markdown format

• type_id (integer, optional): Type ID

• status_id (integer, optional): Status ID

• priority_id (integer, optional): Priority ID

• assignee_id (integer, optional): User ID to assign to

• percentage_done (integer, optional): Completion percentage (0-100)

13. delete_work_package

Delete a work package.

Parameters:

• work_package_id (integer, required): Work package ID

Advanced Filters 🔍

The following tools provide specialized filtering capabilities for common work package search scenarios. All tools support flexible filtering by project, assignee, priority, and type.

14. list_overdue_work_packages

List all work packages that are past their due date.

Parameters:

• project_id (integer, optional): Filter by project

• assignee_id (integer, optional): Filter by assignee

• priority_ids (string, optional): Comma-separated priority IDs (e.g., "3,4")

• type_ids (string, optional): Comma-separated type IDs (e.g., "1,2")

• page_size (integer, optional): Results per page (default: 50, max: 100)

Features:

• Shows "X days overdue" for each task

• Sorted by most overdue first

• Only searches open (non-closed) tasks

Example:

Find all overdue high-priority tasks in project 5

15. list_work_packages_due_soon

List work packages due within the next N days.

Parameters:

• days (integer, optional): Days to look ahead (default: 7, max: 365)

• project_id (integer, optional): Filter by project

• assignee_id (integer, optional): Filter by assignee

• priority_ids (string, optional): Comma-separated priority IDs

• page_size (integer, optional): Results per page (default: 50, max: 100)

Features:

• Shows "Due in X days", "Due tomorrow", or "Due today!"

• Sorted by soonest first

• Configurable lookahead period

Example:

Show me tasks due in the next 3 days

16. list_unassigned_work_packages

List work packages that have no assignee.

Parameters:

• project_id (integer, optional): Filter by project

• priority_ids (string, optional): Comma-separated priority IDs

• type_ids (string, optional): Comma-separated type IDs

• active_only (boolean, optional): Only open tasks (default: true)

• page_size (integer, optional): Results per page (default: 50, max: 100)

Features:

• Identifies tasks needing assignment

• Useful for sprint planning

• Supports priority and type filtering

Example:

Find unassigned high-priority bugs in project 5

17. list_work_packages_created_recently

List work packages created in the last N days.

Parameters:

• days (integer, optional): Days to look back (default: 7, max: 365)

• project_id (integer, optional): Filter by project

• assignee_id (integer, optional): Filter by assignee

• type_ids (string, optional): Comma-separated type IDs

• active_only (boolean, optional): Only open tasks (default: true)

• page_size (integer, optional): Results per page (default: 50, max: 100)

Features:

• Track new task creation patterns

• Sorted by newest first

• Configurable lookback period

Example:

Show bugs created in the last 3 days

18. list_high_priority_work_packages

List work packages with high priority.

Parameters:

• project_id (integer, optional): Filter by project

• assignee_id (integer, optional): Filter by assignee

• type_ids (string, optional): Comma-separated type IDs

• active_only (boolean, optional): Only open tasks (default: true)

• page_size (integer, optional): Results per page (default: 50, max: 100)

Features:

• Assumes priority ID 3 = "High" (typical default)

• Includes helpful note about using list_priorities if needed

• Quick access to urgent tasks

Example:

Show all high-priority tasks in project 5

Note: If your OpenProject instance uses different priority IDs, use list_priorities to find the correct ID, then use the enhanced list_work_packages with specific priority_ids parameter.

19. list_work_packages_nearly_complete

List work packages that are nearly complete (high percentage done).

Parameters:

• project_id (integer, optional): Filter by project

• assignee_id (integer, optional): Filter by assignee

• min_percentage (integer, optional): Minimum completion % (default: 80, range: 1-99)

• active_only (boolean, optional): Only open tasks (default: true)

• page_size (integer, optional): Results per page (default: 50, max: 100)

Features:

• Find tasks needing final push

• Sorted by highest percentage first

• Includes completion summary section

• Useful for sprint reviews

Example:

Show tasks more than 90% complete

20. list_time_entries

List time entries with optional filtering.

Parameters:

• work_package_id (integer, optional): Filter by specific work package

• user_id (integer, optional): Filter by specific user

15. create_time_entry

Create a new time entry.

Parameters:

• work_package_id (integer, required): Work package ID

• hours (number, required): Hours spent (e.g., 2.5)

• spent_on (string, required): Date when time was spent (YYYY-MM-DD format)

• comment (string, optional): Comment/description

• activity_id (integer, optional): Activity ID

16. update_time_entry

Update an existing time entry.

Parameters:

• time_entry_id (integer, required): Time entry ID

• hours (number, optional): Hours spent

• spent_on (string, optional): Date when time was spent

• comment (string, optional): Comment/description

• activity_id (integer, optional): Activity ID

17. delete_time_entry

Delete a time entry.

Parameters:

• time_entry_id (integer, required): Time entry ID

18. list_time_entry_activities

List available time entry activities.

19. list_versions

List project versions/milestones.

Parameters:

• project_id (integer, optional): Filter by specific project

20. create_version

Create a new project version/milestone.

Parameters:

• project_id (integer, required): Project ID

• name (string, required): Version name

• description (string, optional): Version description

• start_date (string, optional): Start date (YYYY-MM-DD format)

• end_date (string, optional): End date (YYYY-MM-DD format)

• status (string, optional): Version status (open, locked, closed)

21. create_project

Create a new project.

Parameters:

• name (string, required): Project name

• identifier (string, required): Project identifier (unique)

• description (string, optional): Project description

• public (boolean, optional): Whether the project is public

• status (string, optional): Project status

• parent_id (integer, optional): Parent project ID

Example:

Create a new project named "Website Redesign" with identifier "web-redesign"

22. update_project

Update an existing project.

Parameters:

• project_id (integer, required): Project ID

• name (string, optional): Project name

• identifier (string, optional): Project identifier

• description (string, optional): Project description

• public (boolean, optional): Whether the project is public

• status (string, optional): Project status

• parent_id (integer, optional): Parent project ID

23. delete_project

Delete a project.

Parameters:

• project_id (integer, required): Project ID

24. get_project

Get detailed information about a specific project.

Parameters:

• project_id (integer, required): Project ID

25. create_membership

Create a new project membership.

Parameters:

• project_id (integer, required): Project ID

• user_id (integer, optional): User ID (required if group_id not provided)

• group_id (integer, optional): Group ID (required if user_id not provided)

• role_ids (array, optional): Array of role IDs

• role_id (integer, optional): Single role ID (alternative to role_ids)

• notification_message (string, optional): Optional notification message

Example:

Add user 5 to project 2 with role ID 3 (Developer role)

26. update_membership

Update an existing membership.

Parameters:

• membership_id (integer, required): Membership ID

• role_ids (array, optional): Array of role IDs

• role_id (integer, optional): Single role ID

• notification_message (string, optional): Optional notification message

27. delete_membership

Delete a membership.

Parameters:

• membership_id (integer, required): Membership ID

28. get_membership

Get detailed information about a specific membership.

Parameters:

• membership_id (integer, required): Membership ID

29. list_project_members

List all members of a specific project.

Parameters:

• project_id (integer, required): Project ID

Example:

List all members of project 5

30. list_user_projects

List all projects a specific user is assigned to.

Parameters:

• user_id (integer, required): User ID

31. list_roles

List all available roles.

Example:

List all available roles in the OpenProject instance

32. get_role

Get detailed information about a specific role.

Parameters:

• role_id (integer, required): Role ID

33. set_work_package_parent

Set a parent for a work package (create parent-child relationship).

Parameters:

• work_package_id (integer, required): Work package ID to become a child

• parent_id (integer, required): Work package ID to become the parent

Example:

Set work package 15 as a child of work package 10

34. remove_work_package_parent

Remove parent relationship from a work package (make it top-level).

Parameters:

• work_package_id (integer, required): Work package ID to remove parent from

35. list_work_package_children

List all child work packages of a parent.

Parameters:

• parent_id (integer, required): Parent work package ID

• include_descendants (boolean, optional): Include grandchildren and all descendants (default: false)

Example:

List all children of work package 10 including descendants

36. create_work_package_relation

Create a relationship between work packages.

Parameters:

• from_id (integer, required): Source work package ID

• to_id (integer, required): Target work package ID

• relation_type (string, required): Relation type (blocks, follows, precedes, relates, duplicates, includes, requires, partof)

• lag (integer, optional): Lag in working days (for follows/precedes)

• description (string, optional): Optional description of the relation

Example:

Create a "blocks" relation where work package 5 blocks work package 8

37. list_work_package_relations

List work package relations with optional filtering.

Parameters:

• work_package_id (integer, optional): Filter relations involving this work package ID

• relation_type (string, optional): Filter by relation type

38. update_work_package_relation

Update an existing work package relation.

Parameters:

• relation_id (integer, required): Relation ID

• relation_type (string, optional): New relation type

• lag (integer, optional): Lag in working days

• description (string, optional): Optional description

39. delete_work_package_relation

Delete a work package relation.

Parameters:

• relation_id (integer, required): Relation ID

40. get_work_package_relation

Get detailed information about a specific work package relation.

Parameters:

• relation_id (integer, required): Relation ID

Development

Setting up Development Environment

# Install development dependencies
uv sync --extra dev

# Or install manually
uv pip install -e ".[dev]"

Running Tests

uv run pytest tests/

Code Formatting

# Format code
uv run black openproject-mcp.py

# Lint code
uv run flake8 openproject-mcp.py

Adding Dependencies

# Add a new dependency
uv add package-name

# Add a development dependency
uv add --dev package-name

# Update dependencies
uv sync

Tool Compatibility & Test Results

✅ Fully Working Tools (40/42)

All these tools have been tested and work correctly with admin privileges:

Core Project Management:

• test_connection, check_permissions, list_projects, create_project, update_project

• delete_project, get_project

Work Package Management:

• list_work_packages, search_work_packages, list_types, create_work_package, update_work_package

• delete_work_package, get_work_package, list_statuses, list_priorities

Work Package Hierarchy & Relations:

• set_work_package_parent, remove_work_package_parent, list_work_package_children

• create_work_package_relation, list_work_package_relations, update_work_package_relation

• delete_work_package_relation, get_work_package_relation

User & Membership Management:

• list_users, get_user, create_membership, update_membership, delete_membership

• get_membership, list_project_members, list_user_projects, list_roles, get_role

Time Tracking:

• list_time_entries, create_time_entry, update_time_entry, delete_time_entry

Project Versions:

• list_versions, create_version

⚠️ Partially Working Tools

• list_memberships: Works globally and with project_id filtering. User ID filtering (user_id) may not be supported in all OpenProject instances.

❌ Endpoint Limitations with Workarounds

• list_time_entry_activities: Returns 404 but time entry activities ARE functional! Use these predefined activity IDs:

  • Management (ID: 1): Administrative and planning tasks

  • Specification (ID: 2): Requirements and documentation

  • Development (ID: 3): Coding and implementation

  • Testing (ID: 4): Quality assurance and testing

Example: create_time_entry with activity_id: 3 for Development work

Permission Requirements

Most create/update/delete operations require appropriate permissions:

• Project Operations: Require global "Create project" and "Edit project" permissions. Deletion typically requires admin rights

• Work Package Operations: Require "Create/Edit work packages" permission in target projects

• Work Package Relations & Hierarchy: Require "Edit work packages" permission for creating/modifying parent-child relationships and dependencies

• Membership Management: Require "Manage members" permission for target projects

• Time Entry Operations: Require time tracking permissions

• Version Management: Require project admin or version management permissions

• User Operations: Admin privileges may be needed for comprehensive user management

• Role Management: Read-only operations generally available; admin privileges may be needed for detailed role information

Use the check_permissions tool to diagnose permission-related issues.

Troubleshooting

Connection Issues

1. 401 Unauthorized: Check your API key is correct and active

2. 403 Forbidden: Ensure your user has the necessary permissions

3. 404 Not Found: Verify the OpenProject URL and that resources exist

4. Proxy Errors: Check proxy settings and authentication

Debug Mode

Enable debug logging by setting:

LOG_LEVEL=DEBUG

Common Issues

• No projects found: Ensure your API user has project view permissions

• SSL errors: May occur with self-signed certificates or proxy SSL interception

• Timeout errors: Increase timeout or check network connectivity

Security Considerations

• Never commit your .env file to version control

• Use environment variables for sensitive data

• Rotate API keys regularly

• Use HTTPS for all OpenProject connections

• Configure proxy authentication securely if needed

Contributing

1. Fork the repository

2. Create a feature branch (git checkout -b feature/amazing-feature)

3. Commit your changes (git commit -m 'Add amazing feature')

4. Push to the branch (git push origin feature/amazing-feature)

5. Open a Pull Request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

• Built for the Model Context Protocol

• Integrates with OpenProject

• Inspired by the MCP community

Support

• 🐛 Issues: GitHub Issues

• 💬 Discussions: GitHub Discussions