Collaboration

coedithtml.com

Shares self-contained HTML artifacts on Coedit and reads back comments, sticky notes, and edits for collaborative review.

1 endpoint4 known toolsFirst detected September 17, 2026Last detected September 17, 2026

ENDPOINT 1

https://app.coedithtml.com/mcp

No auth detected

Capabilities

tools

Put a single self-contained HTML file on Coedit and get a link other people can open, comment on, and edit in the browser.

Potential side effects

Read back everything people left on a Coedit link: comments on passages they quoted, sticky notes on the page, and text they changed themselves.

Inferred read-only

Publish a rewritten version of an artifact already on Coedit.

Potential side effects

Get a direct upload URL for a revised artifact too large to send through coedit_update_artifact, whose html argument tops out around 1MB.

Potential side effects

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.coedit]
url = "https://app.coedithtml.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "coedit": {
      "type": "http",
      "url": "https://app.coedithtml.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: coedit
Remote MCP URL: https://app.coedithtml.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "coedit": {
      "url": "https://app.coedithtml.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "coedit": {
      "type": "http",
      "url": "https://app.coedithtml.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "coedit",
  "transport": "streamable-http",
  "url": "https://app.coedithtml.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.