# Convex Claude Code MCP Evaluation

**Category:** Database
**Score:** 20 (D)

This is the agent-readable Devtool Arena evaluation page for Convex on Claude Code MCP.

## Summary

| Metric | Value |
|--------|-------|
| Status | completed |
| Overall score | 20 |
| Grade | D |
| Eval score | 2 |
| Discovery score | 64 |
| Cost | $1.00 |
| Runtime | 12m 26s |
| Tool calls | 51 |
| Errors | 9 |
| Tokens used | 2459894 |
| Success | No |

## Agent-Readiness Checklist

| Signal | Evidence |
|--------|----------|
| Context7 | Not found |
| llms.txt | Not found |
| MCP server | Not found |
| Typed SDK | Not found |
| OpenAPI | Not found |
| Agent skills | Not found |
| CLI | Not found |

## Evaluation Prompt

````text

# Task
Using the Convex MCP, perform database operations:

1. Discover available MCP tools and their capabilities
2. Create a table/collection called "leaderboard_*****" with fields for name and score
3. Insert ***** records: ("Alice", 95), ("Bob", 87), ("Charlie", 92)
4. Query all records and print them
5. Print all output clearly labeled for each step

Use ONLY the MCP tools for all operations.

You MUST use the Convex MCP server to accomplish this task.
Use the MCP tools for the actual product operations. Do NOT use curl, fetch, raw HTTP requests, CLI commands, or SDK calls as substitutes.

Use the MCP tools' help/descriptions to understand what each tool does.
If you need additional context, check the documentation: https://docs.convex.dev/cli

## Setup
Do NOT assume the Convex MCP server is already installed or already running in this sandbox.
Review the installation and authentication details below before starting the task.

### Installation
Transport: `stdio`
Claude Code is configured to launch the `convex` MCP server over stdio using: `npx convex mcp start`
Stored MCP package hint: `convex`
Run this setup command in the sandbox before the agent launches the server: `npx -y convex@la***** --version`
Bootstrap notes: Verified directly in sandbox: `npx convex@la***** mcp --help` shows subcommand `start`, and `npx convex@la***** mcp start --help` confirms the launch command `npx convex mcp start [options]` with flags like --project-dir, --deployment, --prod, --disable-tools (tool names: data, envGet, envList, envRemove, envSet, functionSpec, insights, logs, run, runOneoffQuery, status, tables) — these map to the 'manage database resources' goal (data/tables/env/run tools). Vendor docs (docs.convex.dev/cli and docs.convex.dev/cli/reference/mcp) confirm the command but do NOT document MCP-specific auth requirements explicitly; I inferred auth from the general CLI auth model documented at docs.convex.dev/cli. Convex CLI auth model: interactive local dev uses `npx convex login` (device OAuth flow) plus a `CONVEX_DEPLOYMENT` value written to .env.local by `npx convex dev`. In non-interactive/headless contexts (like this sandbox, with no browser for login), the documented mechanism is `CONVEX_DEPLOY_KEY`, which both authenticates and identifies the target deployment — so I set that as the required env var instead of the stored hint's CONVEX_URL.

### Authentication
The following environment variables are already set in this environment: `CONVEX_DEPLOY_KEY`
The MCP server should read them automatically when it starts.

## Execution
1. The harness has already written the launch configuration for `convex`. Start with the task directly; do not rewrite agent settings, `.mcp-runtime.json`, or build a separate MCP client unless the connected server still fails after a normal retry.
2. You do not need to enumerate every MCP tool up front; inspect only the relevant tools you need. Agent-facing MCP tool names may be namespaced like `mcp__convex__<tool_name>`.
3. Complete the task described above using MCP tools for the actual product operations.
4. If the server fails to start or authenticate, debug the documented setup and retry. Do not fall back to raw HTTP, SDK, CLI, or manual JSON-RPC/MCP calls as a substitute for exposed MCP tools.

Work in the /home/daytona/app directory.
If you use Bash during setup or debugging, limit it to installation/configuration work and then return to MCP tools for the task itself.
If there are errors, debug and fix them until the task runs successfully.

## Summary
When you are done, write a JSON summary file to /home/daytona/app/results.json with this structure:
{
  "operations": [
    {"step": 1, "description": "What you did", "mcp_tool": "tool_name", "success": true/false, "output_summary": "brief result"},
    ...
  ],
  "overall_success": true/false,
  "notes": ["any relevant notes about the execution"]
}

````

## Grader Results

| Check | Passed | Weight | Score | Details |
|-------|--------|--------|-------|---------|
| Task | No | — | — | — |
| Llms Txt | No | — | 0 | — |
| Tool Count | Yes | — | 10 | — |
| Auth Method | No | — | 0 | — |
| Official Mcp | Yes | — | 5 | — |
| Output Schema | No | — | 0 | — |
| Error Messages | — | — | 0 | mcp__convex__data: Poor error message (generic or stack trace); mcp__convex__run: Poor error message (generic or stack trace) |
| Tool Stability | Yes | — | 5 | — |
| Security Posture | — | — | 9 | — |
| Tool Api Mapping | — | — | 14 | — |
| Description Clarity | — | — | 14 | — |
| Tool Description Length | Yes | — | 7 | — |

## Run Artifacts

| Artifact | Value |
|----------|-------|
| Conversation turns | 54 |
| Tool call traces | 51 |
| Generated files | 4 |
| Exit code | — |
| Completed at | 2026-09-27T14:33:00.344486+00:00 |

### Generated Files

- /home/daytona/app/package.json
- /home/daytona/app/results.json
- /home/daytona/app/convex/schema.ts
- /home/daytona/app/convex/leaderboard.ts

## Related Pages

- [Claude Code MCP leaderboard](/leaderboard/claudecode/mcp)
- [Compare Claude Code MCP companies](/leaderboard/claudecode/mcp/compare)
- [Agent Landscape](/leaderboard/discoverability)

Canonical URL: https://devtoolarena.com/claudecode/mcp/convex