Monty is your AI assistant for Silverile — accessible through Claude Desktop, Claude Code, Codex, Google Antigravity, GitHub Copilot, VS Code, and any other OAuth-capable MCP client. You talk to Monty in plain English; Monty handles the Silverile API calls behind the scenes.
Monty can browse your backlog, check your assigned work, create and update stories and defects, show sprint health, and generate test cases — all without leaving your AI assistant.
Monty always shows a preview before making any changes. For create and update operations you will see a summary of what will be saved and a prompt to confirm. Reply yes or confirm to proceed, or no or cancel to abort.
For defect creation, Monty collects each required field from you before drafting the defect — it will never fabricate your steps to reproduce, actual behavior, expected behavior, or severity.
For updates, Monty only changes the fields you mention. Every other field stays exactly as it is in the database.
After connecting Monty to your AI client (see Claude Desktop integration or Codex Desktop integration), set your default project so Monty knows which workspace to use:
Monty remembers your default project across sessions. Then verify the connection is working:
Monty doesn't know which project to use
Say "Set project 12 as my default" using your numeric Product ID (found in the Silverile URL, e.g. silverile.com/product/12/...). Monty will remember it for future sessions.
"Unauthorized" or authentication errors
Monty connects over OAuth — there is no API key or secret to set. Use your MCP client's Silverile disconnect or sign-out action, then authenticate again and sign in on Keycloak with your Silverile account.
Monty says a story or defect was not found
Use the public-facing ID shown in the Silverile UI (e.g. Story #42, Defect #1762) — not the URL hash or any internal database ID.
Monty stops mid-creation and asks for a field
This is intentional — Monty will never invent content on your behalf. Provide the missing field and it will continue.