mcp-zenskar 1.0.5 → 1.0.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +30 -1
- package/package.json +2 -2
- package/src/mcp-config.json +224 -2532
- package/src/server.js +137 -16
package/README.md
CHANGED
|
@@ -32,6 +32,8 @@ Add to your Claude Desktop configuration (`~/Library/Application Support/Claude/
|
|
|
32
32
|
}
|
|
33
33
|
```
|
|
34
34
|
|
|
35
|
+
> You can omit one or both environment variables from the config, but the server will error until Claude supplies them in a tool call. Keeping them in the env block prevents repeated credential prompts.
|
|
36
|
+
|
|
35
37
|
### For Other AI Applications
|
|
36
38
|
|
|
37
39
|
Install globally:
|
|
@@ -56,6 +58,8 @@ This MCP server requires two authentication parameters for every request:
|
|
|
56
58
|
1. **Organization ID**: Available in your Zenskar dashboard settings
|
|
57
59
|
2. **API Token**: Generate from Zenskar dashboard → Settings → API Keys
|
|
58
60
|
|
|
61
|
+
At runtime the server looks for these values in the tool invocation first, then falls back to the `ZENSKAR_ORGANIZATION` and `ZENSKAR_AUTH_TOKEN` environment variables. Tokens that look like JWTs are sent as `Authorization: Bearer ...`; everything else is sent as an `x-api-key` header automatically.
|
|
62
|
+
|
|
59
63
|
## Usage
|
|
60
64
|
|
|
61
65
|
### In Claude Desktop
|
|
@@ -114,6 +118,31 @@ npm install
|
|
|
114
118
|
npm start
|
|
115
119
|
```
|
|
116
120
|
|
|
121
|
+
### Developing Locally Without Publishing
|
|
122
|
+
|
|
123
|
+
If you want Claude Desktop to use a local checkout instead of the npm package:
|
|
124
|
+
|
|
125
|
+
```bash
|
|
126
|
+
# Install dependencies once
|
|
127
|
+
npm install
|
|
128
|
+
|
|
129
|
+
# Optional: install the local build globally
|
|
130
|
+
npm install -g .
|
|
131
|
+
```
|
|
132
|
+
|
|
133
|
+
Then either point Claude to the globally-installed binary (usually `$(npm bin -g)/mcp-zenskar`) or call the repo copy directly:
|
|
134
|
+
|
|
135
|
+
```json
|
|
136
|
+
{
|
|
137
|
+
"command": "node",
|
|
138
|
+
"args": ["/absolute/path/to/mcp-zenskar/src/server.js"],
|
|
139
|
+
"env": {
|
|
140
|
+
"ZENSKAR_ORGANIZATION": "your-org-id",
|
|
141
|
+
"ZENSKAR_AUTH_TOKEN": "your-token"
|
|
142
|
+
}
|
|
143
|
+
}
|
|
144
|
+
```
|
|
145
|
+
|
|
117
146
|
## Configuration
|
|
118
147
|
|
|
119
148
|
The server uses `src/mcp-config.json` to define available tools and API endpoints. This file contains the complete mapping of MCP tools to Zenskar API operations.
|
|
@@ -126,4 +155,4 @@ MIT
|
|
|
126
155
|
|
|
127
156
|
For issues and support:
|
|
128
157
|
- GitHub Issues: https://github.com/zenskar/mcp-zenskar/issues
|
|
129
|
-
- Zenskar Documentation: https://docs.zenskar.com
|
|
158
|
+
- Zenskar Documentation: https://docs.zenskar.com
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "mcp-zenskar",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.8",
|
|
4
4
|
"description": "Model Context Protocol (MCP) server for Zenskar API - customer management, invoicing, and billing operations",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "src/server.js",
|
|
@@ -39,4 +39,4 @@
|
|
|
39
39
|
"url": "https://github.com/zenskar/mcp-zenskar/issues"
|
|
40
40
|
},
|
|
41
41
|
"homepage": "https://github.com/zenskar/mcp-zenskar#readme"
|
|
42
|
-
}
|
|
42
|
+
}
|