SpiceLogic Documentation MCP Server

SpiceLogic publishes an official Model Context Protocol (MCP) server for the WinForms HTML Editor control at https://mcp.spicelogic.com/html-editor/winforms, using the Streamable HTTP transport. It gives AI coding assistants direct, verified access to the control's documentation and public API surface, so an assistant can integrate the editor correctly on the first pass instead of guessing at method names or pasting outdated examples. SpiceLogic is among the first .NET UI component vendors to ship an MCP server alongside its controls.

This URL is scoped to WinForms only - an assistant connected here can never be answered with WPF's API or docs by mistake, even if it passes the wrong argument. A shared https://mcp.spicelogic.com/html-editor URL also exists for anyone who wants both WinForms and WPF behind one connection (you then pass product explicitly on every call).

The server is a remote read-only documentation endpoint over HTTPS. Nothing is installed on a developer machine, no account is created, and no key is issued, which keeps it straightforward to approve on a managed corporate workstation.

Visual Studio (GitHub Copilot)

Visual Studio 2026, or Visual Studio 2022 version 17.14 and later. Create .mcp.json beside your solution file:

{
  "servers": {
    "spicelogic-winforms-editor": {
      "url": "https://mcp.spicelogic.com/html-editor/winforms"
    }
  }
}

Save the file and Copilot reloads its servers automatically. Then switch Copilot Chat to Agent mode, open the tool picker, and enable the SpiceLogic tools - MCP tools are only available in Agent mode, and new tools start disabled until you turn them on.

Visual Studio also reads %USERPROFILE%\.mcp.json if you want the server available in every solution, and <solution>\.vs\mcp.json for a machine-local setup. Keeping the file at the solution root and checking it into source control is usually best: add it to Solution Items and every developer on the team is connected on their next pull.

VS Code (GitHub Copilot Chat)

Add to .vscode/mcp.json, or run "MCP: Open User Configuration" to have it in every workspace. Note the key is servers, not mcpServers, and remote servers need "type": "http":

{
  "servers": {
    "spicelogic-winforms-editor": {
      "type": "http",
      "url": "https://mcp.spicelogic.com/html-editor/winforms"
    }
  }
}

Switch Copilot Chat from Ask to Agent mode - MCP tools are only available there.

GitHub Copilot CLI

copilot mcp add --transport http spicelogic-winforms-editor https://mcp.spicelogic.com/html-editor/winforms

Claude Code

claude mcp add --transport http spicelogic-winforms-editor https://mcp.spicelogic.com/html-editor/winforms

Claude Desktop

Settings (Ctrl+, or the app menu) → Connectors → Add → Add custom connector → paste https://mcp.spicelogic.com/html-editor/winforms → Add.

Cursor

Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "spicelogic-winforms-editor": {
      "url": "https://mcp.spicelogic.com/html-editor/winforms"
    }
  }
}

OpenAI Codex CLI

Add it from the terminal:

codex mcp add spicelogic-winforms-editor --url https://mcp.spicelogic.com/html-editor/winforms

Or write it into ~/.codex/config.toml by hand (TOML, not JSON):

[mcp_servers.spicelogic-winforms-editor]
url = "https://mcp.spicelogic.com/html-editor/winforms"

Tools

Tool	Example query
`search_docs(product, query)`	"search_docs winforms spell checker dictionary"
`get_doc_page(product, slug)`	"get_doc_page winforms custom toolbar button"
`get_api(product, symbol)`	"get_api winforms WinFormHtmlEditor"
`get_quickstart(product)`	"get_quickstart winforms"
`get_sample(product, task)`	"get_sample winforms insert an image"

On this product-specific URL, product is optional - the URL always wins. The get_api and get_quickstart answers are generated directly from the shipped NuGet package and its XML documentation comments on every release, so they can never drift from what you actually installed.

The server is rate limited per IP address to keep it fair for every user; a well-behaved assistant session will never come close to the limit. A companion llms.txt file lists the same documentation for assistants that prefer a plain-text index over MCP tool calls.