Silverile.AI for VS Code

MCP

Connect VS Code to Silverile via the Model Context Protocol (MCP). Once configured, Copilot in Agent Mode can read and update your stories, sprints, defects, and test cases directly from the chat panel — no copy-pasting, no context switching.

Prerequisites

  • VS Code 1.105.0 or later
  • A Silverile account with at least one project
  • GitHub Copilot (required for Agent Mode and MCP tool use)

Step 1 — Install the extension

Open the Silverile extension on the VS Code Marketplace →

1Open the Extensions view (Ctrl+Shift+X / Cmd+Shift+X)
2Search for Silverile.AI and click Install
3Reload VS Code when prompted

Step 2 — Get your API credentials

1Log in to silverile.com
2Go to Settings → User Settings → API Keys
3Click Generate Key
4Copy the Key ID and Key Secret — the secret is shown only once
Keep the Key Secret private. It cannot be recovered after you leave the key generation page.

Step 3 — Configure MCP

1Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P)
2Run Silverile: Configure MCP
3Enter your Key ID and Key Secret, then click Load Projects
4Select your project from the dropdown and click Save & Start
Credentials are stored in VS Code SecretStorage — never in plaintext settings files or .vscode/mcp.json.

Step 4 — Open Copilot Chat in Agent Mode

1Open Copilot Chat from the Activity Bar
2Switch to Agent Mode using the mode selector at the top of the chat panel
3Confirm the Silverile tools are visible in the tools list (click the tools icon in the chat input bar)
4Try: validate Silverile connection or show my current stories

Automatic tool refresh

The extension fires an MCP reconnect 2 seconds after VS Code starts. When new tools are released on the Silverile MCP server, they appear automatically the next time you open VS Code — no manual action needed. To pick up new tools in the current session, run Silverile: Reconnect Silverile MCP.

Validate a story against the codebase

Ask Copilot to check whether a story's acceptance criteria are implemented in your codebase. Copilot fetches the story, optionally includes test cases, then reads your source files and reports each criterion as Met, Partially met, Not met, or Unclear with file and line evidence.

validate story #837 against the codebase

Before running, Copilot will:

1Confirm it has access to your codebase (filesystem MCP or workspace files)
2Ask whether to include test cases: a) all, b) pick specific ones, c) skip
3Fetch the story and build a validation prompt from the acceptance criteria
4Scan the codebase and produce a per-criterion report with an overall verdict
For full codebase access, run Copilot in Claude Desktop with the filesystem MCP, or use the Silverile extension in an IDE that mounts your workspace automatically.

Create a story

Describe what you want to build and Copilot creates a structured Silverile story — title, description, acceptance criteria, tasks, and optionally test cases.

create a story for user login with Google OAuth

Copilot will:

1Ask: "Should I also generate test cases for this story?"
2Show a full preview of the story (and test cases if requested)
3Wait for your approval before saving anything to Silverile

Example Agent Mode prompts

Use these in Copilot Chat with Agent Mode enabled. No @ mention needed — Silverile tools are available to the agent automatically.

show my current stories
get story 1569
create a story for user login with Google OAuth
validate story #837 against the codebase
generate test cases for story #88
what stories are in the current sprint?
assign story 2149 dev to me
assign defect 501 qa
fix defect #15
update story 220 status to in progress

Command reference

All commands are available via the Command Palette (Ctrl+Shift+P / Cmd+Shift+P).

CommandWhat it does
Silverile: Configure MCPOpens the setup page to enter credentials and register the Silverile MCP server
Silverile: Reconnect Silverile MCPForces an immediate MCP server restart within the current session
Silverile: Reset MCP CredentialsOpens the setup page to change your Key ID, Key Secret, or project
Silverile: Test MCP ConnectionProbes the Silverile MCP server and shows a pass/fail notification
Silverile: Open SilverileOpens the Silverile web app in your browser
Silverile: Sign OutClears stored credentials and removes the Silverile MCP entry from this workspace
Silverile: Reset ConfigurationRemoves the Silverile MCP entry from this workspace without clearing credentials

A status bar item at the bottom right shows whether Silverile MCP is configured. Click it to open the setup page or sign out.

Settings reference

SettingTypeDescription
Silverile.baseUrlstringSilverile web app URL opened by the Open Silverile command. Default: https://www.silverile.com
API credentials (Key ID, Key Secret, Project ID) are stored in VS Code SecretStorage and are not visible in the settings file or .vscode/mcp.json.

Troubleshooting

Silverile tools do not appear in Copilot Agent Mode

Run Silverile: Configure MCP and complete the setup. Then open MCP: List Servers from the Command Palette and start the Silverile server. Confirm the status bar shows "✓ Silverile".

"API key invalid" or connection error

Run Silverile: Reset MCP Credentials and re-enter your Key ID and Key Secret. Make sure you copied both fields before leaving the key generation page.

The status bar shows "Sign in to Silverile" after configuration

Re-run Silverile: Configure MCP. If the issue persists, run Silverile: Sign Out and sign in again.

New Silverile tools are not visible after a server update

The extension automatically refreshes the tool list on VS Code startup. Restart VS Code or run Silverile: Reconnect Silverile MCP to pick up new tools immediately.

Copilot Chat is not in Agent Mode

Open Copilot Chat from the Activity Bar, click the mode selector at the top of the chat panel, and switch to Agent Mode. MCP tools are only available in Agent Mode.

The extension is not activating

Confirm VS Code is version 1.105.0 or later and GitHub Copilot is installed. Open the Extensions view and verify Silverile.AI is enabled.