Summary
Make local / self-hosted DocParse usage a first-class, documented path for people who discover us through the Claude Code skill — either by guiding them to the local docparse CLI, or (if there's demand) by supporting a configurable/local MCP endpoint.
Background
In #1, @henkisdabro got the plugin installing, then found the Claude Code skill is cloud-API only: its MCP server points at the hosted endpoint (https://docparse.ailang.sunholo.com/mcp/) with no way to target a local/self-hosted instance. They wanted local DocParse and uninstalled.
Two things worth noting:
- Our docs FAQ previously implied the skill could be pointed at a self-hosted instance via
AILANG_PARSE_URL — that was inaccurate for the MCP plugin and is being corrected.
- Local use isn't actually blocked: the
docparse CLI runs entirely locally, and AI agents like Claude Code drive it fine without MCP. So for most "I want local" cases, the answer is "use the CLI" — they just need the right install/commands surfaced.
Options (gauge demand before building)
- Smooth the local-CLI path (likely enough). Surface clear install + usage commands for the local
docparse CLI from the skill / docs, so local users have an obvious working route instead of hitting a dead end. Possibly let the skill detect a local CLI and prefer it.
- Configurable / local MCP endpoint (bigger). Allow the plugin's MCP server URL to be overridden (env var / plugin
userConfig) so it can point at a self-hosted DocParse MCP server.
Priority
Low / nice-to-have — we favour the docparse CLI for local work and haven't prioritised local-via-MCP. Filing to track demand; a short design doc can follow if interest grows.
Acceptance
- Docs clearly distinguish cloud skill (MCP) vs local CLI, with a working documented path for local users.
- (If pursued) the plugin's MCP endpoint is configurable for self-hosted instances.
Filed from #1 feedback by @henkisdabro.
Summary
Make local / self-hosted DocParse usage a first-class, documented path for people who discover us through the Claude Code skill — either by guiding them to the local
docparseCLI, or (if there's demand) by supporting a configurable/local MCP endpoint.Background
In #1, @henkisdabro got the plugin installing, then found the Claude Code skill is cloud-API only: its MCP server points at the hosted endpoint (
https://docparse.ailang.sunholo.com/mcp/) with no way to target a local/self-hosted instance. They wanted local DocParse and uninstalled.Two things worth noting:
AILANG_PARSE_URL— that was inaccurate for the MCP plugin and is being corrected.docparseCLI runs entirely locally, and AI agents like Claude Code drive it fine without MCP. So for most "I want local" cases, the answer is "use the CLI" — they just need the right install/commands surfaced.Options (gauge demand before building)
docparseCLI from the skill / docs, so local users have an obvious working route instead of hitting a dead end. Possibly let the skill detect a local CLI and prefer it.userConfig) so it can point at a self-hosted DocParse MCP server.Priority
Low / nice-to-have — we favour the
docparseCLI for local work and haven't prioritised local-via-MCP. Filing to track demand; a short design doc can follow if interest grows.Acceptance
Filed from #1 feedback by @henkisdabro.