Skip to main content

Meet Acumatica AI Resources: Better Context for AI-Assisted Development

  • August 31, 2026
  • 2 replies
  • 76 views

kpopova
Acumatica Employee
Forum|alt.badge.img+3

AI coding agents can move quickly—but only when they have reliable product knowledge and instructions. The new Acumatica AI Resources repository gives AI coding agents structured, version-specific resources for working with Acumatica ERP.

Whether you're upgrading a customization, troubleshooting an integration, or building a Modern UI control, these resources can help your AI coding agent work from relevant Acumatica documentation and development guidance instead of relying only on its general knowledge.

What You’ll Find in the Repository

The 2026R1 branch includes resources aligned with Acumatica ERP 2026 R1:

  • Development skills for updating customization projects, diagnosing and modernizing integrations, and building Modern UI custom controls.
  • Shared agent tools for creating reusable guidance and checking the quality of skills.
  • Official Acumatica 2026 R1 documentation in searchable Markdown, so coding agents can consult it while working.
  • Verification reports showing how the included skills were reviewed.
  • Configuration and discovery files for Claude Code, Cursor, Codex, and GitHub Copilot.

Each future major Acumatica release will have a corresponding branch, so you can use documentation, skills, and supporting resources that match the Acumatica version you're developing for.

Try These Workflows

You can ask a supported AI coding agent to:

  • Update an older customization project for Acumatica 2026 R1.
  • Diagnose and modernize an older REST API integration.
  • Help create a custom control for the Modern UI.
  • Consult the included documentation before giving version-sensitive guidance.
  • Review a new or updated skill for quality and consistency.

Help us improve it

Community contributions are welcome for skills, plugins, prompts, reference material, and other non-documentation resources.

Pull requests are accepted against the latest published major branch only. Before contributing, please read CONTRIBUTING.md. Contributions of new skills and plugins begin with a proposal, and contributed commits require a DCO sign-off.

The Documentation directory is a read-only snapshot of official Acumatica documentation and is not open to external contributions. Please send documentation feedback to training@acumatica.com.

Explore the repository, connect it to your preferred AI coding tool, and let us know what workflows you would like to see supported next:

Explore Acumatica AI Resources on GitHub

2 replies

Forum|alt.badge.img
  • Freshman II
  • August 31, 2026

Thank you ​@kpopova . Very useful.

Note: I used Claude Code to analyze your repo and this reply was partly written by Claude :-).

I'm the author of MCP4Acumatica, an open-source (Apache-2.0) MCP server connecting Claude to Acumatica over the contract-based REST API. Version 0.51.0 — released a day before this post — added documentation tools that let the model look up a screen by Form ID or search the guides while it works. I added this after discovering that the Markdown documentation set was available for download behind a portal login. This release ships an open-source ingestion script and each operator builds their own private index; nothing derived from the docs is committed or redistributed. It works, but every operator repeats the build.

  1. May we distribute a prebuilt index built from the public Documentation/ directory? Asking rather than assuming, since it's excluded from the repo's GPLv3 and marked all rights reserved. The artifact would be a search index of heading breadcrumbs, Form IDs, and section body text chunked verbatim; because it holds real prose I've treated it as the documentation itself, not a transformative work. Publishable, or should I keep per-operator builds? I'll keep per-operator unless you say otherwise.

  2. Any chance of a 2025R2 branch? This is what we currently run — and an index has to match the release the instance is on, or it describes fields that aren't there.

  3. Are you planning an official MCP server? Your README notes that a plugin can reference an MCP server connection configuration, so I'd rather ask than guess. No agenda: if you ship a good one I'll gladly point people at it and stop maintaining mine; if it targets a different use case, mine stays as an alternative.

One note from ingesting the corpus: Documentation/ReleaseNotes/ has only images, no release-notes text — and your own acumatica-integration-diagnostics skill falls back to asking the user for release notes. That's what I'd most like added next.


TimRodman
Pro III
Forum|alt.badge.img+1
  • Pro III
  • August 31, 2026

This is awesome! Thank you for sharing!

Written by Tim, not Claude 😀