MCP

Wellbyte exposes a constant MCP tool set to agents (Claude / Cursor) so one-tool-per-endpoint does not explode context.

Quick start

npx -y @wellbyte/mcp

{
  "mcpServers": {
    "wellbyte": {
      "command": "npx",
      "args": ["-y", "@wellbyte/mcp"],
      "env": {
        "WELLBYTE_API_KEY": "dg_live_xxx",
        "WELLBYTE_PROFILE": "<profile-uuid>",
        "WELLBYTE_API_BASE": "https://api.wellbyte.dev"
      }
    }
  }
}

Create a Profile under Console → MCP and copy the JSON (stdio or remote).

Remote

npx -y -p @wellbyte/mcp wellbyte-mcp-http

{
  "mcpServers": {
    "wellbyte": {
      "url": "https://mcp.wellbyte.io/mcp?profile=<uuid>",
      "headers": { "Authorization": "Bearer dg_live_xxx" }
    }
  }
}

Tool flow

1. search_endpoints — discover

2. get_endpoint_schema — inspect

3. call_endpoint / create_job / monitors / datasets — execute

Same billing as HTTP /v1 (failures free). See SDK and /mcp.