pulsemcp scanned Safe content atomic mcp-remote

Microsoft Edit

This MCP server provides file editing capabilities through Microsoft Edit integration, implementing a hybrid architecture that combines direct file system operations for simple tasks with Microsoft Edit process management for complex editing scenarios. Built with TypeScript and featuring both stdio and HTTP transport modes, it offers tools for reading, writing, and listing files, finding text patterns, formatting code, performing complex find-and-replace operations, and managing interactive editing sessions across multiple files. The implementation includes an intelligent operation router that analyzes file complexity and operation requirements to determine whether to use direct file system access or spawn Edit instances, along with comprehensive HTTP REST API endpoints, authentication support, rate limiting, and Docker-friendly configuration, making it valuable for AI-assisted code editing workflows, automated refactoring tasks, and any use case requiring sophisticated file manipulation with the power of Microsoft Edit's advanced text processing capabilities.

Cognium trust score

70%

Tier

Scanned

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: cloud-infra
Source: PulseMCP
Repository: github.com/mixelpixx/microsoft-edit-mcp
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve Microsoft Edit 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"