Metadata-Version: 2.4
Name: resolve-nvs-mcp
Version: 0.2.0
Summary: Resolve AI Copilot MCP server — connects Claude (and other MCP clients) to the Resolve API over stdio.
Author-email: Resolve <team@jobescape.me>
License: MIT
Requires-Python: >=3.10
Requires-Dist: anyio>=4.0
Requires-Dist: httpx>=0.27
Requires-Dist: mcp>=1.27.2
Description-Content-Type: text/markdown

# resolve-nvs-mcp

Resolve AI Copilot MCP server. Connects Claude (and any MCP-compatible client) to the [Resolve](https://resolve.nvs.team) support platform over stdio — no repo clone, no database required.

## Requirements

- [`uv`](https://docs.astral.sh/uv/) installed (for `uvx`)
- A Resolve API token (issue one at **Settings → API Keys** inside Resolve)

## Add to Claude Desktop / Claude Code

```bash
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:

```bash
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
