mcp-servicenex-v2
A Model Context Protocol (MCP) server for the ServiceNEX REST API. It exposes tickets, knowledge articles, services, users, and MCP resources to AI clients such as Claude Desktop.
Install
Requires Python 3.10+.
pip install mcp-servicenex-v2
Set credentials, then start the stdio server:
export SERVICENEX_API_BASE="https://your-tenant.servicenex.io"
export SERVICENEX_API_KEY="your-api-key"
mcp-servicenex-v2
Or with uvx (no global install):
uvx mcp-servicenex-v2
You can also run the module directly:
python -m mcp_servicenex_v2
Copy .env.example to .env for local development. Host environment
variables still take precedence.
Claude Desktop
{
"mcpServers": {
"servicenex": {
"command": "uvx",
"args": ["mcp-servicenex-v2"],
"env": {
"SERVICENEX_API_BASE": "https://your-tenant.servicenex.io",
"SERVICENEX_API_KEY": "your-api-key"
}
}
}
}
If installed with pip, use "command": "mcp-servicenex-v2" and omit args.
Environment
| Variable | Required | Description |
|---|---|---|
SERVICENEX_API_BASE |
Yes | ServiceNEX base URL (no trailing slash required) |
SERVICENEX_API_KEY |
Yes | Tenant API key (X-API-Key) |
SERVICENEX_API_TIMEOUT |
No | HTTP timeout in seconds (default 120) |
LOG_LEVEL |
No | Logging level (default INFO) |
TWINE_USERNAME |
Publish | Always __token__ for API tokens |
TEST_PYPI_TOKEN |
Publish to TestPyPI | Token from test.pypi.org |
PYPI_TOKEN |
Publish to PyPI | Token from pypi.org |
Publish
Tokens are read from the repo-root .env (never committed). Copy the publish
keys from .env.example if they are missing.
./scripts/package.sh
./scripts/publish.sh testpypi
./scripts/publish.sh pypi
publish.sh pypi asks you to type the package name unless you pass --yes.
Build tools are installed into .venv-build/ so the runtime .venv is unchanged.
License
MIT
Metadata
Release files for mcp-servicenex-v2 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mcp_servicenex_v2-0.3.0.tar.gz | 28.6 kB | Without provenance | Details for mcp_servicenex_v2-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_servicenex_v2-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for mcp_servicenex_v2-0.3.0-py3-none-any.whl |
Total release size: 59.6 kB
Release files / mcp_servicenex_v2-0.3.0.tar.gz
| Download URL | mcp_servicenex_v2-0.3.0.tar.gz |
|---|---|
| Size | 28.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd7897e81d8b1adbfc88cc9d28bdd04794ab4756d486703f186e966d7555b229
|
|
BLAKE2b-256 checksum How to use checksums |
e3d8a83e0e2dcf1a7b967b501da1ae9f104d0b942147afc6a9b826e4b5d926f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / mcp_servicenex_v2-0.3.0-py3-none-any.whl
| Download URL | mcp_servicenex_v2-0.3.0-py3-none-any.whl |
|---|---|
| Size | 31.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9c1d41804392d8adc40d76fd2f3a0600d0ee533204c89eee397be1b1fba2633d
|
|
BLAKE2b-256 checksum How to use checksums |
9333cb4d10296816031b556a60eb111889b98295cad87ec9ca1ae4ff98b41948
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for mcp-servicenex-v2 0.3.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.