AX Module Studio MCP Server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
AX Module Studio MCP Server
Single Python MCP runtime for the shared AX Module Studio tool boundary. The
service exposes one Streamable HTTP endpoint at /mcp and registers both the
approved Coding and Natural CMS tool catalogs in PRODUCTION_TOOL_NAMES.
Runtime boundary
Spring Backend is the only platform client and owns authorization, job state, profile/version binding, and Core persistence.
This repository owns the MCP transport, service-token authentication, fixed tool-name catalog, health endpoints, tests, and image.
The service has no PostgreSQL, Valkey, checkpoint, or Core database dependency.
/health/liveand/health/readyare public container health endpoints./mcprequiresAuthorization: Bearer <service-token>.Coding tools accept an opaque direct-child workspace key beneath
AXMS_MCP_WORKSPACE_ROOT(default/workspaces). Absolute paths, linked paths, authentication/security code, secrets, Git metadata, and Flyway/migration paths are denied.The service does not clone or create workspaces. Production must mount pre-provisioned direct-child Git workspaces with read/write access for UID
10001; that provisioning path remains outside AI04-002.Fixed Git operations use only the startup-validated absolute
AXMS_MCP_GIT_EXECUTABLE(default/usr/bin/git); tool input cannot select an executable or command.apply_patchis serialized per workspace and fully validated against a temporary Git index before mutation. Each patch is limited to 500 unique paths and may change only stage-zero regular100644files.run_checkaccepts onlygit-diff-checkand the import-freepython-syntaxAST profile. It never accepts a command, argument list, environment, or shell fragment.
Related MCP server: yourco-mcp
Local verification
Python 3.12.13 and uv 0.8.13 are the repository baseline.
uv sync --frozen
uv run python -m unittest discover -s tests -v
uv run python -m compileall -q src tests
docker build -t axms/mcp-server:dev .Run the server only with a token file; do not put token values on the command line or in logs.
$env:AXMS_MCP_SERVICE_TOKEN_FILE = 'C:\path\to\mcp_service_token'
uv run python -m axms_mcp_server.serviceDefault port: 8091.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
An MCP server that provides Javelin Standalone Guardrails
One OAuth connector for your team's remote MCP servers, with Tool Packs, guardrails and logs.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA universal MCP server for registering internal, external, and OpenAPI-based APIs as MCP tools. It exposes them to MCP clients via Streamable HTTP and provides admin portal, RBAC/session auth, credential injection, and audit logging.-
- FlicenseNot gradedqualityBmaintenanceEnables developers to build MCP servers with registry-managed tool metadata, runtime hot-reloading, pluggable authentication and authorization, per-audience tool views, and resilient stateless operation.-
- FlicenseNot gradedqualityCmaintenanceProvides a production-oriented MCP server exposing tools, resources, and prompts over Streamable HTTP with JWT authentication and per-tool RBAC, enabling Amazon Bedrock Claude clients to securely invoke MCP capabilities.-
- AlicenseNot gradedqualityCmaintenanceIt enables developers to run a Streamable HTTP MCP endpoint with example tools, a README resource, and a REST API route as a customizable foundation for MCP server projects.MIT