@runhuman/mcp-server 1.1.0 → 2.0.0

package/.env.example

@@ -1,12 +1,12 @@
-# RunHuman API Configuration
-
-# API Base URL
-# For local development, use http://localhost:3400
-# For production, use your deployed API URL
-RUNHUMAN_API_URL=http://localhost:3400
-
-# API Key
-# Get this from the API dashboard at http://localhost:3400/app.html
-# Or use the default test key below for local development
-# Format: qa_live_xxxxxxxxxxxxxxxxxxxxx
-RUNHUMAN_API_KEY=qa_live_test_key_for_demo_purposes_only_12345
+# RunHuman API Configuration
+
+# API Base URL
+# For local development, use http://localhost:3400
+# For production, use your deployed API URL
+RUNHUMAN_API_URL=http://localhost:3400
+
+# API Key
+# Get this from the API dashboard at http://localhost:3400/app.html
+# Or use the default test key below for local development
+# Format: qa_live_xxxxxxxxxxxxxxxxxxxxx
+RUNHUMAN_API_KEY=qa_live_test_key_for_demo_purposes_only_12345

package/README.md

@@ -1,219 +1,219 @@
-# RunHuman MCP Server
-
-A Model Context Protocol (MCP) server that allows AI agents to interact with the RunHuman QA testing service.
-
-## Overview
-
-This MCP server provides tools for creating and managing human QA jobs through the RunHuman API. AI agents can use this server to:
-
-- Create new QA jobs with custom schemas
-- Check the status of running jobs
-- Retrieve completed job results
-
-## Installation
-
-### For Claude Desktop (Recommended)
-
-1. Get your API key at: https://runhuman.com/app.html
-
-2. Add to your Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json` on Mac):
-
-```json
-{
-  "mcpServers": {
-    "runhuman": {
-      "command": "npx",
-      "args": ["-y", "@runhuman/mcp-server", "--api-key=qa_live_xxxxxxxxxxxxx"]
-    }
-  }
-}
-```
-
-3. Restart Claude Desktop
-
-That's it! The server will be automatically downloaded and run by Claude.
-
-### For Development
-
-From the monorepo root:
-
-```bash
-npm install
-npm run build --workspace=@runhuman/mcp-server
-
-# Run with API key
-node packages/mcp-server/dist/index.js --api-key=qa_live_xxxxx
-```
-
-### Available Tools
-
-#### `create_job`
-Create a new QA job with human testers.
-
-**Parameters:**
-- `url` (string): The URL to test
-- `description` (string): Instructions for the human tester describing what to test
-- `schema` (object): Expected result schema that the tester response will be extracted into
-
-#### `get_job_status`
-Get the current status of a QA job.
-
-**Parameters:**
-- `jobId` (string): The ID of the job to check
-
-#### `get_job_result`
-Get the results of a completed QA job.
-
-**Parameters:**
-- `jobId` (string): The ID of the completed job
-
-**Returns:**
-- `result`: Structured test results extracted from tester's response
-- `status`: Job status (completed, failed, etc.)
-- `costUsd`: Exact cost in USD with full precision (e.g., 0.396)
-- `testDurationSeconds`: Time spent by tester in seconds (rounded up)
-- Additional metadata (timestamps, tester info, etc.)
-
-**Cost Calculation:**
-- Costs are calculated as: `duration × $0.0018/second` (general-use tier)
-- Duration is always rounded UP using Math.ceil (any partial second counts)
-- Costs are never $0 unless the tester never actually worked on it
-- Full precision maintained (not rounded to cents)
-
-## Configuration
-
-The MCP server needs to be configured with your RunHuman API credentials.
-
-### 1. Get an API Key
-
-**Option A: Via Dashboard**
-1. Start the API server: `npm run dev --workspace=@runhuman/api`
-2. Open http://localhost:3400/app.html
-3. Go to "API Keys" tab
-4. Click "Create API Key"
-5. Copy the key (starts with `qa_live_`)
-
-**Option B: Use Default Test Key**
-- For local development, you can use: `qa_live_test_key_123`
-- This key exists in `packages/api/data/api-keys.json`
-
-### 2. Configure Environment Variables
-
-Create a `.env` file in the MCP server directory:
-
-```bash
-# For local development
-RUNHUMAN_API_URL=http://localhost:3400
-RUNHUMAN_API_KEY=qa_live_test_key_123
-
-# For production
-RUNHUMAN_API_URL=https://api.runhuman.com
-RUNHUMAN_API_KEY=qa_live_xxxxxxxxxxxxxxxxxxxxx
-```
-
-**Important:** Never commit `.env` files to git! They're already in `.gitignore`.
-
-### 3. Verify Configuration
-
-Test your API key works:
-
-```bash
-curl http://localhost:3400/api/jobs \
-  -H "Authorization: Bearer qa_live_test_key_123" \
-  -H "Content-Type: application/json" \
-  -d '{"url":"https://example.com","description":"test","outputSchema":{}}'
-```
-
-Should return a job ID if authentication works.
-
-For more details, see [docs/API-AUTHENTICATION.md](docs/API-AUTHENTICATION.md)
-
-## Testing
-
-The MCP server includes automated tests to verify it's working correctly:
-
-```bash
-# Build first
-npm run build --workspace=@runhuman/mcp-server
-
-# Run simple automated test
-npm run test --workspace=@runhuman/mcp-server
-
-# Or use the MCP Inspector (interactive testing)
-npm run test:inspector --workspace=@runhuman/mcp-server
-```
-
-The test script will:
-1. ✅ Initialize a connection to the MCP server
-2. ✅ List all available tools (create_job, get_job_status, get_job_result)
-3. ✅ Test calling the create_job tool
-
-### Expected Test Output
-
-```
-✅ Server initialized successfully
-✅ Tools listed: create_job, get_job_status, get_job_result
-✅ create_job tool called successfully
-```
-
-## Development
-
-```bash
-# Watch mode (auto-rebuild on changes)
-npm run dev --workspace=@runhuman/mcp-server
-
-# Build
-npm run build --workspace=@runhuman/mcp-server
-
-# Test after building
-npm run test --workspace=@runhuman/mcp-server
-```
-
-## Integration with Claude Desktop
-
-To use this MCP server with Claude Desktop, add it to your configuration:
-
-```json
-{
-  "mcpServers": {
-    "runhuman": {
-      "command": "node",
-      "args": ["/path/to/qa-experiment/packages/mcp-server/dist/index.js"]
-    }
-  }
-}
-```
-
-## Example Usage
-
-Once connected to an AI agent (like Claude), the agent can use these tools naturally:
-
-**User:** "Can someone test my checkout page at https://myapp.com/checkout?"
-
-**Agent uses create_job:**
-```
-✅ Job created successfully!
-Job ID: job_abc123
-Status: pending
-...
-```
-
-**Agent polls get_job_status until complete, then calls get_job_result:**
-```
-✅ Test completed!
-Results Summary:
-- Checkout Flow: ✅ Working
-- Payment Processing: ✅ Successful
-...
-```
-
-## Developer Documentation
-
-For developers working on this MCP server:
-- [docs/HOW-AGENTS-USE-MCP.md](docs/HOW-AGENTS-USE-MCP.md) - How AI agents discover and use MCP servers
-- [docs/TOOL-RESPONSE-BEST-PRACTICES.md](docs/TOOL-RESPONSE-BEST-PRACTICES.md) - Best practices for tool responses
-
-## Learn More
-
-- [Model Context Protocol Documentation](https://modelcontextprotocol.io/)
-- [RunHuman API Documentation](../api/README.md)
+# RunHuman MCP Server
+
+A Model Context Protocol (MCP) server that allows AI agents to interact with the RunHuman QA testing service.
+
+## Overview
+
+This MCP server provides tools for creating and managing human QA jobs through the RunHuman API. AI agents can use this server to:
+
+- Create new QA jobs with custom schemas
+- Check the status of running jobs
+- Retrieve completed job results
+
+## Installation
+
+### For Claude Desktop (Recommended)
+
+1. Get your API key at: https://runhuman.com/app.html
+
+2. Add to your Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json` on Mac):
+
+```json
+{
+  "mcpServers": {
+    "runhuman": {
+      "command": "npx",
+      "args": ["-y", "@runhuman/mcp-server", "--api-key=qa_live_xxxxxxxxxxxxx"]
+    }
+  }
+}
+```
+
+3. Restart Claude Desktop
+
+That's it! The server will be automatically downloaded and run by Claude.
+
+### For Development
+
+From the monorepo root:
+
+```bash
+npm install
+npm run build --workspace=@runhuman/mcp-server
+
+# Run with API key
+node packages/mcp-server/dist/index.js --api-key=qa_live_xxxxx
+```
+
+### Available Tools
+
+#### `create_job`
+Create a new QA job with human testers.
+
+**Parameters:**
+- `url` (string): The URL to test
+- `description` (string): Instructions for the human tester describing what to test
+- `schema` (object): Expected result schema that the tester response will be extracted into
+
+#### `get_job_status`
+Get the current status of a QA job.
+
+**Parameters:**
+- `jobId` (string): The ID of the job to check
+
+#### `get_job_result`
+Get the results of a completed QA job.
+
+**Parameters:**
+- `jobId` (string): The ID of the completed job
+
+**Returns:**
+- `result`: Structured test results extracted from tester's response
+- `status`: Job status (completed, failed, etc.)
+- `costUsd`: Exact cost in USD with full precision (e.g., 0.396)
+- `testDurationSeconds`: Time spent by tester in seconds (rounded up)
+- Additional metadata (timestamps, tester info, etc.)
+
+**Cost Calculation:**
+- Costs are calculated as: `duration × $0.0018/second` (general-use tier)
+- Duration is always rounded UP using Math.ceil (any partial second counts)
+- Costs are never $0 unless the tester never actually worked on it
+- Full precision maintained (not rounded to cents)
+
+## Configuration
+
+The MCP server needs to be configured with your RunHuman API credentials.
+
+### 1. Get an API Key
+
+**Option A: Via Dashboard**
+1. Start the API server: `npm run dev --workspace=@runhuman/api`
+2. Open http://localhost:3400/app.html
+3. Go to "API Keys" tab
+4. Click "Create API Key"
+5. Copy the key (starts with `qa_live_`)
+
+**Option B: Use Default Test Key**
+- For local development, you can use: `qa_live_test_key_123`
+- This key exists in `packages/api/data/api-keys.json`
+
+### 2. Configure Environment Variables
+
+Create a `.env` file in the MCP server directory:
+
+```bash
+# For local development
+RUNHUMAN_API_URL=http://localhost:3400
+RUNHUMAN_API_KEY=qa_live_test_key_123
+
+# For production
+RUNHUMAN_API_URL=https://api.runhuman.com
+RUNHUMAN_API_KEY=qa_live_xxxxxxxxxxxxxxxxxxxxx
+```
+
+**Important:** Never commit `.env` files to git! They're already in `.gitignore`.
+
+### 3. Verify Configuration
+
+Test your API key works:
+
+```bash
+curl http://localhost:3400/api/jobs \
+  -H "Authorization: Bearer qa_live_test_key_123" \
+  -H "Content-Type: application/json" \
+  -d '{"url":"https://example.com","description":"test","outputSchema":{}}'
+```
+
+Should return a job ID if authentication works.
+
+For more details, see [docs/API-AUTHENTICATION.md](docs/API-AUTHENTICATION.md)
+
+## Testing
+
+The MCP server includes automated tests to verify it's working correctly:
+
+```bash
+# Build first
+npm run build --workspace=@runhuman/mcp-server
+
+# Run simple automated test
+npm run test --workspace=@runhuman/mcp-server
+
+# Or use the MCP Inspector (interactive testing)
+npm run test:inspector --workspace=@runhuman/mcp-server
+```
+
+The test script will:
+1. ✅ Initialize a connection to the MCP server
+2. ✅ List all available tools (create_job, get_job_status, get_job_result)
+3. ✅ Test calling the create_job tool
+
+### Expected Test Output
+
+```
+✅ Server initialized successfully
+✅ Tools listed: create_job, get_job_status, get_job_result
+✅ create_job tool called successfully
+```
+
+## Development
+
+```bash
+# Watch mode (auto-rebuild on changes)
+npm run dev --workspace=@runhuman/mcp-server
+
+# Build
+npm run build --workspace=@runhuman/mcp-server
+
+# Test after building
+npm run test --workspace=@runhuman/mcp-server
+```
+
+## Integration with Claude Desktop
+
+To use this MCP server with Claude Desktop, add it to your configuration:
+
+```json
+{
+  "mcpServers": {
+    "runhuman": {
+      "command": "node",
+      "args": ["/path/to/qa-experiment/packages/mcp-server/dist/index.js"]
+    }
+  }
+}
+```
+
+## Example Usage
+
+Once connected to an AI agent (like Claude), the agent can use these tools naturally:
+
+**User:** "Can someone test my checkout page at https://myapp.com/checkout?"
+
+**Agent uses create_job:**
+```
+✅ Job created successfully!
+Job ID: job_abc123
+Status: pending
+...
+```
+
+**Agent polls get_job_status until complete, then calls get_job_result:**
+```
+✅ Test completed!
+Results Summary:
+- Checkout Flow: ✅ Working
+- Payment Processing: ✅ Successful
+...
+```
+
+## Developer Documentation
+
+For developers working on this MCP server:
+- [docs/HOW-AGENTS-USE-MCP.md](docs/HOW-AGENTS-USE-MCP.md) - How AI agents discover and use MCP servers
+- [docs/TOOL-RESPONSE-BEST-PRACTICES.md](docs/TOOL-RESPONSE-BEST-PRACTICES.md) - Best practices for tool responses
+
+## Learn More
+
+- [Model Context Protocol Documentation](https://modelcontextprotocol.io/)
+- [RunHuman API Documentation](../api/README.md)

package/dist/index.js

@@ -75,22 +75,22 @@ server.setRequestHandler(ListToolsRequestSchema, async () => {
         tools: [
             {
                 name: 'create_job',
-                description: `⚠️ IMPORTANT: This ONLY creates and queues a job. It does NOT perform the test or return results. You MUST follow up with get_job_status and get_job_result.
-
-Creates a QA job that will be performed by a REAL HUMAN tester (not AI). The human will manually test your application, describe findings in natural language, and GPT-4o will extract structured data from their response.
-
-Use this when you need human verification of:
-- UI/UX functionality that's hard to automate
-- Visual issues, accessibility problems
-- Complex user flows (login, checkout, forms)
-- Cross-browser compatibility
-- Real user experience feedback
-
-⚠️ REQUIRED WORKFLOW (do NOT skip steps):
-1. create_job → Returns jobId (job is now QUEUED, not complete!)
-2. get_job_status → Poll every 30-60 seconds until status="completed" (takes 2-10 min)
-3. get_job_result → Retrieve the actual test results
-
+                description: `⚠️ IMPORTANT: This ONLY creates and queues a job. It does NOT perform the test or return results. You MUST follow up with get_job_status and get_job_result.
+
+Creates a QA job that will be performed by a REAL HUMAN tester (not AI). The human will manually test your application, describe findings in natural language, and GPT-4o will extract structured data from their response.
+
+Use this when you need human verification of:
+- UI/UX functionality that's hard to automate
+- Visual issues, accessibility problems
+- Complex user flows (login, checkout, forms)
+- Cross-browser compatibility
+- Real user experience feedback
+
+⚠️ REQUIRED WORKFLOW (do NOT skip steps):
+1. create_job → Returns jobId (job is now QUEUED, not complete!)
+2. get_job_status → Poll every 30-60 seconds until status="completed" (takes 2-10 min)
+3. get_job_result → Retrieve the actual test results
+
 DO NOT treat job creation as completion. You MUST wait for and retrieve results.`,
                 inputSchema: {
                     type: 'object',
@@ -117,10 +117,10 @@ DO NOT treat job creation as completion. You MUST wait for and retrieve results.
             },
             {
                 name: 'get_job_status',
-                description: `Check the current status of a QA job. Jobs progress through states: pending → claimed → in_progress → completed (or failed/timeout).
-
-Use this to poll for completion before fetching results. Typical job completion time is 2-10 minutes depending on test complexity.
-
+                description: `Check the current status of a QA job. Jobs progress through states: pending → claimed → in_progress → completed (or failed/timeout).
+
+Use this to poll for completion before fetching results. Typical job completion time is 2-10 minutes depending on test complexity.
+
 Returns: { status: "pending" | "claimed" | "in_progress" | "completed" | "failed" | "timeout", message: "..." }`,
                 inputSchema: {
                     type: 'object',
@@ -135,10 +135,10 @@ Returns: { status: "pending" | "claimed" | "in_progress" | "completed" | "failed
             },
             {
                 name: 'get_job_result',
-                description: `Get the structured results of a completed QA job. Only call this after get_job_status shows status="completed".
-
-Returns the tester's response extracted into your specified schema, plus metadata about timing and the raw tester response.
-
+                description: `Get the structured results of a completed QA job. Only call this after get_job_status shows status="completed".
+
+Returns the tester's response extracted into your specified schema, plus metadata about timing and the raw tester response.
+
 If the job isn't complete yet, returns an error. If extraction failed, includes the raw response so you can see what the tester said.`,
                 inputSchema: {
                     type: 'object',
@@ -184,14 +184,14 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
                     return {
                         content: [{
                                 type: 'text',
-                                text: `❌ Failed to create job
-
-Error: ${error.error || error.message || response.statusText}
-Status: ${response.status}
-
-Please check:
-- Your RUNHUMAN_API_KEY is valid
-- The API server is running at ${API_URL}
+                                text: `❌ Failed to create job
+
+Error: ${error.error || error.message || response.statusText}
+Status: ${response.status}
+
+Please check:
+- Your RUNHUMAN_API_KEY is valid
+- The API server is running at ${API_URL}
 - Your API key has permission to create jobs`
                             }],
                         isError: true
@@ -203,21 +203,21 @@ Please check:
                     content: [
                         {
                             type: 'text',
-                            text: `⏳ Job QUEUED (not complete yet!)
-
-Job ID: ${data.jobId}
-Status: ${data.status}
-URL: ${args.url}
-Time limit: ${duration} minutes
-
-The test has been queued for a HUMAN tester. It is NOT complete yet.
-
-⚠️ REQUIRED NEXT STEPS:
-1. Wait 30-60 seconds
-2. Call get_job_status(jobId: "${data.jobId}") to check if complete
-3. Repeat step 2 until status="completed" (typical time: 2-10 minutes)
-4. Call get_job_result(jobId: "${data.jobId}") to get the actual test results
-
+                            text: `⏳ Job QUEUED (not complete yet!)
+
+Job ID: ${data.jobId}
+Status: ${data.status}
+URL: ${args.url}
+Time limit: ${duration} minutes
+
+The test has been queued for a HUMAN tester. It is NOT complete yet.
+
+⚠️ REQUIRED NEXT STEPS:
+1. Wait 30-60 seconds
+2. Call get_job_status(jobId: "${data.jobId}") to check if complete
+3. Repeat step 2 until status="completed" (typical time: 2-10 minutes)
+4. Call get_job_result(jobId: "${data.jobId}") to get the actual test results
+
 DO NOT consider this task done until you have retrieved the results!`,
                         },
                     ],
@@ -227,13 +227,13 @@ DO NOT consider this task done until you have retrieved the results!`,
                 return {
                     content: [{
                             type: 'text',
-                            text: `❌ Error creating job
-
-${error instanceof Error ? error.message : 'Unknown error'}
-
-Please check:
-- The API server is running at ${API_URL}
-- Your network connection
+                            text: `❌ Error creating job
+
+${error instanceof Error ? error.message : 'Unknown error'}
+
+Please check:
+- The API server is running at ${API_URL}
+- Your network connection
 - Your .env file configuration`
                         }],
                     isError: true
@@ -251,10 +251,10 @@ Please check:
                         return {
                             content: [{
                                     type: 'text',
-                                    text: `❌ Job not found
-
-Job ID: ${args.jobId}
-
+                                    text: `❌ Job not found
+
+Job ID: ${args.jobId}
+
 The job does not exist or you don't have permission to access it.`
                                 }],
                             isError: true
@@ -263,9 +263,9 @@ The job does not exist or you don't have permission to access it.`
                     return {
                         content: [{
                                 type: 'text',
-                                text: `❌ Failed to get job status
-
-Status: ${response.status}
+                                text: `❌ Failed to get job status
+
+Status: ${response.status}
 Error: ${response.statusText}`
                             }],
                         isError: true
@@ -281,8 +281,8 @@ Error: ${response.statusText}`
                     timeout: '⏰'
                 };
                 const emoji = statusEmoji[job.status] || '📊';
-                let message = `${emoji} Job Status: ${job.status}
-
+                let message = `${emoji} Job Status: ${job.status}
+
 Job ID: ${job.id}`;
                 if (job.status === 'pending') {
                     message += '\n\nWaiting for a tester to claim this job...\nTypical completion time: 2-10 minutes';
@@ -310,8 +310,8 @@ Job ID: ${job.id}`;
                 return {
                     content: [{
                             type: 'text',
-                            text: `❌ Error checking job status
-
+                            text: `❌ Error checking job status
+
 ${error instanceof Error ? error.message : 'Unknown error'}`
                         }],
                     isError: true
@@ -329,10 +329,10 @@ ${error instanceof Error ? error.message : 'Unknown error'}`
                         return {
                             content: [{
                                     type: 'text',
-                                    text: `❌ Job not found
-
-Job ID: ${args.jobId}
-
+                                    text: `❌ Job not found
+
+Job ID: ${args.jobId}
+
 The job does not exist or you don't have permission to access it.`
                                 }],
                             isError: true
@@ -341,9 +341,9 @@ The job does not exist or you don't have permission to access it.`
                     return {
                         content: [{
                                 type: 'text',
-                                text: `❌ Failed to get job result
-
-Status: ${response.status}
+                                text: `❌ Failed to get job result
+
+Status: ${response.status}
 Error: ${response.statusText}`
                             }],
                         isError: true
@@ -354,11 +354,11 @@ Error: ${response.statusText}`
                     return {
                         content: [{
                                 type: 'text',
-                                text: `⏳ Job not yet completed
-
-Job ID: ${job.id}
-Current status: ${job.status}
-
+                                text: `⏳ Job not yet completed
+
+Job ID: ${job.id}
+Current status: ${job.status}
+
 ${job.status === 'pending' ? 'Waiting for a tester to claim this job...' :
                                     job.status === 'claimed' || job.status === 'in_progress' ? 'The tester is working on your test...' :
                                         job.status === 'failed' ? '❌ Job failed. Error: ' + (job.error || 'Unknown error') :
@@ -368,10 +368,10 @@ ${job.status === 'pending' ? 'Waiting for a tester to claim this job...' :
                     };
                 }
                 // Job is completed, format results
-                const message = `✅ Test completed!
-
-Job ID: ${job.id}
-
+                const message = `✅ Test completed!
+
+Job ID: ${job.id}
+
 **Test Results:**`;
                 const contents = [
                     {
@@ -395,8 +395,8 @@ Job ID: ${job.id}
                 return {
                     content: [{
                             type: 'text',
-                            text: `❌ Error getting job result
-
+                            text: `❌ Error getting job result
+
 ${error instanceof Error ? error.message : 'Unknown error'}`
                         }],
                     isError: true

package/package.json

@@ -1,62 +1,62 @@
-{
-  "name": "@runhuman/mcp-server",
-  "version": "1.1.0",
-  "description": "Model Context Protocol (MCP) server for RunHuman - Human-powered QA testing for AI agents",
-  "main": "dist/index.js",
-  "type": "module",
-  "bin": {
-    "runhuman-mcp": "dist/index.js"
-  },
-  "files": [
-    "dist",
-    "README.md",
-    ".env.example"
-  ],
-  "scripts": {
-    "build": "tsc",
-    "dev": "tsx watch src/index.ts",
-    "start": "node dist/index.js",
-    "prepublishOnly": "npm run build",
-    "test": "node test-simple.cjs",
-    "test:all": "node test-all-tools.cjs",
-    "test:routes": "node test-route-fix.cjs",
-    "test:endpoints": "node test-api-endpoints.cjs",
-    "test:ci": "npm run test:endpoints && npm run test:routes",
-    "test:inspector": "npx @modelcontextprotocol/inspector node dist/index.js"
-  },
-  "keywords": [
-    "mcp",
-    "model-context-protocol",
-    "qa",
-    "testing",
-    "human-in-the-loop",
-    "ai-agent",
-    "claude",
-    "anthropic",
-    "qa-testing",
-    "manual-testing"
-  ],
-  "author": "RunHuman <hey@runhuman.com>",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/yueranyuan/qa-experiment.git",
-    "directory": "packages/mcp-server"
-  },
-  "homepage": "https://runhuman.com",
-  "bugs": {
-    "url": "https://github.com/yueranyuan/qa-experiment/issues"
-  },
-  "license": "ISC",
-  "engines": {
-    "node": ">=18.0.0"
-  },
-  "dependencies": {
-    "@modelcontextprotocol/sdk": "latest",
-    "dotenv": "^17.2.3"
-  },
-  "devDependencies": {
-    "@types/node": "^20.11.17",
-    "tsx": "^4.7.1",
-    "typescript": "^5.3.3"
-  }
-}
+{
+  "name": "@runhuman/mcp-server",
+  "version": "2.0.0",
+  "description": "Model Context Protocol (MCP) server for RunHuman - Human-powered QA testing for AI agents",
+  "main": "dist/index.js",
+  "type": "module",
+  "bin": {
+    "runhuman-mcp": "dist/index.js"
+  },
+  "files": [
+    "dist",
+    "README.md",
+    ".env.example"
+  ],
+  "scripts": {
+    "build": "tsc",
+    "dev": "tsx watch src/index.ts",
+    "start": "node dist/index.js",
+    "prepublishOnly": "npm run build",
+    "test": "node test-simple.cjs",
+    "test:all": "node test-all-tools.cjs",
+    "test:routes": "node test-route-fix.cjs",
+    "test:endpoints": "node test-api-endpoints.cjs",
+    "test:ci": "npm run test:endpoints && npm run test:routes",
+    "test:inspector": "npx @modelcontextprotocol/inspector node dist/index.js"
+  },
+  "keywords": [
+    "mcp",
+    "model-context-protocol",
+    "qa",
+    "testing",
+    "human-in-the-loop",
+    "ai-agent",
+    "claude",
+    "anthropic",
+    "qa-testing",
+    "manual-testing"
+  ],
+  "author": "RunHuman <hey@runhuman.com>",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/yueranyuan/qa-experiment.git",
+    "directory": "packages/mcp-server"
+  },
+  "homepage": "https://runhuman.com",
+  "bugs": {
+    "url": "https://github.com/yueranyuan/qa-experiment/issues"
+  },
+  "license": "ISC",
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "latest",
+    "dotenv": "^17.2.3"
+  },
+  "devDependencies": {
+    "@types/node": "^20.11.17",
+    "tsx": "^4.7.1",
+    "typescript": "^5.3.3"
+  }
+}