SpiceLogic Documentation MCP Server

SpiceLogic publishes an official Model Context Protocol (MCP) server for the WPF HTML Editor control at https://mcp.spicelogic.com/html-editor/wpf, 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 property 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 WPF only - an assistant connected here can never be answered with WinForms'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 WPF and WinForms behind one connection (you then pass product explicitly on every call).

Claude Code

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

Claude Desktop

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

Cursor

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

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

VS Code / GitHub Copilot Chat

Add to .vscode/mcp.json, or run "MCP: Open User Configuration" for every workspace. Note the key is servers, not mcpServers:

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

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

GitHub Copilot CLI

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

OpenAI Codex CLI

Add it from the terminal:

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

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

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

Tools

Tool	Example query
`search_docs(product, query)`	"search_docs wpf spell checker dictionary"
`get_doc_page(product, slug)`	"get_doc_page wpf custom toolbar button"
`get_api(product, symbol)`	"get_api wpf WpfHtmlEditor"
`get_quickstart(product)`	"get_quickstart wpf"
`get_sample(product, task)`	"get_sample wpf 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.