casky-mcp-wrapper

A thin MCP server fronting Casky's Platform API v1. Built on Vercel's mcp-handler.

Status

CASKY_API_KEY configured
Set
MCP_WRAPPER_AUTH_TOKEN configured
Set — /api/mcp requires a matching bearer token
Casky API reachable
Connected to https://casky.ai — 6 run(s) visible to this key

Last checked: 8/1/2026, 4:43:09 PM

Connect Hermes Agent (or any MCP client)

MCP endpoint: https://<this-deployment>/api/mcp

Add this to ~/.hermes/config.yaml:

mcp_servers:
  casky-platform:
    url: "https://<this-deployment>/api/mcp"
    headers:
      Authorization: "Bearer ${MCP_WRAPPER_AUTH_TOKEN}"   # only if one is configured

Tools exposed

Tool	Casky route	What it's for
`list_plans`	`GET /api/v1/plans`	Find a plan_id + skill_slug to run.
`create_run`	`POST /api/v1/runs`	Starts a run — returns run_id + a reporting JWT. Does not execute the skill.
`list_runs`	`GET /api/v1/runs`	Poll status of runs created via create_run.

No findings-read tool — there's no GET /api/v1/runs/{id} route yet. Findings are reported by the runner via a separate, non-v1 endpoint.

Endpoints

GET /api/health — liveness check
GET /api/status— this page's checks, as JSON
POST /api/mcp — the MCP Streamable HTTP endpoint