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 — Connect and authenticate

1Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P)
2Run MCP: List Servers and select Silverile
3If the menu shows Stop Server but authentication has not opened, stop Silverile, select it again, and choose Start Server
4When VS Code says Silverile wants to authenticate to mcp.silverile.com, choose Allow
5When VS Code asks to open an external website, choose Open
6On the Silverile sign-in page, sign in with your existing Silverile account to authorize the connection
7On the final browser prompt, choose Open Visual Studio Code to return the authorization result to VS Code
Silverile MCP server actions showing Stop Server, Restart Server, and Show OutputVS Code asking permission for Silverile to authenticateVS Code external website confirmation with the authorization URL redactedBrowser asking to return the successful sign-in to Visual Studio Code
The extension never receives or stores your Silverile credentials or OAuth tokens. VS Code owns the OAuth flow and stores the resulting access and refresh tokens in its secure authentication storage.

Step 3 — Verify the connection

1Run MCP: List Servers and select Silverile
2Choose Show Output
3Confirm the log ends with Discovered ... tools; the number can change as Silverile adds capabilities
Successful Silverile MCP output showing discovered tools

Step 4 — Open Chat in Agent Mode

1Open 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

Manage the connection

Use MCP: List Servers for all connection actions. Select Silverile to stop or restart the server and open Show Output. If Silverile is running but the authentication prompts never appeared, stop it and start it again.

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
Open the repository you want to evaluate as your VS Code workspace and allow Copilot Agent Mode to read the relevant workspace files before starting validation.

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
No Silverile API credentials or custom authorization headers are written to settings or.vscode/mcp.json.

Connection diagnostics

Open MCP: List Servers → Silverile → Show Output. During a normal first connection, VS Code discovers the protected-resource and authorization-server metadata, opens authentication, completes the MCP initialize request, and reportsDiscovered ... tools.

Discovered resource metadata at https://mcp.silverile.com/.well-known/oauth-protected-resource
Discovered authorization server metadata at https://mcp.silverile.com/.well-known/oauth-authorization-server
Discovered ... tools

When requesting support, include the VS Code version, Silverile extension version, approximate failure time, and the relevant lines from Show Output. Never include credentials, OAuth tokens, Redis connection strings, or a full authorization URL.

Troubleshooting

Output repeatedly says “Waiting for server to respond to initialize request”

VS Code is usually waiting for authentication. Run MCP: List Servers, select Silverile, choose Stop Server, select it again, and choose Start Server. Complete the Allow, Open, and Open Visual Studio Code prompts.

“Unknown OAuth client or unregistered redirect_uri”

Run Authentication: Remove Dynamic Authentication Providers from the Command Palette and remove only the production provider containing mcp.silverile.com. Then stop and start Silverile and authenticate again. This clears the stale VS Code OAuth registration without uninstalling the extension.

Silverile tools do not appear in Agent Mode

Open MCP: List Servers → Silverile → Show Output. A successful connection ends with “Discovered … tools.” Then open Chat and enable the Silverile tools in the tool picker.

Authentication completed in the browser but VS Code is still waiting

Return to the browser tab and choose Open Visual Studio Code in the final browser prompt. If that prompt was dismissed, use the “click here” return link on the success page.

“API key invalid” or connection error

Reset the Silverile dynamic authentication provider in VS Code, stop and start the server, and authenticate again. Confirm that the API key is still active in Silverile.

The first MCP request returns 401

This is expected before authentication. VS Code uses the 401 challenge to discover the OAuth server and open the authorization flow.

New Silverile tools are not visible after a server update

Run MCP: List Servers, select Silverile, and choose Restart Server. Use Show Output to confirm that VS Code discovered the current tool list.

Chat is not in Agent Mode

Open Chat from the Activity Bar, use the mode selector to switch to Agent Mode, and enable Silverile in the tool picker.

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.

On this page