Skip to main content
Glama
accform-layout-mcp

accform-layout-mcp

by demilul

accform-layout-mcp

Local MCP server and CLI for Access layout files (*.bas, SaveAsText), rendered to SVG without Microsoft Access. This lets you visually verify form/report layout changes directly.

Features

  • MCP tools: render_form, render_form_svg, list_forms

  • CLI: accform-cli for single-file and batch rendering

  • Default output under rendered/YYYY-MM-DD/

  • Optional PNG export via cairosvg

Related MCP server: Generative-UI-MCP

Installation

Install from repository

python -m venv .venv
.venv\Scripts\activate
pip install .

Optional PNG support:

pip install ".[png]"

Start the MCP server

After installation:

accform-layout-mcp

Alternative (directly from repository):

python server.py

Use the CLI

Render a single file:

accform-cli path/to/F_Contract.bas

Render multiple files in one run:

accform-cli forms/F_Contract.bas forms/F_Customer.bas

Use a custom output directory:

accform-cli forms/F_Contract.bas -o out/svg

Generate optional PNG output:

accform-cli forms/F_Contract.bas --png

Show all options:

accform-cli --help

MCP in VS Code Copilot (Agent Mode)

Example for .vscode/mcp.json:

{
  "servers": {
    "accform-layout": {
      "type": "stdio",
      "command": "python",
      "args": ["${workspaceFolder}/server.py"],
      "env": {
        "ACCFORM_SRC_ROOT": "${workspaceFolder}"
      }
    }
  }
}

ACCFORM_SRC_ROOT limits file discovery to your project folder.

Tool behavior

  • render_form(form, scale_mode="Universal")

    • renders SVG to rendered/YYYY-MM-DD/...

    • returns the path to the generated file

  • render_form_svg(form, scale_mode="Universal")

    • returns SVG markup as text

    • also writes the same SVG file to disk

  • list_forms()

    • lists all detected layout *.bas files under ACCFORM_SRC_ROOT

What rendering includes

Static rendering includes declarative designer state:

  • positions, sizes, captions

  • absolute colors

  • visible/hidden controls (hidden controls are dimmed)

It does not include runtime VBA behavior, for example:

  • Form_Load logic

  • dynamic RecordSource

  • conditional formatting

  • data-driven subforms

Fidelity

Faithfully ported: parse tree, twips-to-pixel conversion, section stacking, painter order, and renderers for Label/TextBox/ComboBox/ListBox/CommandButton/Rectangle/Line, including OLE color conversion.

Reconstructed: CheckBox/OptionButton, Image, Tab, Subform, OptionGroup, placeholder rendering, and theme color references.

Development

Install dependencies from requirements.txt:

pip install -r requirements.txt

License

MIT. See LICENSE.

Available Tools

3 tools
list_formsA

List the Access form/report layout files (*.bas designer files) available under the configured source root, as paths relative to it.

Inputs: no named parameters. Returns: result

render_formA

Render an Access form/report layout to SVG and store it under a dated artifact folder so the result is inspectable without a native Cairo stack.

Pass the form name (e.g. 'A_Lot_Liste') or the path to its *.bas layout file. The render reflects only the declarative designer layout on disk: positions, sizes, captions, absolute colours, hidden controls (dimmed). It does NOT reflect runtime VBA behaviour (Form_Load hiding controls, dynamic RecordSource, conditional formatting).

Inputs: form (required), scale_mode. Returns: result

render_form_svgA

Render an Access form/report layout to SVG markup (text). Useful when you want to inspect exact control coordinates, sizes and captions rather than just look at a picture. Same layout caveats as render_form.

Inputs: form (required), scale_mode. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing available forms, rendering to a stored SVG file, and rendering to SVG text output. There is no overlap or ambiguity.

    Naming Consistency4/5

    All tools follow an underscore_separated verb_noun pattern. 'render_form_svg' is a slight deviation as it adds a suffix, but it is still clear and consistent with the base verb.

    Tool Count5/5

    With only 3 tools, the server is well-scoped for its purpose of inspecting Access form layouts. Each tool is justified and there is no bloat.

    Completeness4/5

    The server covers the core workflow: list forms and render them in two formats. It lacks tools for modifying or uploading forms, but for an inspection-focused server, this is a minor gap.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers