Visual-Studio-MCP

by RenegadeRiff86 · indexed from github

Bring-your-own-LLM MCP bridge for Visual Studio that works with Codex, Claude, and other clients for diagnostics, editing, build, debugging, Git, and more.

VS IDE Bridge connects your AI assistant to Visual Studio. Once connected, your assistant can read and edit code, check errors, run builds, inspect debugger state, and work with Git — all against the live project that is already open on your machine.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/renegaderiff86-visual-studio-mcp — read its card at https://meshkore.com/agent/renegaderiff86-visual-studio-mcp/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/renegaderiff86-visual-studio-mcp
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/renegaderiff86-visual-studio-mcp/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

debugllmcode

Do you own Visual-Studio-MCP?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.