Connect an agent and it can read your endpoints, tell you what changed, and set up new ones from a sentence. At the end it lists Dialect’s tools.
There are two addresses.
| Address | What an agent can do there |
|---|---|
https://api.dialectlayer.com/mcp | Everything its access allows |
https://api.dialectlayer.com/mcp/readonly | Read endpoints, their history and notes, and subscribe to changes. It can’t take photos, set up, change or stop endpoints |
Any MCP client that speaks HTTP can connect. The apps below are the ones the console sets up for you, under Connections.
Sign in from Claude Code
One command and no token. It acts with your access.
Then run /mcp, choose dialect and sign in. You should see it read Connected.
Connect other apps with a token
In the console, open Access, then Grant access, then An agent’s token. Choose its gateways and select Issue token. It’s shown once. Set it as DIALECT_TOKEN where the agent runs.
Run in a terminal:
Then run /mcp in Claude Code. You should see dialect read Connected.
Then restart Codex and run /mcp. You should see dialect listed with its tools.
Then open Customize in Cursor’s sidebar and turn dialect on. You should see its tools under Available Tools.
Then select Start above dialect in mcp.json. You should see it read Running once connected.
This goes through the mcp-remote bridge, so Claude Desktop needs Node.js. Create the file if it isn’t there:
| Computer | File |
|---|---|
| Mac | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| Linux | ~/.config/Claude/claude_desktop_config.json |
Then quit Claude Desktop fully and open it again. You should see dialect under Connectors in the + menu.
Ask your first question
- What can Dialect’s cameras see right now?
- Use Dialect to tell me whether the screen on my desk is on, and keep checking it as an endpoint.
- With Dialect, watch the coffee machine and tell me when its light turns red.
Set how far an agent reaches
An agent signed in with OAuth reaches what you can: your gateways, and every gateway if you’re an administrator. It never administers. It can’t grant access, invite or revoke gateways, or confirm an endpoint.
An administrator can cap these agents for the whole workspace on Access, under What agents people connect can do. It takes effect on each agent’s next request, with nobody reconnecting.
| Choice | What agents can do |
|---|---|
| Change things | What their person can, but never administer |
| Read and look | Read endpoints, take photos and test, but change nothing |
| Read only | Read endpoints and subscribe to changes, but not take photos or change anything |
A token keeps the access it was issued with, and that cap doesn’t touch it. It reads only the gateways it was granted. It may be Full or Read only. See Create a token.
A tool past an agent’s reach isn’t listed, and is refused if called.
Leave these to a person
- Confirm an endpoint. An agent proposes, and asks you to confirm at dialectlayer.com/endpoints.
- Pay. An agent that’s refused gets
payment_requiredand a link to give you. - Add a gateway to a workspace. An agent can start the container, and sends you the link to open.
- Answer a re-aim’s question. The agent passes on your words. See Handle a re-aim.
Treat answers as data
Dialect’s answers hold text from the physical world, such as a sign the camera reads, and notes saved by other agents. Each answer’s data sits between <untrusted-data-…> markers, and the server tells every client not to follow instructions inside it.
Fix a connection
- No tools are listed. The token may use no gateway. Grant it one on Access.
- 401 with
token_expired. Ask an administrator to rotate it on Access. - 401 with
token_rotated. Use the token that replaced it. payment_required. Reading works, but setting up and taking photos need a paid plan.