This MCP server package provides two concepts under a single repository: a Nominatim-based MCP server for geocoding and location lookup, and a BayernCloud Tourism MCP server for retrieving tourism events data near a location within a date range. The MCP framework lets large language models like Claude interact with these tools through standardized MCP commands and tools. You can integrate the servers into your assistant environment and expose tools such as geocoding (forward/reverse lookup) and list_events for nearby events. The example integration shows how to configure two Node.js-based MCP servers in Claude or similar environments, each mapped to a separate server instance. Use these tools by pointing your client to the appropriate server entry (e.g., nominatim for geocoding, bayerncloud for tourism data) and invoking the provided actions in natural language prompts that reference those tools.

Prerequisites:

• Node.js (v14 or newer) installed on your system
• npm (comes with Node.js) or pnpm/yarn if you prefer
• API credentials for BayernCloud Tourism API (BCT) if you plan to use the events server

Installation steps:

1. Clone the repository git clone <repository-url> cd <repository-directory>

2. Install dependencies npm install

3. Create a .env file in the root directory (optional if you prefer environment variables in your shell/session): BCT_API_TOKEN=your_bayern_cloud_api_token NOMINATIM_BASE_URL=https://nominatim.openstreetmap.org OSRM_BASE_URL=http://router.project-osrm.org BAYERN_CLOUD_API_URL=https://data.bayerncloud.digital/api/v4/endpoints

4. Run the MCP servers locally (examples):

   Start Nominatim MCP server

   node /path/to/your/mcp-server/src/nominatim.js

   Start BayernCloud Tourism MCP server

   node /path/to/your/mcp-server/src/bayerncloud.js

Note: Adjust the paths to point to the actual locations of nominatim.js and bayerncloud.js in your environment. You can also containerize these servers or use a process manager as appropriate.

Tips:

• Ensure environment variables are loaded before starting the servers. If you’re using a .env file, consider tools like direnv or dotenv-safe to enforce required variables.
• If a server fails to start due to missing dependencies, run npm install in the project root and verify Node.js compatibility.
• When using BayernCloud data, ensure your API token is valid and has the necessary permissions for the endpoints you query.
• For Claude or other LLM integrations, follow the quickstart docs at modelcontextprotocol.io to wire up the integration with the provided JSON structure. Use the example in the README as a template for your own environment.
• If you run into CORS or network issues, verify that the host allows outbound connections to NOMINATIM_BASE_URL, OSRM_BASE_URL, and BAYERN_CLOUD_API_URL, and that any firewalls or proxies are configured accordingly.