DevStride MCP Server

Setting Up Your Connection

Connect your AI client to the DevStride MCP Server with OAuth 2.1 or an API key, using the ready-to-paste snippet for Claude, ChatGPT, Cursor, Copilot, Codex, or Gemini CLI.

Connecting takes a few minutes: pick an authentication method, add the server to your client, and confirm which organization you are connected to.

The Connect AI page

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.

The MCP Server URL

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.

Choose an authentication method

The Connection method toggle at the top of the panel offers OAuth 2.1 (recommended, the default) and API Key.

OAuth 2.1API Key
Stores a long-lived secret on your machineNo — a short-lived token, refreshed automaticallyYes — you copy and keep the secret
Works with web clients (Claude.ai, ChatGPT)YesNo — they cannot send custom headers
Works with Claude Code, Codex, Cursor, Copilot, Gemini CLIYesYes
OrganizationChosen on the consent page when you sign inChosen when you create the key
To take it backMy Account → Connected Apps → RevokeMy 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.

  • One organization per connection. If you belong to several, nothing is pre-selected — choose, then Allow. The choice cannot be changed later; to work in another organization, connect again and pick it. If you belong to one, its name is shown and you can allow straight away.
  • You must be an active member of the organization you authorize. If the page cannot confirm your memberships it asks you to pick explicitly; if you belong to none it tells you to reload after you have been added.
  • The page checks who is signed in. If you sign out or switch accounts in another tab while it is open, it asks you to reload rather than offering the previous account's organizations. Deny always works.
  • Unverified apps are labelled. The consent page shows the app's registered name with Verified by DevStride for known clients, and a warning plus the redirect destination for apps DevStride has not verified. Continue only if you recognize both.

Your grants are listed under My Account → Connected Apps, where you can revoke them.

Apps that must use a client secret

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.

Method 2: API Key

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.

Set up your AI client

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:

ClientWhat you paste
Claude CodeA terminal command: claude mcp add --transport http devstride https://api.devstride.com/mcp (API-key snippets add --header lines)
Codexcodex mcp add devstride --transport http --url https://api.devstride.com/mcp
CopilotA .vscode/mcp.json block; enable the server in VS Code
CursorA ~/.cursor/mcp.json (or project .cursor/mcp.json) entry; enable DevStride under Cursor → Settings → MCP
Gemini CLIAn entry for the mcpServers object in ~/.gemini/settings.json; restart Gemini CLI
Claude (web), ChatGPTA connector Name (DevStride) and the MCP Server URL

With OAuth, the client opens your browser to sign in the first time you use it.

Copilot, Cursor and Gemini CLI

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"
    }
  }
}

Claude (web)

  1. In Claude, open Settings → Connectors → Add custom connector.
  2. Name: DevStride. URL: https://api.devstride.com/mcp.
  3. Click Add, then Connect, and sign in to DevStride when prompted.

The Claude.ai free plan allows one custom connector.

ChatGPT

  1. Open Settings → Connectors → Create.
  2. Paste the same Name and MCP Server URL, plus the Description the panel provides (it helps ChatGPT know when to use DevStride), and set authentication to OAuth.
  3. For full access to DevStride's tools, turn on Developer mode under Connectors → Advanced.

Reconnecting or switching organizations

Remove the server from the client, then run the setup again and pick the other organization. In Claude Code:

claude mcp remove devstride

Working in more than one organization

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.

  1. Create one API key per organization. Go to My Account → API Keys → New Key and choose the organization under For Organization; the organization travels with the key. The success dialog shows a ready-to-paste command (see Method 2: API Key).
  2. Add the connection from inside each project folder. In Claude Code, run that command from the project's folder: 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.
  3. Keep only the per-project connections signed in. If you also use the DevStride Claude Code plugin, sign its own connection out so it does not compete with the folder's: 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.
  4. Check each folder with the whoami prompt below: it should name that folder's organization.

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.

Confirm the connected organization

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.

New to the command line? Set up Claude Code first

If you want Claude Code (the terminal assistant) and do not have it yet:

  1. Mac: install Homebrew from brew.sh and run the two PATH commands it prints, then brew install node. Windows: install Node.js (LTS) from nodejs.org and open Windows Terminal or PowerShell.
  2. Install Claude Code: npm install -g @anthropic-ai/claude-code, then claude --version to confirm.
  3. Start it from a folder you want to work in: claude. It walks you through signing in the first time.
  4. Paste the Claude Code snippet from the Connect AI panel, restart Claude Code, and run /mcp to confirm DevStride shows as connected.