superserve.ai
Superserve exposes a control-plane HTTP API at `https://api.superserve.ai` (OpenAPI-backed, mostly `X-API-Key`, with one public billing endpoint), a sandbox data-plane HTTP API at `https://sandbox.superserve.ai` / `https://boxd-{sandbox_id}.sandbox.superserve.ai` authenticated by per-sandbox `X-Access-Token`, plus an MCP server available as hosted Streamable HTTP at `https://mcp.superserve.ai` or local `npx -y @superserve/mcp`, both using your Superserve API key.
- Superserve MCP Server (hosted)detected
- Superserve Control Plane APIdiscovered
- Superserve MCP Server CLI (local stdio)discovered
In the Superserve API key guide, go to console.superserve.ai, open Settings → API keys, click Create key, and copy the key value once. Superserve says keys are prefixed with ss_live_ and are scoped to a single team. For SDKs and local MCP setups, set it as SUPERSERVE_API_KEY; for hosted MCP, send it as a bearer token.
conventions · 0/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing