rhodecode-mcp-server

MCP server that exposes RhodeCode (Rhodecode/Bitbucket-compatible SCM) functionality as MCP tools so AI agents can interact with repositories/issues/changes through the MCP protocol.

Evaluated Apr 04, 2026 (27d ago)
Homepage ↗ Repo ↗ DevTools mcp developer-tools integration scm rhodecode automation agent-tools
⚙ Agent Friendliness
40
/ 100
Can an agent use this?
🔒 Security
40
/ 100
Is it safe for agents?
⚡ Reliability
32
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
40
Error Messages
0
Auth Simplicity
45
Rate Limits
20

🔒 Security

TLS Enforcement
50
Auth Strength
40
Scope Granularity
30
Dep. Hygiene
40
Secret Handling
40

Authentication, TLS enforcement, and secret handling practices were not provided in the supplied input. As an MCP wrapper over a SCM system, it likely requires credentials; ensure transport security (HTTPS/TLS), least-privilege tokens, and that logs do not include secrets. Rate-limit and input validation behavior are unknown.

⚡ Reliability

Uptime/SLA
0
Version Stability
50
Breaking Changes
50
Error Recovery
30
AF Security Reliability

Best When

You already use MCP in your agent stack and want RhodeCode capabilities exposed as tool calls.

Avoid When

You need documented REST/GraphQL APIs, strong OAuth scopes, or you cannot access or verify the MCP server configuration/documentation.

Use Cases

  • • Enable AI agents to perform RhodeCode operations (e.g., browse repos, inspect changes, manage issues) via MCP tools
  • • Automate repository triage and status checks from an agent workflow
  • • Integrate RhodeCode data into agent-based code review or incident response workflows

Not For

  • • Direct production trading/financial operations
  • • Highly regulated workflows that require audited, domain-specific guarantees not documented in the MCP server
  • • Use cases requiring a full REST/SDK experience rather than MCP tool calls

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

OAuth: No Scopes: No

No authentication details were provided in the supplied input. MCP servers commonly rely on RhodeCode credentials (e.g., tokens/basic auth) but this cannot be confirmed without the actual README/manifests.

Pricing

Free tier: No
Requires CC: No

No pricing information provided; assumed self-hosted/open-source package unless stated otherwise, but not confirmed.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • ⚠ MCP tool implementations may not be explicitly documented for pagination; agents may need to implement their own paging/continuation strategy if supported
  • ⚠ Without explicit idempotency guarantees, repeated tool calls could duplicate actions (e.g., creating comments/tickets)
  • ⚠ Auth/config issues are common in self-hosted MCP servers; ensure correct environment variables/connection details before agent use

Alternatives

Using RhodeCode’s native REST API directly (if available) Building your own MCP wrapper around RhodeCode’s API Using an existing generic SCM integration/MCP server (if it supports RhodeCode)

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for rhodecode-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo
API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
♥
Community Powered