Use Doow from any AI agent or MCP client.
Connect the AI tools you already work with, like Claude, Codex, and Cursor, directly to your Doow workspace.
Claude
Codex
Cursorhttps://mcp.doow.coOne connection that works wherever you do.
Connect your MCP client, complete the browser-based OAuth flow to authenticate with Doow, and we’ll enforce your organization and role permissions before granting access to approved tools.
- 1Choose your clientClaude, Cursor, Codex, or any MCP-compatible client
- 2Authenticate with DoowConnect and authenticate once with a secure server URL
- 3Access your workspaceQuery and manage data within your existing permissions
Your questions, answered
Didn't find what you were looking for? Drop us a message at hello@doow.co, and we'll get back to you soon.
Connect Claude Code, Claude Desktop, Codex, Cursor, or another MCP client that supports Streamable HTTP and OAuth 2.0 with PKCE. Protected operations also require interactive MCP elicitation so your client can display and return a confirmation.
You need a Doow account with organization membership and an MCP client that supports Streamable HTTP and OAuth 2.0 with PKCE. Add https://mcp.doow.co as the server URL, then complete the browser-based sign-in and authorization flow.
No. MCP does not expand your Doow permissions. Access is limited by the requested mcp:read or mcp:write scope and the permissions assigned to your Doow role. Each OAuth session is bound to one member and organization.
Yes. Request mcp:read for read-only access. Use mcp:write when you need write tools; it also includes read access. Protected operations require confirmation from an interactive MCP client.
