VS Code Coding Assistant (nys)

A Visual Studio Coding Assistant that connects to Model Context Protocol (MCP) servers and External data sources to provide maximum output to user's request. It provides an AI Chat panel, executes prompts, lists available tools, and supports both HTTP/WebSocket servers and local stdio binaries. it also has special base prompts, debugging, coding and orchestration workflows build in and provide graph database connection to store relationship in codebase to generate documentations to better assist in daily task

demo.mp4

Key Features

• Connect to MCP servers
  • Standard HTTP/WebSocket servers
  • Stdio mode for local binaries (e.g., GitHub MCP server)
• AI Chat webview (View: MCP AI Chat → AI Chat)
• Commands: Connect, Execute Prompt, List Tools, Open Chat View, Disconnect
• Status bar integration (connection/processing state)
• Tool discovery cached on connect (no periodic 30‑min refresh)
• Leverages MCP protocol to perform elicitation reducing hallucination rate
• Format's user's prompt based on previous chat and project context improving result output
• Read and work with knowledge and Guidelines from specific directories and files
• Provide request/response cost
• Should be capable of rolling back to any code version
• Langchain Intergration for chat orchestration and memory management

Requirements

• Visual Studio Code 1.60.0 or newer
• Access to an MCP server:
  • Standard HTTP/WebSocket endpoint, or
  • A local stdio-compatible binary (e.g., github-mcp-server), or
  • Optional demo Filesystem server (run-mcp-server.sh)
• Credentials:
  • API key for your MCP/LLM service, or
  • GitHub Personal Access Token when using github-mcp-server
• Optional for semantic tool selection:
  • Embedding MCP endpoint and Vector MCP endpoint, or
  • A reachable Milvus instance
• For building/packaging from source: Node.js and npm

Quick Start

1.1) Installing from the VS Code Marketplace

• Search for "nys" in the Extensions view
• Click Install

1.2) Installing from source

• From VSIX: Build or download a .vsix, then in VS Code: Extensions → … → Install from VSIX…

2. Configure (Settings → “nys”)

3. Use

• Command Palette → MCP: Connect to Server
• Command Palette → MCP: Open Chat View (or MCP: Execute Prompt)
• Command Palette → MCP: List Available Tools

Commands

• MCP: Connect to Server (vscode-mcp-client.connect)
• MCP: Disconnect (vscode-mcp-client.disconnect)
• MCP: Execute Prompt (vscode-mcp-client.executePrompt)
• MCP: List Available Tools (vscode-mcp-client.listTools)
• MCP: Open Chat View (vscode-mcp-client.openChatView)

Configuration (summary)

Security & Privacy

• No telemetry is collected by this extension.
• Network access is limited to the endpoints you configure (MCP server, optional Embedding MCP, Vector MCP, or Milvus).
• Credentials:
  • Standard HTTP/HTTPS: If provided, an Authorization: Bearer header is used for MCP requests.
  • Stdio mode: Tokens are forwarded to the MCP binary via environment variables (GITHUB_PERSONAL_ACCESS_TOKEN, GITHUB_TOKEN, API_KEY) for compatibility.
  • Tokens are only persisted if you explicitly save them in VS Code settings.
• Tool discovery is cached in memory for the session after connecting; there is no periodic background refresh.
• Logs may include masked identifiers for debugging; avoid sharing logs that could contain sensitive project details.

Troubleshooting

• Not connected? Ensure serverUrl is correct. For stdio, verify the binary path and that your token is valid.
• GitHub MCP stdio: In stdio mode the extension forwards the token via GITHUB_PERSONAL_ACCESS_TOKEN/GITHUB_TOKEN and API_KEY env vars.
• Tool list empty? Connect first; tools are fetched on connect and cached for the session.
• Semantic selection requires embedding/vector config (Vector MCP) or Milvus connectivity.

Links

• Changelog: CHANGELOG.md
• Usage guide: USAGE_GUIDE.md
• Publish guide: publishGuide.md
• Issues & Support: https://github.com/Christiantyemele/mimie/issues

License

MIT