Remote Documentation RAGs

Remote Documentation RAGs

Three remote MCP servers (Cloudflare Workers) that serve indexed EPLAN documentation over semantic or keyword search — already deployed, no local data required. Use them to verify an exact action name or parameter before guessing.

< Back to Home

---

The three servers

# EPLAN Electric P8 documentation (2026, semantic search)
claude mcp add eplan-rag -- cmd /c npx mcp-remote https://rag2026.covaga.xyz/mcp

# EPLAN EEC Pro 2026 documentation
claude mcp add eecpro-rag -- cmd /c npx mcp-remote https://rageecpro.covaga.xyz/mcp

# EPLAN Electric P8 documentation (2027, keyword/full-text search)
claude mcp add eplan-wiki-2027 -- cmd /c npx mcp-remote https://rag2027.covaga.xyz/mcp

Server	Doc version	Search mode	Backing
eplan-rag (rag2026.covaga.xyz)	EPLAN P8 2026	Semantic (Vectorize + bge-base)	cloudflare-rag-eplan-p8/
eecpro-rag (rageecpro.covaga.xyz)	EEC Pro 2026	Semantic	cloudflare-rag-eecpro/
eplan-wiki-2027 (rag2027.covaga.xyz)	EPLAN P8 2027	Keyword/FTS5 (SQLite + bm25)	cloudflare-rag-eplan-2027/

eplan-wiki-2027 is deliberately a separate server, not a 2026→2027 upgrade of eplan-rag: different doc version and a different search mode. Measured against each other on real queries, they fail differently — FTS5 wins on exact-name lookups ("what's the signature of X"), semantic wins when the query shares no vocabulary with the docs at all. Use both.

Plain REST API

Handy for a quick check without adding an MCP server:

curl -X POST https://rag2026.covaga.xyz/search -H "Content-Type: application/json" \
     -d "{\"query\": \"export project pdf\", \"topK\": 3}"

curl -X POST https://rag2027.covaga.xyz/search -H "Content-Type: application/json" \
     -d "{\"query\": \"FindAction\", \"topK\": 3}"

eecpro-rag exposes the equivalent search endpoint at rageecpro.covaga.xyz.

See cloudflare-rag-eplan-p8/README.md and cloudflare-rag-eecpro/README.md in the repo for the full tool list, REST endpoints, and architecture of each Worker.

Why this matters for tool calls

Action names and parameters in the EPLAN API are exact identifiers, not something an LLM should improvise from pretrained knowledge. tools/validate_actions.py in eplan-p8-mcp-server/ cross-checks this repo's wrappers against the RAG for exactly this reason — see Claude Code Skill for how the skill enforces the same discipline when writing new EPLAN code.