rigosis-smax-mcp
MCP server for OpenText SMAX: work with EMS records (Incidents, Requests,
Changes, People, Devices, custom types), comments, and attachments from any
MCP client. Fifteen generic tools including live schema discovery
(describe_entity, list_entity_types) and warn-first write validation.
rigosis-smax-mcp is developed and licensed by Rigosis for integration with OpenText™ Service Management software, formerly known as SMAX. It is not an OpenText product.
Requirements
- uv (provides
uvx; installs its own Python) - A SMAX user with the "Access OData API" role and a Personal Access Token (Service Portal → Personal Access Tokens), or username/password.
Quick setup (recommended)
uvx --from rigosis-smax-mcp smax-mcp-setup
An interactive wizard: asks for your connection details, tests them live against your tenant, writes the Claude Desktop config for you (backing up any existing file), and prints ready-to-paste snippets for every other MCP client. If it ends with a green checkmark, you're done — the sections below are the manual alternative.
Verify your setup first
uvx --from rigosis-smax-mcp smax-mcp-verify
This checks configuration and authenticates against your tenant before you
wire up any client. It reads the environment variables below (a .env file
found from the working directory upward also works).
Configuration
| Variable | Meaning |
|---|---|
SMAX_MCP_BASE_URL |
e.g. https://smax.example.com (required) |
SMAX_MCP_TENANT_ID |
numeric tenant id (required) |
SMAX_MCP_USERNAME |
Service Portal login (required) |
SMAX_MCP_PAT |
Personal Access Token — recommended; paired with the username that created it |
SMAX_MCP_PASSWORD |
alternative to PAT: password auth (JWT fetched automatically) |
SMAX_MCP_VERIFY_SSL |
default true |
SMAX_MCP_CA_BUNDLE |
CA bundle path for private CAs |
SMAX_MCP_READ_ONLY |
true registers only read tools (default false) |
SMAX_MCP_ATTACHMENTS_DIR |
sandbox directory for attachment upload/download (required for attachment tools) |
SMAX_MCP_MAX_ATTACHMENT_MB |
default 10 |
SMAX_MCP_SKIP_SCHEMA_CHECK |
true disables the warn-only pre-write schema check |
Use a least-privilege SMAX integration account — every tool acts as that one configured user.
Connect an MCP client
The server speaks MCP over stdio. Generic client configuration:
- command:
uvx - args:
["--from", "rigosis-smax-mcp", "smax-mcp"] - environment: the variables above
Claude Code:
claude mcp add smax \
--env SMAX_MCP_BASE_URL=https://smax.example.com \
--env SMAX_MCP_TENANT_ID=123456789 \
--env SMAX_MCP_USERNAME=integration.user \
--env SMAX_MCP_PAT=your-token \
--env SMAX_MCP_ATTACHMENTS_DIR=/path/to/attachments \
-- uvx --from rigosis-smax-mcp smax-mcp
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"smax": {
"command": "uvx",
"args": ["--from", "rigosis-smax-mcp", "smax-mcp"],
"env": {
"SMAX_MCP_BASE_URL": "https://smax.example.com",
"SMAX_MCP_TENANT_ID": "123456789",
"SMAX_MCP_USERNAME": "integration.user",
"SMAX_MCP_PAT": "your-token",
"SMAX_MCP_ATTACHMENTS_DIR": "C:\\smax-attachments"
}
}
}
}
Windows note: SMAX_MCP_ATTACHMENTS_DIR takes a normal Windows path; create
the directory before first use.
In a session, call whoami first as a connectivity smoke test.
Support
Contact your Rigosis representative. Use of this software is governed by the LICENSE file and your agreement with Rigosis Information Systems.
1 maintainer
Release files for rigosis-smax-mcp 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| rigosis_smax_mcp-0.3.2.tar.gz | 25.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rigosis_smax_mcp-0.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 53.8 kB
Release files / rigosis_smax_mcp-0.3.2.tar.gz
| Download URL | rigosis_smax_mcp-0.3.2.tar.gz |
|---|---|
| Size | 25.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a5629e0be7e5e00d9b4c5a5b0b0d1084413d3c2f076e95ddda30fa9575d6d5ee
|
|
BLAKE2b-256 checksum How to use checksums |
7b523ae90af91e2b889c60a99dc3080b76611cdae73b3f90b82162f083e2460a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.
Transparency logRelease files / rigosis_smax_mcp-0.3.2-py3-none-any.whl
| Download URL | rigosis_smax_mcp-0.3.2-py3-none-any.whl |
|---|---|
| Size | 28.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a17f0a56cedf143ac1516c9a58b52c95fc662503a2749fdee56b5680ef616ecc
|
|
BLAKE2b-256 checksum How to use checksums |
e884248da6b8675e68de3d0c800cc4260533f0969449d8ed6a686630292cb203
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.
Transparency log
