VA Form Generation

External MCP server that audits and fixes VA forms to meet 21P-601 and VA.gov content standards.

javascript

1

GitHub Stars

javascript

Language

5 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "agilesix-va-form-generation-mcp": {
      "command": "node",
      "args": [
        "/Users/YOUR_USERNAME/va-form-generation-mcp/index.js"
      ]
    }
  }
}

This external MCP server provides tools to audit and fix VA form scaffolds, ensuring they follow 21P-601 best practices and VA.gov content standards. It runs outside the main VA codebase so you can share improvements across your team and track changes independently.

How to use

You connect an MCP client (Claude Desktop, Claude Code, or Cursor) to the VA Form Generation MCP Server to access a set of form-related tools. Use the available tools to audit forms, generate orchestration prompts, validate form syntax, get agent prompts, and apply quick fixes. The workflow typically starts with an audit, then proceeds to orchestration, and finally executes the necessary agents or tooling steps in a defined order.

How to install

Prerequisites: Node.js and npm must be installed on your computer.

Create the MCP server directory and install dependencies.

cd ~/va-form-generation-mcp
npm install

Additional sections

Configuration for your MCP clients is shown in two equivalent stdio configurations. Choose the one that matches your setup. Both configurations point to the same local index script.

Claude Desktop configuration (stdio) and project-local setup for Claude Code are provided exactly as shown below.

{
  "mcpServers": {
    "va-form-generation": {
      "command": "node",
      "args": [
        "/Users/YOUR_USERNAME/va-form-generation-mcp/index.js"
      ]
    }
  }
}

Security and reliability notes

Keep the MCP server code outside the main VA repos and control access via your existing authentication and workspace permissions. Treat the local path to index.js as you would any executable script, and avoid exposing sensitive workspace paths in shared configs.

Notes on usage across clients

Claude Code (VS Code) and Cursor users add a similar MCP entry to the workspace root: create or update a .mcp.json with the same name and path, then reload the editor window to load the MCP server.

Examples of common workflows

Option 1: Full automation: Audit a form, generate the orchestration prompt, and execute all agents in order.

Option 2: Step-by-step: Retrieve prompts for each agent one at a time and run them manually in sequence.

Available tools

audit_form

Generate a comprehensive audit report for a scaffolded form, including form information, an agent execution plan, expected fixes, and quick start commands.

get_agent_prompt

Retrieve a customized prompt for a specific agent (1-4) with paths tailored to the audited form.

validate_form

Run validation checks on a form’s schema, syntax, apostrophes, and imports, and return commands to execute.

get_fix_reference

Provide quick references for common fixes, including yesNoUI, radioSchema, apostrophes, transformers, and fullNamePath.

generate_orchestration_prompt

Create the complete orchestration prompt to launch all four agents in the recommended order.