Remote MCP OAuth 2.1 Explicit approvals

Latent for AI agents

From “what could work?” to an approved rollout.

Give your agent one safe remote control plane: explore a solution, shape the space interactively, manage installation state, inspect evidence, and prepare the exact recipient or package handoff.

Connect in 3 steps See what it can do

Your agent never receives your Latent password. Every consequential action stays visible.

YOUR AGENT AI

LATENT MCP

◇SPACE ◉DEVICES ↗APP

Read the guide now. Sign in when you connect.

The setup page is public; authentication is only needed to give an agent access to your workspace.

One connection · the complete setup

Rich when you explore. Direct when you act.

The agent can surface all the possibilities, then narrow the work to the next safe decision.

Plans and hardware stay interactive. Your agent can open the plan editor, show the hardware setup, and guide the work step by step. Important changes are always shown before they happen. Wi-Fi passwords, payment details, and device keys are entered only in Latent and are never passed to the agent.

Discover

Search solutions, compare sensing approaches, inspect evidence, plans and compatible hardware.

Read

Design

Open the interactive plan App, preview semantic area/object/node changes, then create one exact revision.

Draft

Install

Open interactive hardware setup, prepare physical nodes, and match each one to its planned position.

Approve

Validate

Inspect stored heartbeats and install state, plus an optional configured public HTTPS runtime—not a phone or ESP directly.

Read

Publish

Preview the recipient experience, publish a verified app, share it, or revoke access.

Confirm

Commerce

Build a quote, compare capacity, request hardware or begin checkout with the final choice kept visible.

Confirm

Permission, in plain language

One clear consent. Exact boundaries.

The consent screen groups every requested permission in plain language before anything is connected. Consequential tools then open a short-lived Latent review showing the exact action, target and current room state. If anything changes, that approval no longer works.

latent.catalog.readlatent.design.writelatent.deploy.writelatent.publish.writelatent.commerce.intent

01
Observe
Search, compare, inspect status and explain. No workspace state changes.
Runs safely
02
Prepare
Create a draft, plan a layout or assemble a quote you can inspect first.
You approve writes
03
Commit
Pair, publish, revoke or enter checkout only after you approve the exact request in your browser.
Browser approval

No prompt silently purchases anything. Hardware requests and checkout stay behind a single-use Latent browser approval; payment details remain only with Stripe.

About two minutes

Connect. Authenticate. Ask one harmless question.

Streamable HTTP

1ENDPOINT

Use this one URL everywhere

It is the canonical remote MCP endpoint. There is no API key to create or secret to paste.

https://studio.darkioc.com/mcp

2CLIENT

Choose where your agent runs

Each path ends at the same Latent consent screen.

CodexApp, CLI and IDE extension

Terminal

codex mcp add latent --url https://studio.darkioc.com/mcp
codex mcp login latent --scopes latent.catalog.read,offline_access

1
Run both commands. The second opens Latent in your browser and requests durable sign-in for Codex.
2
Sign in and approve the permissions shown on the Latent consent screen.
3
Return to Codex. The same MCP configuration is available to the app, CLI and IDE extension.

Never put your Latent password, OAuth token or payment details in an MCP configuration file.

3TEST

Start read-only

This prompt proves discovery works while explicitly ruling out every write or purchase.

Show me the Latent solutions for a small office and explain which permissions you would need for the next step. Do not change, buy, install, or publish anything.

Expected: a short list of suitable solutions plus a plain-language permission preview. No draft, device, app, order or subscription is created.

One endpoint, your boundaries