Refactoring MCP
The Refactoring MCP server provides HTTP API and CLI tools for generating, storing, and managing structured protocol and governance refactoring prompts along with guidance documentation.
Core Capabilities:
Service Monitoring: Check server status, version, uptime, and metadata via
service_statustoolDocumentation Access: List all guidance documents, fetch individual documents by key (spec_prompts, prd, trd, mcp_server, trd_questions, agents), or download all documents as a bundle
Prompt Generation: Generate protocol or governance prompts using built-in builders with schema validation and optional parameters
Prompt Management: List stored prompts with metadata (ID, type, project name, timestamp) and retrieve specific prompts by ID with in-memory storage
Server Operations: Start and monitor via CLI (
refactoring-mcpornpm start) with configurable port settingsIntegration: Use with MCP clients through standard configuration and integrate with automation workflows for downstream tooling consumption
Testing: Run validation tests to ensure prompt builders, store, and validators function correctly
Primary Use Cases: Provide automation-ready API access to refactoring governance templates, enable consistent prompt generation for MCP workflows, and support platform engineers and reviewers with standardized refactoring messaging.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Refactoring MCP generate a governance prompt for updating our API rate limits"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Refactoring MCP — PRD
This project turns the Refactoring MCP prompt and governance specification templates into a dedicated MCP server so teams can host structured prompt generation via HTTP and automation scripts.
1. MCP Server Goal
What is this project?
A dedicated MCP server (built on@modelcontextprotocol/sdk) that exposes MCP tools for generating protocol and governance prompt payloads following the Refactoring MCP standards.What problem does it solve?
Documentation-only templates are hard to integrate; this MCP server exposes prompt builders via HTTP so downstream automation and review tooling can consume the specs.Who is the primary user?
Platform engineers, MCP reviewers, or automation scripts needing consistent refactoring governance messaging via MCP workflows.
2. Success Definition
How do we know this project is successful?
The npm package publishes, the MCP server starts, and prompts can be generated and stored via therefactoring_mcp_*tools.What measurable outcome must be achieved?
npm testsucceeds,npm start(orrefactoring-mcp) brings the MCP service online, and at least one prompt record can be created through the MCP tools.What does failure look like?
Prompt definitions remain stuck in Markdown without API access, or the automated validation/tests do not run.
3. Core MCP Server Action
What is the single most important action a user performs?
Start the MCP server (vianpm startorrefactoring-mcp), host the API, and POST a protocol/governance prompt definition for downstream tooling.What moment should make the user say “this works”?
A successfulPOST /api/promptsfollowed by aGET /api/prompts/:idthat returns the prompt text and metadata.
4. Non-Goals
What will this project NOT attempt to do?
It does not persist prompts beyond in-memory, support authentication, or orchestrate remote agents.What features are explicitly out of scope?
Any persistent database, full LLM orchestration, or advanced scheduling can be deferred to future MCPs.
5. Constraints
Time constraints: Keep the MVP lean for npm publishing—no long-running refactors.
Scope constraints: Single MCP server (Express + prompt builders) without sprawling CLI features.
Resource constraints: Only trusted dependencies (Express, built-in Node modules) are permitted.
Validation Check
Can the project goal be explained in one sentence? Yes — “Expose Refactoring MCP prompts via an Express API and CLI for automation-ready tooling.”
Can success be evaluated without subjective judgment? Yes — endpoints respond successfully and tests pass.
6. MCP Server Usage
Installation
npm install -g refactoring-mcp(ornpm install refactoring-mcpfor local use).
Run (stdio)
refactoring-mcpornpm startboots the MCP server on port 3000 by default.Use
--port <number>(or-p) or set thePORTenv var to change the listening port.
Example MCP Client Config
{
"command": "npx",
"args": ["-y", "refactoring-mcp"]
}Tools
service_status→ return service metadata (name, version, uptime, timestamp).refactoring_mcp_list_documents→ list the guidance documents that describe this MCP.refactoring_mcp_get_document→ fetch a specific guidance document by key.refactoring_mcp_get_bundle→ download all guidance documents in one bundle.refactoring_mcp_generate_prompt→ build a protocol or governance prompt, validate the schema, and store the payload.refactoring_mcp_list_prompts→ inspect saved prompt metadata and timestamps.refactoring_mcp_get_prompt→ retrieve a stored prompt byid.
Documents
spec→docs/spec-prompts.md(protocol & governance spec templates).trd→TRD.md(technical boundaries for the MCP server).mcp_server→docs/mcp-server.md(server responsibilities and customization steps).agents→examples/AGENTS.md(agent instructions tied to this MCP).trd_questions→prompts/trd.questions.md(prompt template for drafting the TRD).
Tool Overview
service_statuskeeps MCP agents aware of the running version and uptime of the server.refactoring_mcp_*tools encapsulate prompt generation, doc discovery, and persisted prompt storage so other agents can consume the MCP output.
MCP Server Runtime
refactoring-mcp(installed globally) ornpm startstarts the MCP server so agents can access prompt specs.Override the port with
--port,-p, or thePORTenvironment variable.
Testing & Validation
npm testrunstsc(build) and thennode --test ./dist/test/*.test.js, covering the prompt builders, store, and validators.
Available Tools
7 toolsrefactoring_mcp_generate_promptGenerate Refactoring MCP PromptB
Generate a protocol or governance prompt using the Refactoring MCP builders and persist the output.
Inputs: type (required), options. Returns: spec, errors
refactoring_mcp_get_bundleRefactoring MCP BundleB
Return all Refactoring MCP guidance documents in one bundle.
Inputs: no named parameters. Returns: bundle
refactoring_mcp_get_documentRefactoring MCP DocumentB
Fetch a Refactoring MCP document by key.
Inputs: document (required). Returns: document
refactoring_mcp_get_promptFetch a stored promptB
Retrieve a stored Refactoring MCP prompt by ID.
Inputs: id (required). Returns: prompt
refactoring_mcp_list_documentsRefactoring MCP DocumentsB
List the published Refactoring MCP guidance documents.
Inputs: no named parameters. Returns: documents
refactoring_mcp_list_promptsList stored Refactoring MCP promptsB
Return metadata for all prompts stored in the MCP server.
Inputs: no named parameters. Returns: prompts
service_statusRefactoring MCP StatusB
Return the MCP server metadata and uptime.
Inputs: no named parameters. Returns: uptime, service, version, timestamp
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: generate_prompt creates new prompts, get_bundle retrieves all documents, get_document fetches a specific document, get_prompt retrieves a specific prompt, list_documents lists documents, list_prompts lists prompts, and service_status provides server metadata. There is no overlap in functionality, making tool selection unambiguous.
Six of the seven tools follow a consistent 'refactoring_mcp_verb_noun' pattern (e.g., refactoring_mcp_generate_prompt, refactoring_mcp_list_documents), which is highly predictable. However, 'service_status' deviates from this pattern by using a different prefix and structure, slightly reducing consistency.
With 7 tools, the count is well-scoped for a refactoring MCP server focused on document and prompt management. Each tool serves a specific role (e.g., generation, retrieval, listing, status), and none appear redundant, making the set appropriately sized for its domain.
The tool set covers core operations for managing refactoring MCP documents and prompts, including listing, retrieving, generating, and bundling. A minor gap exists in the lack of update or delete tools for documents or prompts, which could limit lifecycle management, but agents can likely work around this with the provided tools.
Related MCP Connectors
Generate contextual prompts and reusable agent skills, evaluate prompts with the 16-dimension Prompt Score, and manage saved work in PromptDrive. Twelve MCP tools also provide authorized access to private Memory for source-grounded answers. Connect over Streamable HTTP using OAuth 2.1 and PKCE. Generation consumes account quota and automatically saves successful results; Memory access follows account permissions and plan limits.
Free MCP contract auditing for AI agents and developers. Check tool schemas, detect potential breaking changes between versions, and get structured compatibility findings before deployment. Static analysis only.
Team prompt library with version control and reviews. Save, search and reuse prompts via MCP.
Statically audits MCP tool surfaces for token cost, schema quality, and design issues.