Best Practices & Tips

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

Start read-only, then build up

When you're getting to know the connection, lead with questions that only read your data — "what's assigned to me?", "summarize my priorities." They're fast, safe, and immediately useful, and they help you learn how the assistant interprets your requests before you ask it to make changes.

Ask it what it can do

The server includes a built-in help tool. Asking "What tools are available from the DevStride MCP, and what can you do with them?" returns a current list of capabilities and example prompts — handy because the toolset grows over time.

Two behaviours worth knowing when an assistant works with the tools directly:

• Asking for a field by name returns it. The tools answer with a compact summary by default, which leaves out large or rarely needed values. When the assistant names the fields it wants — on comments, activity entries and templates as well as on items — those fields come back even if the summary would normally omit them, so "the field is absent" always 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 DevStride API directly through the MCP and includes a misspelled or misplaced key anywhere in the call, the call is refused up front and the reply names every key that would have been ignored. Before, the call went ahead without those keys and reported success while doing something other than what was asked. The assistant should correct the keys and try again.

Review before it applies changes

A connection acts with your permissions, so the assistant can change real work. For anything that writes — updating estimates, setting dates, bulk edits, creating a roadmap — ask it to propose first and wait for your approval. A good pattern is to end planning prompts with "…wait for my approval before changing anything." You stay in control, and you get to sanity-check the plan before it lands.

Refer to things by name

You don't need IDs. The assistant resolves names to the right object — "move this to the Sprint 2 board," "assign it to Priya," "add it to the Platform team's work," "tag it Blocked." Spelling names the way they appear in DevStride helps everything match cleanly.

Keep the connection healthy

• Restart after connecting. After you add the MCP to a client, restart it so the connection loads. In Claude Code, run /exit, start claude again, then /mcp to confirm DevStride shows as connected.
• Switching organizations? Each connection is scoped to one organization. Reconnect (and pick the other org) to work elsewhere — see Setting Up Your Connection.
• Using an API key? Treat the key and secret like passwords — don't share or email them, and regenerate them if they're ever exposed. OAuth 2.1 avoids storing a secret at all, which is why it's the recommended method for clients that support it.
• Hit the rate limit? An organization's API keys and MCP connections share 1,000 requests a minute. Over it, the MCP tells the assistant how long to wait, and it carries on once the minute resets — see API keys.

Terminal tips for first-timers

If you're using a command-line client like Claude Code:

• Paste with Cmd + V (Mac) or Ctrl + V (Windows) — not right-click.
• When you type a password, nothing appears on screen. That's normal — type it and press Return.
• If a command seems to hang with no new prompt, it's still running. Wait rather than pressing Return again.
• If a command "isn't found" right after installing something, close the terminal window and reopen it.