Connecting an AI assistant to DevStride just got easier and more secure. You can now authenticate your MCP client with OAuth 2.1 instead of an API key.
API keys are still supported if you prefer them β your secret is shown only once, when you create the key.
An MCP connection can invoke any tool you can perform in the UI β including destructive ones (archiving boards and items, deleting comments and time entries, bulk-updating items). Read-only scopes are not yet available. Access is limited to the organization you pick when you sign in.
Connecting an AI client is now a first-class action. A new Connect AI (MCP) item in the main menu (under Help) opens a setup page with everything you need to connect DevStride to Claude.ai, Claude Code, ChatGPT, Codex, Cursor, Copilot, and Gemini CLI.
Each client has step-by-step instructions and a ready-to-paste MCP server URL. For example, to connect Claude.ai:
https://api.devstride.com/mcpOrganization Admins can now reset multi-factor authentication for users in their organization. When a user loses access to their authenticator device, an Admin can clear their MFA so they can set it up again β no need to wait on support.
The MCP Server is now documented in detail in its own section β see DevStride MCP Server for what it is, how to connect your AI client, and what you can do with it.
Having trouble setting up the MCP connection? Email us at shend@devstride.com or use the Support option in the menu, and we'll get back to you.
Found something you can do in the UI that the MCP server doesn't support yet? Let us know β we'll add support for it.