CliDeck MCP gives AI agents exact, version-aware network knowledge. Known answers are fast and repeatable. Unknown questions are researched, independently checked, and published only when they are ready.
How do I check interface health before a maintenance change?
Review status, errors, and recent changes before continuing.
show interfaces statusLive proof, not a promise
These aggregate signals come from the running public service. Private source details never reach this page.
Checking the live public service…
The simple version
Your AI remains responsible for understanding the request and choosing a tool. CliDeck supplies the precise, specialized facts that change too often to trust to model memory alone.
The question arrives with device, operating system, version, and workflow context.
Known knowledge is retrieved and validated deterministically—without generating a new answer.
The response includes prerequisites, risks, verification, rollback, conflicts, and honest limitations.
Missing knowledge becomes a research demand. It is reusable only after independent checks and publication.
What it helps with
Start with a read-only question, then use the same knowledge layer across planning, review, and verification.
Find a command that matches the vendor, model, operating system, version, and CLI mode you are actually using.
Check proposed commands or configuration changes for prerequisites, risk, stop conditions, verification, and rollback.
Turn a sanitized CLI snapshot into useful device context without storing the raw output by default.
Compare current and target versions with compatibility checks, required preparation, and a verification plan.
Compare before-and-after evidence and get a structured result instead of relying on a visual guess.
Interpret CDP, LLDP, route, and traceroute output to surface paths, links, and likely fault domains.
Browser-native WebMCP
The CliDeck Network Evidence Workbench turns a question and selected network evidence into a revision-safe case. CliDeck detects the device context, searches active version-aware knowledge, and lets a WebMCP-capable browser agent work through six typed tools—without hidden access to the complete file or your equipment.
Files are processed in the browser. Only the selected, locally redacted evidence window is sent to CliDeck, and browser-agent access requires an explicit opt-in.
Device model, operating system, software version, case version, and active knowledge revision stay attached to the investigation. Stale responses cannot overwrite a changed case.
Official CliDeck results retain applicability and provenance. The browser agent’s analysis appears separately and can cite only results from the current case.
Every primary workflow also has an ordinary browser control, so the workbench remains usable when browser-native WebMCP is unavailable.
Shared case workflow
Selected evidence. Current case only. Verified sources.
Paste evidence or select a supported local file and describe the question.
Choose the relevant page or line window. Secrets are redacted locally before a request is sent.
CliDeck identifies the device context and searches active, version-aware knowledge and workflows.
The browser agent can explain the current sourced result, or CliDeck can track a real research task when the answer is unknown.
read_network_casereads a bounded window of user-approved, locally redacted evidence.
analyze_network_casedetects vendor, model, operating system, and version.
search_network_casesearches active CliDeck knowledge and operational workflows.
present_network_case_analysisplaces the agent’s interpretation separately from official results.
start_case_researchstarts one tracked research task after a real unknown result.
get_case_research_statusreads the current research status without exposing task credentials.
The workbench accepts pasted text and TXT, LOG, MD, CSV, JSON, JSONL, HTML, and text-layer PDF files within the limits shown in the interface. OCR, encrypted PDFs, and image-only PDFs are not supported.
Watch the walkthrough
This practical walkthrough follows CliDeck Knowledge MCP with Codex and GPT-5.6—from the public connection to technical answers that people can inspect instead of simply trust.
Watch on YouTubeThe real product
The public demo uses the same interface, components, pipeline states, charts, and counters as production. Its read-only role blocks final mutations and replaces sensitive values on the server.
Open live demo ↗Connect in minutes
Choose a client, copy the setup, and begin with a low-risk read question. The hosted public endpoint needs no CliDeck account.
https://mcp.clideck.com/mcpFastest setup
codex mcp add clideck --url https://mcp.clideck.com/mcp
codex mcp listNo CliDeck account or access token is required for the public server.
Read the official Codex MCP documentationOpen source by design
The framework, schemas, Domain Pack scaffolder, tests, and project-authored fixtures are available under Apache-2.0. Production knowledge and third-party manuals are intentionally not bundled with the repository.
Universal Domain Packs
A Domain Pack defines the context, record types, schemas, normalization, and deterministic validation for one field. The core keeps publication, history, trust, conflicts, and rollback consistent.
pnpm domain:create -- --id marine-science --name "Marine Science"Trust needs boundaries
CliDeck is designed to support engineering judgment, not conceal uncertainty or bypass change control.
If applicable published knowledge is missing, the result is unknown—not a plausible-sounding command.
Answers can include applicability, prerequisites, risks, verification, rollback, limitations, confidence, and conflicts.
CliDeck never connects to a router, switch, firewall, or server and never executes the commands it describes.
Public responses omit source URLs, manual titles, evidence fragments, internal IDs, credentials, and acquisition details.
FAQ
Start free with the public endpoint, or inspect the complete framework on GitHub.
Yes. You can connect to the public CliDeck MCP endpoint without a CliDeck account or subscription. Your chosen AI client may still have its own plan, API, or usage limits.
No. When verified knowledge already exists, PostgreSQL retrieves the version-aware answer deterministically. AI is reserved for research and review work when the knowledge system needs to learn something new.
No. CliDeck MCP provides knowledge and advisory workflows. It never opens a device session and never executes a command on your infrastructure.
The system returns unknown instead of inventing an answer. The question can become a prioritized research task, but it is reusable only after validation and publication.
Network Knowledge currently has its deepest verified coverage for Cisco Catalyst and IOS XE. Other vendors can be recognized, but coverage varies and the service states those limits clearly.
Yes. The framework is open source under Apache-2.0. Domain Packs keep subject-specific schemas and validation separate from the trusted revision, release, conflict, and rollback core.
The hosted MCP endpoint connects CliDeck’s verified knowledge to AI clients such as Codex, Claude Code, and Cursor. WebMCP exposes narrowly scoped tools from the live web application to a compatible browser agent, so the person and agent can work with the same visible, current case.
No. Analysis, search, research, file selection, and reset remain available through ordinary page controls. A WebMCP-capable browser additionally lets its agent use the six typed tools registered by the workbench.
No. Complete files stay in browser memory. The agent receives no evidence until you explicitly enable sharing, and it can read only the selected, locally redacted evidence window.
No. The workbench analyzes user-provided evidence and retrieves advisory knowledge. It never opens a device session and never executes a command on network infrastructure.
The result remains unknown instead of being filled with a plausible guess. From a genuine unknown result, the workbench can start and track a research task, but starting research does not promise an immediate published answer.
See it before you connect it
Explore the real read-only administration console, then add the free public MCP to your AI client.