Skip to content
Dexto Dexto Docs

Getting started

Connect via MCP

Connect Dexto to Claude, ChatGPT / Codex, Cursor, OpenClaw, or Hermes with one secure remote MCP endpoint.

Copy the Dexto connector URL

Paste this URL into your client in the next step.

https://app.dexto.ai/mcp

Connect, sign in and start

Connect, sign in, then enable Dexto from Search and tools.

Claude MCP docs

Start with what you want to do

Section titled “Start with what you want to do”

After OAuth sign-in, Dexto introduces itself to your MCP client as four connected layers:

LayerWhat it gives you
ConnectConnections bring services such as GitHub and reusable account context into Dexto
WorkCapabilities perform direct actions; Agents and AutoBots take on delegated work
ReuseSkills preserve useful procedures; Apps provide focused interactive experiences
AutomateAutomations run recurring work autonomously

For an unfamiliar task, ask your client to search Dexto first. Dexto returns a small ranked set of routes that are available to your account, why each route matched, whether setup is needed, and the next product action. It does not paste the full catalog or tool schemas into the conversation.

Try prompts such as:

  • “Search Dexto for the best way to connect my GitHub work.”
  • “Find a reusable release or pull-request review playbook.”
  • “Find an Agent or AutoBot that can own a competitor research brief.”
  • “Find or create a weekly project status automation.”
  • “Open Blender on a GUI computer and show me the default scene.”

Search results can include Capabilities, Skills, Agents, AutoBots, Apps, Connections, Automations, Services, and Marketplace resources. A result is a route, not a grant: Dexto checks current access, approval, billing, and availability again when the client takes the next action.

Progressive discovery and context safety

Section titled “Progressive discovery and context safety”

Dexto search deliberately returns a small page. The server enforces the result limit, bounds every display field and the complete serialized response, and supplies a cursor when more matches exist. The client can move wider through outcome-family facets and the cursor, or move deeper by inspecting one promising route for its current affordances and a few related alternatives. Setup requirements are resolved before the client takes the owning product action.

The route’s source type is descriptive rather than a closed allowlist. New Dexto resource types can remain discoverable, while stable outcomes such as connect, work, reuse, delegate, automate, and experience help the client understand how a result can be used. Exact inputs become strict only when the client selects an action.

Some tool families are available only with the corresponding OAuth scope or platform policy. For example, managed GPU tools appear only when that capability is available to the connected organization. The server rechecks authorization when a tool is called; a tool listing is not a permanent grant.

dexto_computer_* refers to bounded shell and file operations in the connected workspace. Managed GUI computers are a separate visual service exposed through the normal capability tools. Search for GUI computers, then describe or call dexto.gui.gui_computer or dexto.gui.gui_computer_control. They are available to ordinary organizations when the hosted GUI provider and an owned Desktop context are available; they are not sandbox or GPU operations.