DevStride MCP Server

Best Practices & Tips

Habits that make the DevStride MCP Server fast, accurate, and safe: start read-only, ask it to propose before it changes anything, refer to things by name, and keep the connection healthy.

A few habits make the DevStride MCP Server faster, more accurate, and easier to trust.

Start read-only, then build up

Lead with questions that only read — "what's assigned to me?", "summarize my priorities", "what's on the Platform board?". They are fast and safe, and they show you how the assistant interprets your requests before you let it change anything.

Ask it what it can do

Ask "What tools are available from the DevStride MCP, and what can you do with them?" — the built-in devstride_help tool returns a current catalogue of prompts grouped by job. The Tool Reference lists every tool.

Two behaviours worth knowing:

  • Asking for a field by name returns it. Tools answer with a compact summary that leaves out large or rarely needed values. When the assistant names the fields it wants — on items, comments, activity entries, templates — they come back, so "the field is absent" means the record has no value, not that it was trimmed.
  • A raw API call with a mistaken key is refused, not quietly trimmed. When the assistant calls the API directly through invoke_api_operation and includes a misspelled or misplaced key, the call is refused up front and the reply names every key that would have been ignored. The curated tools warn after the call instead when they drop an unknown top-level argument.

Review before it applies changes

The connection has your permissions, so the assistant can change real work. For anything that writes — estimates, dates, bulk edits, a new roadmap — end the prompt with "…propose first and wait for my approval before changing anything." You see the plan, then say go.

Prefer reversible tools. archive_item, archive_board, and archive_workstream can be undone; delete_item, delete_board, delete_workstream, and delete_time_entry cannot. If the assistant proposes a permanent delete, ask whether archiving would do.

Refer to things by name

You do not need IDs. The assistant resolves "move this to the Sprint 2 board", "assign it to Priya", "tag it Blocked". Spell names the way they appear in DevStride; when a name is ambiguous the assistant is told the candidates and will ask you which one.

Item numbers are the exception worth knowing: an I number is a work item and an F number is a workstream, each with its own tools. Sending a workstream number to an item tool is refused with a message naming the right tool.

Keep the connection healthy

  • Restart after connecting. After adding the MCP to a client, restart it so the server loads. In Claude Code, /exit, start claude again, then /mcp to confirm DevStride is connected.
  • Confirm the organization first. "Use DevStride whoami to tell me which organization this connection is bound to." Each connection is bound to one organization; reconnect and pick another to work elsewhere — see Setting Up Your Connection.
  • Using an API key? Treat the key and secret like passwords — never paste them into shared chats or commit them to a repository, and delete the key if it is ever exposed. OAuth 2.1 stores no secret at all, which is why it is recommended wherever the client supports it.
  • Clean up. Revoke clients you no longer use under My Account → Connected Apps (OAuth) or delete the key under My Account → API Keys.
  • Hit the rate limit? An organization's API keys and MCP connections share 1,000 requests a minute, and the /mcp route itself is throttled at the edge to bound a runaway client. Over the limit, the MCP tells the assistant how long to wait and carries on once the window resets — see API keys.
  • Big batches are queued. bulk_update_items applies up to 400 work units per call; larger ones are refused before anything changes, and batches too slow to finish inside one request are queued as a job the assistant polls with get_job. A queued batch is not done until the job reports it is.

Working with sub-tasks, personas, and renamed tools

  • What the UI calls a sub-task is a sub-item in the tools; the assistant treats the words as interchangeable.
  • Personas (for example Engineer) are available alongside person assignments; a persona never grants item access.
  • The tools use the app's vocabulary — create_workstream not create_folder, create_status not create_lane. The old folder- and lane-named tools were removed on October 10, 2026, and rank_item no longer accepts the scope lane (use status). Update any saved prompts and scripts that still name them — see API keys.