Search capabilities or support number/
More
← Blueprint Studio

Serverless MCP · same app origin

Let any capable agent learn the language.

Codex, Claude, Cursor, and generic MCP clients use the same versioned resources, bounded semantic tools, private revisions, deterministic previews, and exact browser approvals.

Design service endpointNot tested

01

Add the MCP endpointThe client reads protected-resource and authorization-server discovery automatically.

02

Latent opens in your browserThe client starts /oauth/authorize; Latent sends you to /login when needed.

03

Approve exact scopesReturn through Authorization Code + S256 PKCE. Passwords and access tokens are never pasted into configuration.

Standard OAuth, no session handoffThe MCP client owns its OAuth transaction. This Studio page never captures a transaction ID and never forwards an app account bearer token.

Open complete setup

Client-neutral first

One endpoint, four client families

Use each client’s remote MCP server flow and enter only the endpoint above. OAuth discovery supplies authorization and token endpoints; never paste a password or access token.

C
CodexRemote Streamable HTTP · OAuth PKCE · resources, prompts, tools, images
C
ClaudeRemote Streamable HTTP · OAuth PKCE · resources, prompts, tools, images
C
CursorRemote Streamable HTTP · OAuth PKCE · resources, prompts, tools, images
G
Generic MCPRemote Streamable HTTP · OAuth PKCE · resources, prompts, tools, images

Portable shape

Generic configuration

{
  "mcpServers": {
    "latent": {
      "type": "http",
      "url": "/mcp"
    }
  }
}

Exact UI labels and local config-file syntax belong to the client version you install. The server contract stays standard.

A safe first request

Tell the agent to learn, render, and wait.

The MCP server also exposes guided prompts. This client-neutral wording works when a client does not show server prompts.

Use the Latent MCP server. Read latent://blueprint-language/v1/quickstart and the capability kit before editing. Search for the capability I describe, create a private draft, validate it, render the preview, show me the picture and limitations, and wait for my exact browser approval before publishing or preparing an export. Never invent surveyed measurements or promote catalog readiness.

Exact-revision flow

Nothing important happens invisibly.

  1. 01
    Discover

    Read language, objects, copy contract, repair guide, and the exact capability kit.

  2. 02
    Draft

    Create or semantically patch an owner-scoped revision with expected-head protection.

  3. 03
    Validate + render

    Show the deterministic PNG, warnings, unknown measurements, readiness, and limitations.

  4. 04
    Review

    Open a private browser review bound to owner, client, scope, operation, revision, and hash.

  5. 05
    Publish or export

    Consume approval once. Any edit, stale head, scope mismatch, or reuse fails closed.

Your agent sees only what it needs.

Plans and deployment details can be shared with the agent. Wi-Fi passwords, payment details, device keys, and private readings stay in Latent.

Setup & connections