MCP Setup Guide

Set MCP_API_KEY in this Next.js app environment and redeploy.

# .env.local or Vercel env
MCP_API_KEY=your_same_mcp_api_key
NEXT_PUBLIC_APP_BASE_URL=https://person-search-siddayao.vercel.app

Recommended for Claude Desktop: use mcp-remote bridge config.

{
  "mcpServers": {
    "person-crud": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://person-search-siddayao.vercel.app/api/mcp",
        "--header",
        "x-mcp-api-key:your_same_mcp_api_key"
      ]
    }
  }
}

Optional fallback (only if your Claude build supports direct streamable HTTP transport):

{
  "mcpServers": {
    "person-crud": {
      "transport": "streamable-http",
      "url": "https://person-search-siddayao.vercel.app/api/mcp",
      "headers": {
        "x-mcp-api-key": "your_same_mcp_api_key"
      }
    }
  }
}

After connecting, run tools/list and confirm these CRUD tools appear.

Available MCP tools:
- person_create(name, email, phoneNumber)
- person_list(query?)
- person_get(id)
- person_update(id, name?, email?, phoneNumber?)
- person_delete(id)

Run these checks:

• Create person via Claude Desktop tool call.
• List/search person and confirm record exists.
• Update person fields and verify persisted values.
• Delete person and confirm it no longer appears in list results.

Use the in-app live tester at /mcp-demo for evaluator-visible request logs and JSON responses.