🚀 EasyProject MCP Server

What is EasyProject MCP Server?

EasyProject MCP Server is a Model Context Protocol server that integrates with the EasyProject API, enabling the use of EasyProject tools directly within the Cursor AI editor. It is designed for developers and project managers who want to manage projects, tasks, users, time tracking, and reports without leaving their code editor.

How to use EasyProject MCP Server?

Install via Cargo, Docker, or build from source. Configure using a TOML file or environment variables (EASYPROJECT_API_KEY, EASYPROJECT_BASE_URL). For Cursor, add the server to your mcpServers configuration. Invoke tools such as list_projects, create_issue, or log_time using @easyproject <tool_name>.

Key features of EasyProject MCP Server

• Full MCP protocol implementation for EasyProject API
• Project CRUD: create, update, delete, list projects
• Issue management with assignment and completion
• User management and workload analysis
• Time tracking: log and manage time entries
• Reporting: generate project reports and dashboard data
• In-memory caching with configurable TTL per entity
• Rate limiting and automatic retry on failed requests
• Structured JSON logging and extensive configuration

Use cases of EasyProject MCP Server

• Create and update project issues directly from Cursor
• Assign tasks to team members and mark them complete
• Track work time by logging entries against projects
• Generate detailed project reports with time and issue data
• View user workloads and dashboard summaries

FAQ from EasyProject MCP Server

What runtime dependencies are required?

Rust 1.70+ for building from source, or a pre-built binary. An active EasyProject instance and a valid API key are mandatory.

How does authentication work?

Authentication uses an API key sent via the X-Redmine-API-Key header. The key must be set via the EASYPROJECT_API_KEY environment variable or in the config file.

What transports are supported?

The server supports both stdio and websocket transports. The default is stdio; websocket can be enabled in the configuration with a configurable port.

What are the rate limits and how can they be adjusted?

Rate limiting is enabled by default at 60 requests per minute with a burst size of 10. These values can be changed in the [rate_limiting] section of the config.

How can I clear the cache or troubleshoot caching issues?

Restart the server or set cache.enabled = false in the configuration to disable caching. Debug logging can be enabled with the RUST_LOG=debug environment variable.