pulsemcp verified Safe content atomic mcp-remote

.NET Framework Development

This MCP server provides .NET Framework development capabilities through TCP communication, enabling AI assistants to build projects, run tests, and analyze solutions using MSBuild and Visual Studio tools. Built by bytedreamer using C# with .NET 8 and targeting .NET Framework projects, it offers three core tools: build_project for compiling solutions/projects with MSBuild integration and detailed error parsing, run_tests supporting MSTest/NUnit/xUnit frameworks with VSTest.Console execution, and solution analysis for project structure inspection. The implementation features automatic Visual Studio version detection (2019/2022), flexible MSBuild path resolution, comprehensive test framework detection, structured error reporting with file/line information, and cross-platform support through WSL bridge scripts, making it valuable for legacy .NET Framework maintenance, automated CI/CD workflows, and building AI assistants that need programmatic access to Windows-based .NET development tools without manual Visual Studio navigation.

Cognium trust score

100%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.

Scan details: Circle-IR · 2026-09-28 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: devops-ci
Source: PulseMCP
Repository: github.com/bytedreamer/dotnetframeworkmcp
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve .NET Framework Development from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"