resolve-nvs-mcp
Resolve AI Copilot MCP server. Connects Claude (and any MCP-compatible client) to the Resolve support platform over stdio — no repo clone, no database required.
Requirements
uvinstalled (foruvx)- A Resolve API token (issue one at Settings → API Keys inside Resolve)
Add to Claude Desktop / Claude Code
claude mcp add resolve \
-e RESOLVE_API_TOKEN=rsv_... \
-e RESOLVE_API_URL=https://api.resolve.nvs.team \
-- uvx resolve-nvs-mcp
Replace rsv_... with your actual token. RESOLVE_API_URL is optional and defaults to https://api.resolve.nvs.team.
Local development
Point the server at a locally running API instance:
RESOLVE_API_TOKEN=rsv_... RESOLVE_API_URL=http://localhost:8080 uvx resolve-nvs-mcp
Environment variables
| Variable | Required | Default | Description |
|---|---|---|---|
RESOLVE_API_TOKEN |
Yes | — | Plaintext API token (rsv_... prefix). Issue at /settings/api-keys. |
RESOLVE_API_URL |
No | https://api.resolve.nvs.team |
Base URL for the Resolve API. Use http://localhost:8080 for local dev. |
How it works
On startup the server fetches the available tool list from the API (GET /api/v1/mcp/tools), validates your token, and then serves those tools over the MCP stdio protocol. Every tool call is forwarded to the API (POST /api/v1/mcp/tools/{name}) — no local state or database access is involved.
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for resolve-nvs-mcp 0.2.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 | |
|---|---|---|---|---|
| resolve_nvs_mcp-0.2.0.tar.gz | 59.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| resolve_nvs_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 63.6 kB
Release files / resolve_nvs_mcp-0.2.0.tar.gz
| Download URL | resolve_nvs_mcp-0.2.0.tar.gz |
|---|---|
| Size | 59.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bc5ea48d2c137332757a587b5d9ca6f5daa374be2c813bfd67259131c70e4485
|
|
BLAKE2b-256 checksum How to use checksums |
e2c15b52f76132afec89d8eba7346465b3bf1ce8774d6ba69becc34de118a644
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / resolve_nvs_mcp-0.2.0-py3-none-any.whl
| Download URL | resolve_nvs_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 4.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f61b5ee53add3856e3cff6ec0621fd5985144808715f27e09925894e2e6527b0
|
|
BLAKE2b-256 checksum How to use checksums |
ec49439b6517805407daa5e61753cb033b55a16a3bc4da17946febc174ed1676
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for resolve-nvs-mcp 0.2.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.
