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.
The DevStride MCP Server connects an AI assistant — Claude, ChatGPT, Cursor, Copilot, Codex, Gemini CLI — directly to your DevStride workspace. Once connected you talk to your work in plain language: "What am I working on this week?", "Which of my items are blocked?", "Draft a status update for leadership" — and the assistant answers from your live data, and makes changes when you ask it to.
MCP (Model Context Protocol) is an open standard for giving AI assistants tools. Think of it as a USB port for AI: your assistant has the socket, DevStride provides the plug, and once connected the assistant can call DevStride's tools — search_items, create_item, start_time_entry, and about two hundred more — the way it already calls a calculator or a web search. DevStride hosts the server at https://api.devstride.com/mcp; there is nothing for you to install or run.
What your assistant can do with it#
- Find and summarize work by name — boards, teams, people, items, and workstreams — without looking up IDs.
- Create and update items, including bulk edits across hundreds of items in one pass, reparenting, moving between boards and cycles, and ranking.
- Plan: create cadences and cycles, build roadmaps (Gantt) with initiatives and milestones, and convert item types across a whole tree.
- Track time: start and stop timers, log entries, report on logged time.
- Measure delivery: velocity, throughput, cycle metrics, progress snapshots, time-tracking rollups.
- Check quality: items missing estimates, owners, dates, or descriptions, on your own work or a whole board.
- Work the Knowledge Base: find, write, publish, and review articles and their comment threads.
- Administer, if your role allows: members, teams, roles, custom fields, statuses, integrations, and billing.
Anything without a purpose-built tool is still reachable through the full DevStride API, so uncommon configuration tasks are within reach too. The complete list is in the Tool Reference.
It acts as you
Every tool call runs with your permissions in one organization you choose when you connect. The assistant can do nothing you could not do yourself — and nothing you could not do, it can. See Best Practices & Tips for staying in control.
Supported clients#
| Client | Connection method |
|---|---|
| Claude (web) and ChatGPT | OAuth 2.1 only |
| Claude Code, Codex, Cursor, Copilot (VS Code), Gemini CLI | OAuth 2.1 (recommended) or API key |
| Microsoft Copilot Studio | OAuth 2.1 with a client secret — see Setting Up Your Connection |
You connect once per client. The toolset grows with each release; the assistant can ask devstride_help for the current catalogue at any time.
Where to go next#
- Setting Up Your Connection — connect your client in a few minutes.
- Doing Real Work with the DevStride MCP Server — what to ask, with a worked example.
- Tool Reference — every tool and what it does.
- Best Practices & Tips — get reliable results and stay safe.