MCP server

The VernaOne MCP server exposes your prompts and flows to MCP clients (Claude Desktop, Cursor, and others) as tools — so an assistant can list, run, and manage your governed prompts directly.

It runs in two transports:

• Local (stdio) — one project, credentials from environment variables. Best for a single developer’s client.
• Remote (Streamable HTTP) — multi-tenant, credentials per request. Hosted at https://mcp.promptlab.vernalabs.net/mcp.

Local (stdio) — Claude Desktop / Cursor

Add VernaOne to your MCP client config:

{
  "mcpServers": {
    "vernaone": {
      "command": "node",
      "args": ["/absolute/path/to/promptlab-mcp-server/dist/index.js"],
      "env": {
        "PROMPTLAB_API_KEY": "plp_xxx_xxx",
        "PROMPTLAB_PROJECT_ID": "YOUR_PROJECT_ID"
      }
    }
  }
}

The stdio server calls the Router at https://router.promptlab.vernalabs.net by default; override with PROMPTLAB_ROUTER_URL if needed.

Remote (Streamable HTTP)

Point an MCP client that supports Streamable HTTP at the hosted endpoint and pass your credentials as headers on each request:

POST https://mcp.promptlab.vernalabs.net/mcp
x-api-key: plp_xxx_xxx
x-promptlab-project-id: YOUR_PROJECT_ID

Authorization: Bearer plp_… is accepted as an alias for x-api-key. Health check: GET https://mcp.promptlab.vernalabs.net/healthz.

Tools

The server exposes full read and write access to prompts and flows:

Prompts — list_prompts, get_prompt, execute_prompt, upsert_prompt, delete_prompt, get_job

Flows — run_flow, get_flow_run, list_flow_runs, cancel_flow_run, get_flow, upsert_flow, delete_flow, list_flow_versions, get_flow_version, activate_flow_version, delete_flow_version

Because these tools can create and delete prompts and flows, scope the API key you give an MCP client carefully — see Authentication.