recursor-mcp-server

recursor-mcp-server is an MCP server package intended to expose Recursor-related capabilities to AI agents via the Model Context Protocol (MCP).

Evaluated Apr 04, 2026 (27d ago)
Homepage ↗ Repo ↗ DevTools mcp agents tooling integration devtools
⚙ Agent Friendliness
35
/ 100
Can an agent use this?
🔒 Security
28
/ 100
Is it safe for agents?
⚡ Reliability
25
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
35
Error Messages
0
Auth Simplicity
40
Rate Limits
10

🔒 Security

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

No concrete security implementation details were provided (TLS, auth, scopes, secret handling, and dependency posture cannot be confirmed from the given input). Treat as unverified until you review the repository code/docs.

⚡ Reliability

Uptime/SLA
0
Version Stability
40
Breaking Changes
40
Error Recovery
20
AF Security Reliability

Best When

You are building an agent platform that already supports MCP and you want Recursor capabilities exposed as MCP tools.

Avoid When

You need strong guarantees around auth/scopes, pagination semantics, or retry/idempotency behavior but documentation/specs are missing.

Use Cases

  • Agent-mediated access to Recursor functions/tools
  • Tool-using assistants that need a standardized MCP integration
  • Building agent workflows where Recursor operations are invoked as MCP tools

Not For

  • Direct end-user applications that need a browser UI
  • Use cases requiring a traditional REST/GraphQL/SDK interface without MCP
  • Production environments where API contracts, auth, and error behaviors are not clearly documented

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 input, so auth method/scopes cannot be verified.

Pricing

Free tier: No
Requires CC: No

No pricing information was provided.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • MCP tool schemas and required parameters are not provided here; agents may guess fields and trigger errors.
  • Without documented retry/idempotency semantics, agents may unintentionally duplicate operations on transient failures.
  • Without documented rate limit headers/limits, agents may over-call and receive throttling responses.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for recursor-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

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

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