Systemdox MCP server

Read from the package source without running it. The installed server may list more.

• create_checkwrite action
• create_guardrailwrite action
• create_project_rulewrite action

  Create a new project rule in SystemDox Standards. Use this when you discover a team principle or convention that should be enforced across the project.

• create_prompt_templatewrite action

  Create a new reusable prompt template in SystemDox Standards. Use this to store preconfigured prompts for common AI tasks like code reviews, documentation generation, or analysis frameworks.

• get_checks
• get_context

  Intelligent context aggregator: fetches checks, specs, docs, and tech stack, ranks them by relevance to your current task, and returns the full text of the highest-ranked items within a token budget \u2014 each with the ID needed to fetch the rest. Use this instead of calling individual tools when you want curated, relevant context.

• get_docs

  Retrieve synced documentation from connected GitHub repositories. Filter by repo, file path pattern, or keyword search. Pass doc_id with section (a heading anchor) or chunk_id to retrieve just that section instead of the whole document.

• get_guardrails
• get_plan_board

  Read the GitHub Projects boards connected to this workspace. With no arguments, lists the open boards with their item counts by status. With project_number, lists that board's issues grouped by status (In Progress / Todo / Done), each with issue number, title, repo, labels, assignees and URL \u2014 so you can see what is planned or in flight and pick up the right issue. Read-only: this tool cannot

• get_planning_context

  Retrieve org-wide planning context: connected repos with summaries, cross-repo dependencies, ADRs, and active specs. Optionally focus on a target repo.

• get_project_rules

  Retrieve project rules defined in SystemDox Standards. These are team-defined principles covering deployment, architecture, security, testing, and process. Filter by category to get only relevant rules.

• get_prompt_templates

  Retrieve reusable prompt templates from SystemDox Standards. These are preconfigured prompts that Gen AI should use when generating content \u2014 e.g. code review checklists, documentation templates, or analysis frameworks.

• get_specs

  Retrieve SystemDox specifications (proposal, requirements with RFC 2119 keywords, Given/When/Then scenarios). Get a specific spec by ID, filter by status, or search by keyword.

• get_tech_stack

  Retrieve the configured technology stack (languages, frameworks, databases, infrastructure) with versions and notes.

• report_decision

  Record an architecture decision made during development. Creates a draft ADR in SystemDox for human review.

• update_specwrite action

  Update an existing SystemDox spec's proposal, tasks, or requirements. Only draft specs can be modified \u2014 published specs must be versioned first.

• Code scan38 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityno repository or website to verify2/10

Systemdox: common questions

Is Systemdox MCP server safe?

With care: it is graded C, so read the findings first (55/100). Read the Systemdox safety report

How do I install Systemdox?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does Systemdox need an API key?

Yes. The registry entry asks for SYSTEMDOX_API_KEY.

Is Systemdox maintained?

The latest release is v0.1.35.

What can I use instead of Systemdox?

Servers from other publishers that do the same job: no_human MCP server, loci MCP server and SvGrid MCP server. Compare all Systemdox alternatives.