Connect DevTune MCP With OAuth
DevTune's MCP server now supports OAuth for interactive MCP clients. You can connect tools like Codex without creating or pasting an API key.
What Changed
When your MCP client supports OAuth, setup now opens a browser sign-in flow. After signing in, choose the DevTune project the client should access, and DevTune links that project to the MCP connection.
This makes MCP setup simpler for agent workflows where a human is present to approve access.
What Agents Can Access
OAuth MCP connections use your DevTune account permissions for the selected project:
- Project members can use read tools for visibility, citations, traffic, actions, and briefs
- Users with DevTune management permission can also use write tools such as action brief generation
API Keys Still Work
API keys remain the right option for non-interactive clients, CI jobs, and automations that cannot complete a browser-based OAuth flow.
Getting Started
Use the DevTune MCP server URL in an OAuth-capable MCP client:
https://devtune.ai/api/mcp
Read the MCP server setup guide for OAuth and API key client examples.