feat: add mcpb #17
feat: add mcpb #17
Conversation
WalkthroughAdds a new MCPB release workflow, upgrades GitHub Actions checkout to v5 across CI, introduces MCPB ignore patterns, adds documentation and manifest, replaces JS ESLint config with a TypeScript-based config, expands Prettier and package scripts, and applies non-functional import/formatting changes in source and tests. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor User as Release (published)
participant GH as GitHub Actions
participant Runner as ubuntu-latest
participant Repo as Repository
participant Bun as Bun (oven-sh/setup-bun@v2)
participant MCPB as @anthropic-ai/mcpb
participant Rel as GitHub Release
User->>GH: publish release (event)
GH->>Runner: start job (release-mcpb)
Runner->>Repo: actions/checkout@v5
Runner->>Bun: setup bun (1.2.23)
Runner->>Runner: update version fields (package.json, manifest.json via jq)
Runner->>Bun: bun install --frozen-lockfile
Runner->>Bun: bun run build
Runner->>MCPB: bunx @anthropic-ai/mcpb pack
Runner->>MCPB: bunx @anthropic-ai/mcpb clean mcp.mcpb
Runner->>Rel: upload mcp.mcpb (softprops/action-gh-release@v2)
note right of Rel: Artifact attached to the release
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
🧹 Nitpick comments (6)
src/tools/__tests__/prepareResponse.test.ts (1)
58-77: Avoid double invocation; assert using the captured response.You call handleGeocodeResult twice. Use the response variable for the final equality check to keep tests deterministic and slightly faster.
- const response = handleGeocodeResult(circularResult) + const response = handleGeocodeResult(circularResult) expect(response.content[0]?.type).toBe('text') @@ - expect(handleGeocodeResult(circularResult)).toEqual(expected) + expect(response).toEqual(expected).github/workflows/test.yml (1)
13-13: Pin actions/checkout and setup-bun to specific commit SHAsactions/checkout@v5 (v5.0.0 tag, Aug 11 2025) is officially released; pin both actions to exact commit SHAs to mitigate supply-chain risks.
eslint.config.ts (1)
24-28: Consider enabling @typescript-eslint/no-unused-vars.Disabling
no-unused-varsprevents catching unused variables, parameters, and imports. Consider usingwarninstead ofoff, or configure it to ignore specific patterns if needed.Apply this diff if you want warnings for unused variables:
rules: { '@typescript-eslint/no-explicit-any': 'off', '@typescript-eslint/ban-ts-comment': 'off', - '@typescript-eslint/no-unused-vars': 'off', + '@typescript-eslint/no-unused-vars': 'warn', },manifest.json (1)
5-5: Document the "dev" version placeholder.The version is set to "dev", which suggests it's updated during the release process. Consider adding a comment in the manifest or documenting this in the release workflow documentation.
INSTALLATION.md (2)
51-53: Add language identifiers to fenced code blocks.The usage example code blocks lack language identifiers. Add
textormarkdownto improve rendering consistency.Apply this diff:
-``` +```text Find the coordinates for "Times Square, New York"```diff -``` +```text What address is at coordinates 40.7580, -73.9855?Also applies to: 57-59 --- `129-129`: **Specify the exact MCP SDK version.** Using "Latest" for version information is imprecise and can lead to ambiguity. Specify the actual version number for clarity and reproducibility. Based on learnings, the current stable version is 1.17.5. Apply this diff: ```diff -- **MCP SDK Version**: Latest +- **MCP SDK Version**: 1.17.5
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
bun.lockis excluded by!**/*.lock
📒 Files selected for processing (24)
.github/workflows/lint.yml(1 hunks).github/workflows/release-mcpb.yml(1 hunks).github/workflows/release-npm.yml(3 hunks).github/workflows/test.yml(1 hunks).gitignore(1 hunks).mcpbignore(1 hunks)INSTALLATION.md(1 hunks)MCPB_README.md(1 hunks)eslint.config.js(0 hunks)eslint.config.ts(1 hunks)manifest.json(1 hunks)package.json(1 hunks)prettier.config.ts(1 hunks)src/clients/__tests__/nominatimClient.test.ts(2 hunks)src/clients/nominatimClient.ts(2 hunks)src/index.ts(1 hunks)src/tools/__tests__/geocode.test.ts(6 hunks)src/tools/__tests__/prepareResponse.test.ts(2 hunks)src/tools/__tests__/reverseGeocode.test.ts(7 hunks)src/tools/geocode.ts(1 hunks)src/tools/reverseGeocode.ts(1 hunks)src/types/commonTypes.ts(1 hunks)src/types/geocodeTypes.ts(1 hunks)src/types/reverseGeocodeTypes.ts(1 hunks)
💤 Files with no reviewable changes (1)
- eslint.config.js
🧰 Additional context used
🧬 Code graph analysis (2)
src/tools/__tests__/geocode.test.ts (1)
src/types/geocodeTypes.ts (1)
GeocodeParams(12-12)
src/tools/__tests__/reverseGeocode.test.ts (2)
src/types/reverseGeocodeTypes.ts (1)
ReverseGeocodeParams(12-12)src/tools/prepareResponse.ts (1)
handleGeocodeResult(3-24)
🪛 markdownlint-cli2 (0.18.1)
MCPB_README.md
48-48: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
68-68: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
110-110: Bare URL used
(MD034, no-bare-urls)
123-123: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
INSTALLATION.md
48-48: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
68-68: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
110-110: Bare URL used
(MD034, no-bare-urls)
123-123: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🔇 Additional comments (27)
.gitignore (1)
39-40: LGTM: ignore MCPB artifacts.Good addition; avoids committing built MCPB bundles.
src/tools/__tests__/prepareResponse.test.ts (1)
46-46: LGTM: array literal formatting is fine.src/types/commonTypes.ts (1)
4-4: LGTM: formatting-only change; semantics unchanged.src/types/reverseGeocodeTypes.ts (1)
2-2: LGTM: import order tweak; no behavioral impact.prettier.config.ts (1)
7-19: LGTM! Comprehensive Prettier configuration.The added formatting options establish clear standards and the
prettier-plugin-organize-importsexplains the import reordering changes observed throughout this PR..github/workflows/lint.yml (1)
13-13: LGTM! Standard GitHub Actions upgrade.The upgrade to
actions/checkout@v5aligns with other workflow files in this PR.src/types/geocodeTypes.ts (1)
1-2: LGTM! Import reordering by prettier-plugin-organize-imports.Non-functional change that aligns with the new Prettier configuration.
src/index.ts (1)
5-6: LGTM! Import reordering by prettier-plugin-organize-imports.Non-functional change that aligns with the new Prettier configuration.
src/tools/reverseGeocode.ts (1)
7-7: LGTM! Import reordering by prettier-plugin-organize-imports.Non-functional change that aligns with the new Prettier configuration.
manifest.json (1)
28-34:${__dirname}substitution is supportedThe
${__dirname}placeholder is valid and automatically replaced with the extension’s unpacked directory at launch..github/workflows/release-npm.yml (3)
1-1: LGTM! Workflow name clarification.The workflow name change from "Release" to "Release NPM Package" improves clarity now that there are two release workflows (NPM and MCPB).
17-17: LGTM! Checkout action upgraded to v5.The upgrade to actions/checkout@v5 aligns with best practices and matches the upgrades in other workflows across this PR.
29-29: manifest.json check passed—manifest.json exists and has a version field.src/clients/__tests__/nominatimClient.test.ts (2)
1-1: LGTM! Import reordering improves readability.The reordering of imports from bun:test is a non-functional change that improves code organization.
39-40: LGTM! Assertion condensed without semantic change.The assertion has been condensed from checking multiple parts to checking the main components. The semantic validation remains the same.
src/tools/geocode.ts (1)
3-4: LGTM! Import consolidation and reordering.The consolidation of GeocodeParamsSchema and GeocodeParams into a single import statement and the reordering of McpServer after type imports improve code organization without changing behavior.
src/clients/nominatimClient.ts (2)
2-3: LGTM! Import organization improved.The reordering of type imports and placement of axios import after types follows common TypeScript conventions and improves code organization.
15-15: LGTM! Concise arrow function formatting.The reformatting of condenseOutput to a single-line arrow function is more concise without changing behavior.
package.json (3)
37-37: LGTM! Prettier caching for improved performance.Adding the
--cacheflag to the format script improves performance by caching formatting results.
40-40: LGTM! MCPB CLI script added.The new mcpb script executes @anthropic-ai/mcpb via bunx, aligning with the PR's objective to add MCPB packaging support.
47-49: LGTM! Dev dependencies for enhanced formatting and linting.The additions of eslint-config-prettier and prettier-plugin-organize-imports enhance the development tooling for formatting and linting, aligning with the import reorganization changes throughout this PR.
src/tools/__tests__/reverseGeocode.test.ts (3)
27-27: Mock module path correctly updated.The mock.module path has been updated to match the new relative import path, ensuring the mock is applied correctly.
43-43: LGTM! Formatting refinements.The type annotations and variable declarations have been reformatted to single-line equivalents with no runtime behavior changes. These are minor formatting improvements.
Also applies to: 57-57, 73-75, 93-93, 109-109
3-8: Consistent relative imports for nominatimClient in testsBoth test files now import nominatimClient via
../../clients/nominatimClient.js, andtsconfig.jsonstill defines the"@/*"alias for non-test code..github/workflows/release-mcpb.yml (2)
1-11: LGTM! Well-structured MCPB release workflow.The workflow is properly structured with appropriate permissions (contents: write for uploading, id-token: write for provenance) and triggers on release publication.
16-34: LGTM! Setup and build steps are correct.The workflow correctly:
- Uses actions/checkout@v5 (latest)
- Pins Bun to 1.2.23 (matching package.json)
- Updates versions in both package.json and manifest.json
- Installs dependencies with frozen lockfile for reproducibility
- Builds the project before packaging
src/tools/__tests__/geocode.test.ts (1)
3-5: LGTM! Clean refactoring.The changes are non-functional improvements that enhance code consistency:
- Import ordering aligns with project conventions
- Mock path updates are correct relative to the test file location
- Type annotations are simplified while remaining semantically equivalent
- Changes align with broader test suite refactoring mentioned in the PR summary
Also applies to: 29-29, 32-32, 38-38, 53-53, 71-71, 89-89, 103-103
| - name: Pack MCPB | ||
| run: bunx @anthropic-ai/mcpb pack | ||
|
|
||
| - name: Clean MCPB | ||
| run: bunx @anthropic-ai/mcpb clean mcp.mcpb | ||
|
|
||
| - name: Upload MCPB to GitHub Release | ||
| uses: softprops/action-gh-release@v2 | ||
| with: | ||
| files: mcp.mcpb | ||
| fail_on_unmatched_files: true |
There was a problem hiding this comment.
🧩 Analysis chain
Verify MCPB command syntax and artifact naming.
The MCPB pack, clean, and upload steps look appropriate, but verify:
- The
bunx @anthropic-ai/mcpb clean mcp.mcpbcommand syntax is correct. - The artifact name
mcp.mcpbmatches what's produced by the pack command. - The clean step is necessary (or if pack already produces a clean artifact).
Ask the user to search the web for the latest @anthropic-ai/mcpb CLI documentation:
🌐 Web query:
What are the correct command-line arguments for @anthropic-ai/mcpb pack and clean commands, and what artifact filename does pack produce?
💡 Result:
Short answer:
-
pack: mcpb pack [] []
- If you omit arguments it runs in the current directory and writes a .mcpb archive. It validates the manifest and generates the archive. Examples: npx @anthropic-ai/mcpb pack and npx -y @anthropic-ai/mcpb pack . my-server.mcpb. [1][2]
-
clean: mcpb clean []
- Removes/cleans pack-generated build artifacts for the given directory (runs against the current directory if omitted). Use this to remove temporary files / previously produced bundle artifacts before repacking. [1][2]
-
Artifact filename produced by pack:
- pack produces a .mcpb ZIP archive. If you supply an explicit output filename it uses that (e.g. my-server.mcpb). If you don’t supply one the CLI will write a sensible default (common examples: bundle.mcpb or -.mcpb depending on the project’s metadata). [1][2]
Sources: Anthropic MCPB repo / README and Anthropic engineering docs (pack examples). [1] https://github.com/anthropics/mcpb [2] https://www.anthropic.com/engineering/desktop-extensions
Correct MCPB pack & clean commands
- Pack:
bunx @anthropic-ai/mcpb pack . mcp.mcpbto explicitly generatemcp.mcpb - Clean:
bunx @anthropic-ai/mcpb clean(no file argument) to remove previous build artifacts
🤖 Prompt for AI Agents
.github/workflows/release-mcpb.yml lines 36-46: The workflow uses incorrect mcpb
pack and clean commands; update the Pack step to run the pack command with
explicit output (bunx @anthropic-ai/mcpb pack . mcp.mcpb) so it generates
mcp.mcpb in the workspace, and change the Clean step to run the clean command
without a file arg (bunx @anthropic-ai/mcpb clean) to remove previous build
artifacts before packing.
| *.config.* | ||
| *.md | ||
| **/__tests__/* | ||
|
|
||
| .git* | ||
| .trae | ||
|
|
||
| src | ||
|
|
||
| glama.json | ||
| tsconfig.json |
There was a problem hiding this comment.
🧩 Analysis chain
Review ignore patterns for correctness.
The ignore patterns generally look appropriate for MCPB packaging, excluding source, tests, and config files while keeping the built artifacts.
However, verify that line 6 (.trae) is intentional. This appears to be a typo or an uncommon file pattern.
Run the following script to check if .trae files exist in the repository:
🏁 Script executed:
#!/bin/bash
# Description: Check for .trae files in the repository
# Search for files matching .trae pattern
fd -H -t f '\.trae$'
# Also check if this might be a typo for .trace
echo "Checking for .trace files:"
fd -H -t f '\.trace$'Length of output: 26
Remove or correct .trae in .mcpbignore
No files match .trae; if you meant to ignore .trace, update or remove this entry (line 6).
🤖 Prompt for AI Agents
In .mcpbignore around lines 1 to 11, the entry ".trae" on line 6 is a typo and
matches no files; either remove that line or correct it to the intended pattern
(for example ".trace" or "*.trace") so the ignore file actually excludes the
desired files; update the entry accordingly and save the file.
|
|
||
| For issues or questions: | ||
| 1. Check the troubleshooting section above | ||
| 2. Review the DXT_README.md for detailed documentation |
There was a problem hiding this comment.
🧩 Analysis chain
Verify the referenced file exists.
The documentation references DXT_README.md, but it's unclear if this file exists in the repository.
Run the following script to check if the file exists:
🏁 Script executed:
#!/bin/bash
# Check if DXT_README.md exists in the repository
fd -t f "DXT_README.md"Length of output: 0
Locate any matching README file
Run the following to confirm whether a DXT_README.md (or similarly named) file exists:
🏁 Script executed:
#!/bin/bash
# Find any Markdown file with “dxt” and “readme” in its name (case-insensitive)
find . -type f -iname "*dxt*readme*.md"
# Search for references to “DXT_README” in the repository
rg -n "DXT_README"Length of output: 74
Broken link to DXT_README.md
The file DXT_README.md referenced in INSTALLATION.md:112 doesn’t exist—update the link to the correct documentation file or add the missing README.
🤖 Prompt for AI Agents
In INSTALLATION.md around line 112, the referenced file "DXT_README.md" is
missing; update the link or add the file. Replace the broken reference with the
correct documentation filename/path (e.g., the actual README present in the repo
such as "DXT/README.md" or "docs/DXT_README.md"), or add the missing
DXT_README.md to the repository; ensure the link text and relative path are
valid so the reference resolves correctly.
MCPB_README.md
Outdated
| - Claude Desktop (version 1.0.0 or higher) | ||
| - Node.js runtime (version 16.0.0 or higher) |
There was a problem hiding this comment.
Version requirements mismatch with manifest.json.
The README states Node.js 16.0.0+ and Claude Desktop 1.0.0+, but manifest.json requires Node.js 18.0.0+ (line 54) and Claude Desktop 0.11.0+ (line 47). Align these version requirements.
Apply this diff to match the manifest requirements:
-- Claude Desktop (version 1.0.0 or higher)
-- Node.js runtime (version 16.0.0 or higher)
+- Claude Desktop (version 0.11.0 or higher)
+- Node.js runtime (version 18.0.0 or higher)Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In MCPB_README.md around lines 18 to 19, update the version requirements to
match manifest.json by changing the Claude Desktop requirement to 0.11.0 or
higher and the Node.js runtime requirement to 18.0.0 or higher; edit those two
bullet lines so they exactly read "Claude Desktop (version 0.11.0 or higher)"
and "Node.js runtime (version 18.0.0 or higher)" to keep docs and manifest
consistent.
MCPB_README.md
Outdated
| ``` | ||
| Geocode "1600 Amphitheatre Parkway, Mountain View, CA" | ||
| ``` |
There was a problem hiding this comment.
Add language specifiers to fenced code blocks.
Based on static analysis feedback, add language identifiers to improve Markdown rendering and tooling support.
Apply these diffs:
-**Example Usage:**
-```
-Geocode "1600 Amphitheatre Parkway, Mountain View, CA"
-```
+**Example Usage:**
+```text
+Geocode "1600 Amphitheatre Parkway, Mountain View, CA"
+```-**Example Usage:**
-```
-Reverse geocode coordinates 37.4224764, -122.0842499
-```
+**Example Usage:**
+```text
+Reverse geocode coordinates 37.4224764, -122.0842499
+```-### Project Structure
-
-```
-├── manifest.json # MCPB extension manifest
+### Project Structure
+
+```text
+├── manifest.json # MCPB extension manifestAlso applies to: 68-70, 123-132
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
48-48: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
In MCPB_README.md around lines 48-50 (also apply same changes at 68-70 and
123-132), fenced code blocks lack language specifiers and some headings/context
are missing; update the README by adding a brief heading like "Example Usage:"
before those examples, add a language identifier (use "text") to each fenced
code block, and replace the solitary file tree line with a small "Project
Structure" heading followed by a fenced "text" block containing the tree line so
all three locations have proper headings and fenced blocks with language
specifiers.
| This extension uses the OpenStreetMap Nominatim API: | ||
| - **Data**: © OpenStreetMap contributors | ||
| - **License**: ODbL 1.0 | ||
| - **Copyright**: http://osm.org/copyright |
There was a problem hiding this comment.
Use proper Markdown link syntax for the bare URL.
Based on static analysis feedback, wrap the URL in angle brackets or use proper link syntax.
Apply this diff:
-- **Copyright**: http://osm.org/copyright
+- **Copyright**: <http://osm.org/copyright>📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - **Copyright**: http://osm.org/copyright | |
| - **Copyright**: <http://osm.org/copyright> |
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
110-110: Bare URL used
(MD034, no-bare-urls)
🤖 Prompt for AI Agents
In MCPB_README.md around line 110, the copyright line uses a bare URL which
triggers static analysis; replace it with proper Markdown link syntax by either
wrapping the URL in angle brackets like <http://osm.org/copyright> or using full
link format [http://osm.org/copyright](http://osm.org/copyright) so the URL is
recognized and rendered correctly.
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (3)
MCPB_README.md (3)
123-132: Add language identifier to fenced block (MD040).Use text for the tree listing.
-``` +```text ├── manifest.json # MCPB extension manifest ├── dist/ # Compiled JavaScript files │ ├── index.js # Main entry point │ ├── tools/ # MCP tool implementations │ ├── clients/ # API client code │ └── types/ # TypeScript type definitions ├── src/ # Source TypeScript files └── mcp.mcpb # Generated MCPB extension file -``` +```
18-19: Align README version requirements with manifest (Claude Desktop).Manifest requires Claude Desktop 0.11.0+. Update README accordingly. Node is already 18+ here.
- - Claude Desktop (version 1.0.0 or higher) + - Claude Desktop (version 0.11.0 or higher)
110-110: Replace bare URL to satisfy markdownlint (MD034).-- **Copyright**: http://osm.org/copyright +- **Copyright**: <http://osm.org/copyright>
🧹 Nitpick comments (3)
MCPB_README.md (3)
59-61: Verify nonstandard parameters (“layer”, “featureType”).Nominatim doesn’t expose layer/featureType params in its public API. If these are extension-level options mapped to Nominatim queries, clarify in README; otherwise remove/rename.
Also applies to: 80-81
16-21: Add Bun to prerequisites (used throughout dev/build/test commands).Readers need Bun installed to run the documented commands.
### Prerequisites @@ - Claude Desktop (version 0.11.0 or higher) - Node.js runtime (version 18.0.0 or higher) +- Bun runtime (version 1.x or higher) - Compatible with macOS, Windows, and Linux
9-10: Normalize casing for GeocodeJSON.Use consistent lowercase (geocodejson) everywhere to match parameter examples.
-- **Multiple Output Formats**: Support for JSON, GeoJSON, and GeocodeJSON formats +- **Multiple Output Formats**: Support for JSON, GeoJSON, and geocodejson formatsAlso applies to: 99-103
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
bun.lockis excluded by!**/*.lock
📒 Files selected for processing (4)
INSTALLATION.md(1 hunks)MCPB_README.md(1 hunks)eslint.config.ts(1 hunks)package.json(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- INSTALLATION.md
🚧 Files skipped from review as they are similar to previous changes (2)
- package.json
- eslint.config.ts
🧰 Additional context used
🪛 markdownlint-cli2 (0.18.1)
MCPB_README.md
110-110: Bare URL used
(MD034, no-bare-urls)
123-123: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
| 1. **Extension not loading**: Ensure Claude Desktop version is 1.0.0 or higher | ||
| 2. **Node.js errors**: Verify Node.js version 16.0.0 or higher is installed | ||
| 3. **API errors**: Check internet connection and Nominatim service availability |
There was a problem hiding this comment.
Fix contradictory versions in Troubleshooting.
These should match manifest and Prerequisites (Claude Desktop ≥0.11.0, Node.js ≥18).
-1. **Extension not loading**: Ensure Claude Desktop version is 1.0.0 or higher
-2. **Node.js errors**: Verify Node.js version 16.0.0 or higher is installed
+1. **Extension not loading**: Ensure Claude Desktop version is 0.11.0 or higher
+2. **Node.js errors**: Verify Node.js version 18.0.0 or higher is installed📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| 1. **Extension not loading**: Ensure Claude Desktop version is 1.0.0 or higher | |
| 2. **Node.js errors**: Verify Node.js version 16.0.0 or higher is installed | |
| 3. **API errors**: Check internet connection and Nominatim service availability | |
| 1. **Extension not loading**: Ensure Claude Desktop version is 0.11.0 or higher | |
| 2. **Node.js errors**: Verify Node.js version 18.0.0 or higher is installed | |
| 3. **API errors**: Check internet connection and Nominatim service availability |
🤖 Prompt for AI Agents
In MCPB_README.md around lines 150 to 152, the troubleshooting version numbers
contradict the manifest/prerequisites; update the listed minimums so they match:
change "Claude Desktop version is 1.0.0 or higher" to "Claude Desktop ≥0.11.0"
and change "Node.js version 16.0.0 or higher" to "Node.js ≥18", and verify the
wording/formatting aligns with the rest of the README.
Summary by CodeRabbit