Skip to content

Commit e62d286

Browse files
[otel] Update Server docs with OTEL information
1 parent 2c0a763 commit e62d286

4 files changed

Lines changed: 10 additions & 68 deletions

File tree

docs/claude-code-integration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -95,8 +95,8 @@ If you want to use a local version (need to clone and build from this repo):
9595
{
9696
"mcpServers": {
9797
"mapbox-devkit": {
98-
"command": "/path/to/your/node",
99-
"args": ["/path/to/mapbox-mcp-devkit/dist/esm/index.js"],
98+
"command": "node",
99+
"args": ["/absolute/path/to/mapbox-mcp-devkit/dist/esm/index.js"],
100100
"env": {
101101
"MAPBOX_ACCESS_TOKEN": "your_token_here"
102102
}

docs/claude-desktop-integration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -106,8 +106,8 @@ If you want to use a local version (need to clone and build from this repo):
106106
{
107107
"mcpServers": {
108108
"mapbox-devkit": {
109-
"command": "/path/to/your/node",
110-
"args": ["/path/to/mapbox-mcp-devkit/dist/esm/index.js"],
109+
"command": "node",
110+
"args": ["/absolute/path/to/mapbox-mcp-devkit/dist/esm/index.js"],
111111
"env": {
112112
"MAPBOX_ACCESS_TOKEN": "your_token_here"
113113
}

docs/cursor-integration.md

Lines changed: 3 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ docker build -t mapbox-mcp-devkit .
6767
"MapboxDevKit": {
6868
"type": "stdio",
6969
"command": "node",
70-
"args": ["<ABSOLUTE_PATH_TO_REPO>/dist/esm/index.js"],
70+
"args": ["/absolute/path/to/repo/dist/esm/index.js"],
7171
"env": {
7272
"MAPBOX_ACCESS_TOKEN": "<YOUR_TOKEN>"
7373
}
@@ -99,37 +99,8 @@ Additional environment variables you can set:
9999
If the Mapbox DevKit Server doesn't appear in Cursor's MCP tools:
100100

101101
1. Check that your `MAPBOX_ACCESS_TOKEN` is valid
102-
2. Verify `node` and `npx` are in your PATH (run `which node` or `which npx`)
103-
3. For Docker: ensure the image is built with `docker images | grep mapbox-mcp-devkit`
104-
4. Check Cursor's logs for any error messages
105-
106-
### Command Not Found
107-
108-
If you get "command not found" errors for `node` or `npx`:
109-
110-
1. Find the absolute path:
111-
112-
```bash
113-
# Mac/Linux
114-
which node
115-
which npx
116-
117-
# Windows
118-
where node
119-
where npx
120-
```
121-
122-
2. Use the absolute path in your config:
123-
```json
124-
{
125-
"mcpServers": {
126-
"MapboxDevKit": {
127-
"command": "/usr/local/bin/npx", // Use your actual path
128-
...
129-
}
130-
}
131-
}
132-
```
102+
2. For Docker: ensure the image is built with `docker images | grep mapbox-mcp-devkit`
103+
3. Check Cursor's logs for any error messages
133104

134105
### Connection Errors
135106

docs/vscode-integration.md

Lines changed: 3 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ docker build -t mapbox-mcp-devkit .
7373
"type": "stdio",
7474
"command": "node",
7575
"args": [
76-
"<ABSOLUTE_PATH_TO_REPO>/dist/esm/index.js"
76+
"/absolute/path/to/repo/dist/esm/index.js"
7777
],
7878
"env": {
7979
"MAPBOX_ACCESS_TOKEN": "<YOUR_TOKEN>"
@@ -136,9 +136,8 @@ If the Mapbox DevKit Server doesn't appear in VS Code's MCP servers:
136136

137137
1. **Check GitHub Copilot**: Ensure GitHub Copilot is installed and active
138138
2. **Verify token**: Check that your `MAPBOX_ACCESS_TOKEN` is valid
139-
3. **Verify PATH**: Ensure `node` and `npx` are in your PATH (run `which node` or `which npx`)
140-
4. **Docker image**: If using Docker, verify the image exists: `docker images | grep mapbox-mcp-devkit`
141-
5. **Check Output**: Open "Output" panel → Select "MCP" from dropdown to see logs
139+
3. **Docker image**: If using Docker, verify the image exists: `docker images | grep mapbox-mcp-devkit`
140+
4. **Check Output**: Open "Output" panel → Select "MCP" from dropdown to see logs
142141

143142
### Connection Errors / JSON-RPC Parsing Errors
144143

@@ -157,34 +156,6 @@ If tools fail to execute:
157156
3. **Verbose errors**: Add `"VERBOSE_ERRORS": "true"` to the env config for detailed error messages
158157
4. **Network**: Ensure you can reach `api.mapbox.com` from your network
159158

160-
### Command Not Found
161-
162-
If you get "command not found" errors for `node` or `npx`:
163-
164-
1. Find the absolute path:
165-
166-
```bash
167-
# Mac/Linux
168-
which node
169-
which npx
170-
171-
# Windows
172-
where node
173-
where npx
174-
```
175-
176-
2. Use the absolute path in your config:
177-
```json
178-
"mcp": {
179-
"servers": {
180-
"MapboxDevKit": {
181-
"command": "/usr/local/bin/npx", // Use your actual path
182-
...
183-
}
184-
}
185-
}
186-
```
187-
188159
## Example Usage
189160

190161
Once configured, you can use natural language in GitHub Copilot Chat to interact with Mapbox tools:

0 commit comments

Comments
 (0)