Model Context Protocol

Authentication

Pass a Bearer token on every request. Workspace API keys prefixed with sh_live_ work the same as REST v1 (create keys on Launch+; Free workspaces cannot issue keys). Other bearer tokens use the OAuth 2.1 flow advertised from /.well-known/oauth-protected-resource; hosted login completes the authorize step. OAuth issuance needs MCPAUTH_SECRET and an RSA private key in the server environment.

Remote MCP hosts (Claude, ChatGPT, Codex, Grok, and similar) discover OAuth from /.well-known/oauth-protected-resource/api/mcp, then use Client ID Metadata Documents (preferred) or dynamic client registration as a fallback. Hosted sign-in on SlateHut completes authorization — no manual redirect-uri setup or API key paste in those apps.

Endpoint

Replace the origin with your deployment host. Example for this environment:

https://slatehut.com/api/mcp

Install

{
  "mcpServers": {
    "slatehut": {
      "url": "https://slatehut.com/api/mcp"
    }
  }
}

{
  "mcpServers": {
    "slatehut": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://slatehut.com/api/mcp"
      ]
    }
  }
}

MCP Registry

The MCP Registry is the official metadata catalog for publicly discoverable MCP servers (currently in preview; breaking changes are possible). It lists how to reach a server (npm, PyPI, Docker Hub, or a public remote URL) and trust signals via namespace authentication. Package registries host code; the MCP Registry hosts server.json records. Private-only endpoints are out of scope, see the registry overview for ecosystem notes (aggregators, OpenAPI, moderation).

SlateHut is published as remote Streamable HTTP metadata under io.github.sandeep1995/slatehut. Search the registry API: registry.modelcontextprotocol.io/v0.1/servers. Report registry bugs on GitHub.

Recipe: build a site end-to-end

1. Discover: read schema://blocks for the block catalog and schema://theme for theme enums.
2. Create: create_site_from_template when you know the starter shape, or create_site_from_document with a full pages[] you built from schemas. Pass a subdomain hint to keep URLs memorable.
3. Refine theme: update_site_theme with hex colors and enum values from the theme schema.
4. Swap blocks: prefer update_page with blocks:[...] for atomic bulk replacement over looping add_block/delete_block.
5. Add media: unsplash_search → unsplash_import returns a permanent blob URL plus the photographer attribution you must display.
6. Iterate: use update_page, update_block, and update_site_theme (no extra AI credits).
7. Ship: get_site now returns a public url, share it.

Recipe: Free plan / no AI credits

Free workspaces include one AI prompt and a small monthly credit pool. When AI tools return quota errors, the dashboard and editor remain available for manual editing. Use this deterministic MCP flow instead:

1. Pick a template: list_templates or read example://sites/{templateId} (e.g. fineDining).
2. Create: create_site_from_template with templateId and optional title, or create_site_from_document when you already have valid pages[].
3. Inspect: get_site to read current pages, blocks, and theme.
4. Customize: update_site, update_page, update_block, and update_site_theme — no AI credits required.

Tools

Resources

Resources are read-only; fetch them with your MCP client’s resource API (e.g. FetchMcpResource in Cursor). Use them before authoring to avoid guess-and-retry on block shapes.

Prompts

MCP prompts are pre-built instructions you can invoke with your client's prompt API (e.g. GetMcpPrompt in Cursor). They accept a subdomain argument and expand into a detailed site-creation or editing brief, saving you from writing the same instructions each time. Requires the mcp:prompts OAuth scope.

Block catalog (48 types)

Every block has the shape { id, type, anchorId?, fullWidth?, colorOverrides?, animation?, props }. Fetch schema://blocks/{type} for the exact props schema before adding or updating.

Error handling for agents

• Block validation errors now return a field-path list like props.variant: Invalid enum value. Expected 'editorialStart' | 'split' | … plus a hint to fetch the matching schema://blocks/{type}.
• Quota errors (create_site site limit) are returned with a human-readable message. MCP tools do not call SlateHut AI; use create_site_from_template or create_site_from_document. Free plans typically allow 1 site; call delete_site to free the slot before retrying.
• Concurrency: update_site accepts expectUpdatedAt for optimistic locking; pass force: true to override.
• 401 on OAuth: verify MCPAUTH_SECRET and an RSA private key are set in your server environment. The OAuth server metadata is available at /.well-known/oauth-authorization-server.
• Prompts returning empty: confirm your OAuth token includes the mcp:prompts scope. Workspace API keys (Launch+) use the same workspace permissions as REST v1.

Cost & quotas

MCP tools are deterministic and do not consume SlateHut AI credits (template/document create, block/page/theme CRUD, media import). Hosted AI generation is REST-only (POST /api/v1/sites/generate). Create-site quota still applies to new sites. Free workspaces keep dashboard and editor access after AI limits. See AI credits and Free plan / no AI credits for plan details and fallbacks.

See also

• REST API v1 reference (same schemas)
• API keys
• Editor & blocks