WhyEva MCP Server

Overview #

The WhyEva MCP server implements the Model Context Protocol over Streamable HTTP. It exposes tools that AI agents can invoke to read and write data in your WhyEva account — without writing a single line of integration code.

The server uses the JSON-RPC 2.0 transport over a single POST /mcp endpoint. Authentication is performed via a standard JWT Bearer token.

Endpoint #

All MCP requests are sent to a single endpoint:

The server supports only the POST method. GET and DELETE return 405 Method Not Allowed.

Authentication #

The MCP endpoint requires a valid JWT Bearer token. Obtain one by logging in through the WhyEva API and pass it with every request.

POST https://my.whyeva.com/api/account/login
Content-Type: application/json

{
  "email": "user@example.com",
  "password": "your-password"
}

Authorization: Bearer <your-access-token>

Quick Connect #

Add the WhyEva MCP server to your AI client by pasting the configuration below. Replace with the Bearer token obtained from the step above.

{
  "mcpServers": {
    "whyeva": {
      "url": "https://my.whyeva.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

{
  "mcpServers": {
    "whyeva": {
      "type": "http",
      "url": "https://my.whyeva.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

{
  "servers": {
    "whyeva": {
      "type": "http",
      "url": "https://my.whyeva.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:whyevaToken}"
      }
    }
  },
  "inputs": [
    {
      "id": "whyevaToken",
      "type": "promptString",
      "description": "WhyEva JWT Bearer Token",
      "password": true
    }
  ]
}

{
  "mcpServers": {
    "whyeva": {
      "serverUrl": "https://my.whyeva.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

curl -X POST https://my.whyeva.com/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <YOUR_TOKEN>" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2024-11-05",
      "capabilities": {},
      "clientInfo": { "name": "my-agent", "version": "1.0" }
    }
  }'

Tools #

The server exposes 29 tools grouped into three categories. Call tools/list to retrieve the full list with JSON Schema definitions at runtime.

Vacancies  16 tools

Questions  6 tools

Candidates  7 tools

JSON-RPC Methods #

The server implements MCP Streamable HTTP transport using JSON-RPC 2.0.

initialize

Performs the MCP handshake and returns server capabilities.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "initialize",
  "params": {
    "protocolVersion": "2024-11-05",
    "capabilities": {},
    "clientInfo": { "name": "my-agent", "version": "1.0" }
  }
}

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "protocolVersion": "2024-11-05",
    "capabilities": { "tools": { "listChanged": false } },
    "serverInfo": { "name": "WhyEva-MCP", "version": "1.0.0" }
  }
}

tools/list

Returns all available tools with their JSON Schema definitions.

{ "jsonrpc": "2.0", "id": 2, "method": "tools/list" }

tools/call

Invokes a specific tool by name, passing arguments as a JSON object.

{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "getVacancy",
    "arguments": {
      "vacancyId": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
    }
  }
}

notifications/initialized

Sent by the client after a successful initialize. The server returns 200 OK with no body.

Error Codes #