Connecting takes a few minutes: pick an authentication method, add the server to your client, and confirm which organization you are connected to.
Configure Settings → AI Assistants → Connect AI opens Connect your AI client (MCP), with the server URL and a ready-to-paste snippet for each client. It is shown to people whose role grants Manage Ai Assistant. You do not need that page to connect: the server URL and every snippet it offers are on this page, so every member can follow the steps below. Every member also meets the same panel, pre-filled for the API-key method, in the dialog that My Account → API Keys → New Key shows once a key is created. Whatever you connect acts within the permissions you already have.
Every client connects to one endpoint, shown on the page as a copyable MCP Server URL:
https://api.devstride.com/mcp
The server identifies itself to clients as devstride-mcp.
The Connection method toggle at the top of the panel offers OAuth 2.1 (recommended, the default) and API Key.
| OAuth 2.1 | API Key | |
|---|---|---|
| Stores a long-lived secret on your machine | No — a short-lived token, refreshed automatically | Yes — you copy and keep the secret |
| Works with web clients (Claude.ai, ChatGPT) | Yes | No — they cannot send custom headers |
| Works with Claude Code, Codex, Cursor, Copilot, Gemini CLI | Yes | Yes |
| Organization | Chosen on the consent page when you sign in | Chosen when you create the key |
| To take it back | My Account → Connected Apps → Revoke | My Account → API Keys → delete the key |
Use OAuth 2.1 unless your client cannot open a browser to sign in.
On first use your client opens a browser to DevStride's consent page: "<App> wants to access your DevStride workspace." You pick an organization and click Allow. Your client receives a token that lasts about an hour and refreshes itself for up to 30 days of inactivity, so you rarely sign in again.
Your grants are listed under My Account → Connected Apps, where you can revoke them.
Most clients register with DevStride's sign-in server without a secret. Some platforms — Microsoft Copilot Studio is one — insist on a client secret at registration. Such an app can request one: it is shown once, and the app must present it whenever it exchanges, refreshes, or revokes a sign-in. The one-time code check (PKCE) every client passes stays mandatory; the secret is in addition to it. Apps that do not ask for a secret behave exactly as before, and each person still signs in as themselves and picks their organization.
For clients that can send headers. Create a key from the panel's Create a new API key link or from My Account → API Keys → New Key, giving it a Label and choosing For Organization — the organization travels with the key.
The success dialog shows the Api Key, Organization Id, Organization Slug, and Api Secret, and embeds the Connect AI panel pre-filled with them so you get a ready-to-paste command.
Under the hood an API-key client sends four headers with every request: X-DevStride-Api-Key, X-DevStride-Api-Secret, X-DevStride-Organization-Id, and X-DevStride-Organization-Slug. The snippets fill them in for you.
The panel has a tab per client under Install in your AI client, each with a snippet matching how that client is configured, plus Set it up — step by step instructions:
| Client | What you paste |
|---|---|
| Claude Code | A terminal command: claude mcp add --transport http devstride https://api.devstride.com/mcp (API-key snippets add --header lines) |
| Codex | codex mcp add devstride --transport http --url https://api.devstride.com/mcp |
| Copilot | A .vscode/mcp.json block; enable the server in VS Code |
| Cursor | A ~/.cursor/mcp.json (or project .cursor/mcp.json) entry; enable DevStride under Cursor → Settings → MCP |
| Gemini CLI | An entry for the mcpServers object in ~/.gemini/settings.json; restart Gemini CLI |
| Claude (web), ChatGPT | A connector Name (DevStride) and the MCP Server URL |
With OAuth, the client opens your browser to sign in the first time you use it.
These three take a configuration block rather than a command. With OAuth, each block is only the server URL; with an API key, add a headers object holding the four headers listed under Method 2, which is what the panel's API-key snippets do.
Copilot, in .vscode/mcp.json (then enable the server in VS Code):
{
"servers": {
"devstride": {
"type": "http",
"url": "https://api.devstride.com/mcp"
}
}
}
Cursor, in ~/.cursor/mcp.json or a project's .cursor/mcp.json (then enable DevStride under Cursor → Settings → MCP):
{
"mcpServers": {
"devstride": {
"url": "https://api.devstride.com/mcp"
}
}
}
Gemini CLI, in the mcpServers object of ~/.gemini/settings.json (then restart Gemini CLI):
{
"mcpServers": {
"devstride": {
"httpUrl": "https://api.devstride.com/mcp"
}
}
}
DevStride. URL: https://api.devstride.com/mcp.The Claude.ai free plan allows one custom connector.
Remove the server from the client, then run the setup again and pick the other organization. In Claude Code:
claude mcp remove devstride
If you belong to several DevStride organizations and keep a separate code project for each, give each project folder its own connection, bound to that project's organization. Each folder then reads and writes only its own organization, with nothing to switch, and you can run assistant sessions in two projects side by side.
claude mcp add saves a connection to the current folder unless you pass --scope user, so each folder keeps its own. Copilot (.vscode/mcp.json) and Cursor (a project's .cursor/mcp.json) are configured per project in the same way.claude mcp logout plugin:devstride:devstride. Until it is signed in, it adds no tools. A connection added with --scope user applies to every folder; remove it with claude mcp remove devstride --scope user.An OAuth sign-in is one organization per connection, and a connection shared by every folder (the plugin's own, or one added with --scope user) answers for whichever organization was chosen last. That is why the per-folder setup uses API keys.
Before asking the assistant to change anything, ask: "Use DevStride whoami to tell me which organization this connection is bound to." The answer includes the organization ID and, when available, its slug (the short name in its DevStride web address). If it names the wrong organization, reconnect and choose the right one — the connection cannot be switched in place.
X-DevStride-Toolset: core to list only the everyday groups; administration, billing, integrations, data-model configuration, analytics, and pull-request tools stay callable by name and through invoke_api_operation, they are just not advertised.If you want Claude Code (the terminal assistant) and do not have it yet:
PATH commands it prints, then brew install node. Windows: install Node.js (LTS) from nodejs.org and open Windows Terminal or PowerShell.npm install -g @anthropic-ai/claude-code, then claude --version to confirm.claude. It walks you through signing in the first time./mcp to confirm DevStride shows as connected.What Is the DevStride MCP Server?
Connect Claude, ChatGPT, Cursor, Copilot, Codex, or Gemini CLI to your DevStride workspace so your assistant can answer questions about your work and change it on your behalf.
Doing Real Work with the DevStride MCP Server
What you can ask the DevStride MCP Server, grouped by the job you are doing, with a worked example from backlog to roadmap and prompts by role.