Silverile.AI for VS Code

Connect VS Code to the Silverile HTTP MCP server so that AI coding agents (GitHub Copilot, Claude, etc.) can read and update your Agile work items directly inside the editor.

Features

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

Quick Start

1. Install the extension.
2. Open a workspace folder.
3. Run Silverile: Configure MCP from the Command Palette (Ctrl+Shift+P / Cmd+Shift+P).
4. Enter your Silverile API Key ID, API Key Secret, and Product ID in the setup page.
5. Click Save & Start. The extension registers and starts the Silverile MCP server.
6. Open Copilot Chat in Agent Mode and use the Silverile tools.

Secrets are stored in VS Code SecretStorage. They are not written to .vscode/mcp.json.

After Configuration

After Silverile: Configure MCP runs, Silverile tools appear after the extension-provided MCP server starts.

Recommended flow:

1. Open Copilot Chat in Agent Mode.
2. Confirm Silverile tools are visible in the tools list.
3. Try show stories, show my work, or validate Silverile connection.

The extension also offers quick actions after configuration: Open MCP Servers, Open Copilot Chat, and View Instructions.

MCP Registration

The extension uses VS Code's MCP server provider API to register Silverile. It also removes old silverile entries from workspace .vscode/mcp.json to avoid duplicate servers.

Automatic Tool Refresh

The extension fires an MCP reconnect 2 seconds after VS Code starts. This means Silverile tools are always up to date — when new tools are released on the Silverile MCP server, they appear automatically the next time you open VS Code without any manual action.

Reconnect Silverile MCP

Use Silverile: Reconnect Silverile MCP if you need to force an immediate reload of the Silverile MCP tools within the current session (e.g. after a credential change or network interruption).

This command:

• Removes old workspace .vscode/mcp.json Silverile entries
• Keeps stored credentials in VS Code SecretStorage
• Attempts to restart the extension-provided Silverile MCP server

This does not revoke server-side access and does not rewrite raw secrets to the workspace file.

Reset MCP Credentials

Use Silverile: Reset MCP Credentials when you need to change the Silverile API Key ID, API Key Secret, or Product ID.

This command opens the setup page for new values, stores them in VS Code SecretStorage, removes old workspace silverile MCP entries, and tries to restart the extension-provided Silverile MCP server.

Settings

Sign Out

Silverile: Sign Out removes Silverile from:

• VS Code SecretStorage
• Any old workspace .vscode/mcp.json Silverile entry

It does not revoke server-side access. It only removes local Silverile MCP configuration and stored credentials.

Publishing as an update to the existing Marketplace extension

This project uses the same publisher (silverile) and name (silverile) as the previous extension, so publishing it replaces the existing Marketplace listing under the same extension ID (silverile.silverile).

# Package and inspect the .vsix before publishing
npm run package

# Publish (requires a Personal Access Token with Marketplace scope)
npx vsce publish
# or
npm run publish-ext

The PAT must be set via vsce login silverile or the VSCE_PAT environment variable.

Development

npm install
npm run compile      # one-shot TypeScript build
npm run watch        # incremental rebuild on save
npm run package      # build + create .vsix

Press F5 in VS Code (with the Extension Development Host launch config) to run the extension in debug mode.