agentleFS
Sign inStart free
yourlastnamesoundslikeatypeofpastayourlastnamesoundslikeatypeofpasta/acumatica-mcp-server/CLAUDE.md

acumatica-mcp-server

CLAUDE.md0 starsChanged 3 months agoMITView on GitHub

Python MCP server for Acumatica ERP: 8 generic tools over any tenant's contract-based REST API. Source in src/acumatica_mcp/, packaged with setuptools (pyproject.toml), published as the acumatica plugin's remote backend.

  • Reads credentials
  • Installs packages

The file

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run local: python -m acumatica_mcp (reads .env — see .env.example)

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

acumatica-mcp-server — Claude Code notes

Python MCP server for Acumatica ERP: 8 generic tools over any tenant's contract-based REST API. Source in src/acumatica_mcp/, packaged with setuptools (pyproject.toml), published as the acumatica plugin's remote backend.

Commands (verified 2026-08-15)

  • Syntax gate: every .py edit is byte-compiled automatically (PostToolUse hook).
  • Install dev: pip install -e .
  • Run local: python -m acumatica_mcp (reads .env — see .env.example)

Rules this repo earned

  • Remote vs local: the PRODUCTION server runs remotely (AcumaticaRuviraRemoteMCP scheduled task). Analyzing or editing the local checkout says nothing about what is live — after any deploy, re-list tools from a client and verify the new behavior (a session once analyzed the local server while the remote was the one misbehaving).
  • Auth: tenant credentials live in .env / the remote host's environment. Never print them; never commit .env. Pause and ask for manual auth rather than entering credentials anywhere.
  • Write tools are gated — keep it that way. Any new tool that mutates ERP state needs the same gating/audit treatment as the existing write tools.
  • Version bumps: pyproject.toml version + CHANGELOG.md entry together.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free