Side-by-Side Model Context Protocol Comparison

Redmine MCP Stdio vs Procore MCP Server

Q: What is the key difference between Redmine MCP Stdio and Procore MCP Server?

Redmine MCP Stdio belongs to the Product Management category with local stdio execution, while Procore MCP Server belongs to the Product Management category with local stdio execution.

Q: How do I install Redmine MCP Stdio or Procore MCP Server in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Q: Are Redmine MCP Stdio and Procore MCP Server free or paid?

Redmine MCP Stdio operates under a Free / Open Source model (API Key required). Procore MCP Server operates under a Free / Open Source model (OAuth 2.0).

Q: Which MCP server has more tools and community activity?

Redmine MCP Stdio lists 12 tools with 2 views and 0 GitHub stars. Procore MCP Server lists 6 tools with 3 views and 8 GitHub stars.

Q: Can I use both Redmine MCP Stdio and Procore MCP Server together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

In-depth architectural comparison of the Redmine MCP Stdio and Procore MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Redmine MCP Stdio

Product Management · Local stdio

Quality: 55/100 (Good) | Auth: API Key required

Procore MCP Server

Product Management · Local stdio

Quality: 45/100 (Fair) | Auth: OAuth 2.0

Verdict Summary: Choose Redmine MCP Stdio if you need specialized Product Management tools running via a local process. Choose Procore MCP Server if your workspace requires Product Management integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Redmine MCP Stdio when:

You need dedicated capabilities in the Product Management domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: REDMINE_URL, REDMINE_API_KEY.
Primary tools included: list_issues, get_issue, list_projects.

Explore Redmine MCP Stdio Details

Choose Procore MCP Server when:

You need dedicated capabilities in the Product Management domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: PROCORE_CLIENT_ID, PROCORE_CLIENT_SECRET, PROCORE_COMPANY_ID, PROCORE_TOOL_MODE.

Feature & Specification Comparison

Specification	Redmine MCP Stdio andrelaptenok Product Management	Procore MCP Server TylerIlunga Product Management
Summary	Search, read, create and update Redmine issues, projects and time entries from any MCP client. 12 tools with MCP safety annotations: full-text search, issue journals with attachments, comments and time tracking. npx -y redmine-mcp-stdio	MCP server exposing the full Procore REST API (2,636 endpoints) for construction project management. Includes 7 discovery and execution tools covering projects, RFIs, submittals, daily logs, budgets, and more. Single-user OAuth with auto-refresh.
Category & Scope

Tools & Capabilities Breakdown

Redmine MCP Stdio Tools (12)

list_issues

List/filter issues, paginated

get_issue

Full details of one issue + comments/history + attachments

list_projects

Accessible projects

get_project

Project details, versions and members

create_issue

Create an issue

update_issue

Update issue fields

add_comment

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Redmine MCP Stdio Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "andrelaptenok-redmine-mcp-stdio": {
      "command": "npx",
      "args": [
        "-y",
        "redmine-mcp-stdio"
      ],
      "env": {
        "REDMINE_URL": "YOUR_REDMINE_URL_HERE",
        "REDMINE_API_KEY": "YOUR_REDMINE_API_KEY_HERE"
      }
    }
  }
}

Procore MCP Server Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "tylerilunga-procore-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "tylerilunga-procore-mcp-server"
      ],
      "env": {
        "PROCORE_CLIENT_ID": "YOUR_PROCORE_CLIENT_ID_HERE",
        "PROCORE_CLIENT_SECRET": "YOUR_PROCORE_CLIENT_SECRET_HERE",
        "PROCORE_COMPANY_ID": "YOUR_PROCORE_COMPANY_ID_HERE",
        "PROCORE_TOOL_MODE": "YOUR_PROCORE_TOOL_MODE_HERE"
      }
    }
  }
}

Frequently Asked Questions

Redmine MCP Stdio is categorized under Product Management and uses a local stdio subprocess. In contrast, Procore MCP Server belongs to Product Management using local stdio subprocess. Select Redmine MCP Stdio when you need capabilities focused on product management and Procore MCP Server when you require tools for product management.

More alternatives to Redmine MCP Stdio More alternatives to Procore MCP Server Product Management category hub