MCP Server Project (Proof of Concept)

Created By
BayernTourismusa year ago
A Proof of Concept for a MCP Server that lets LLM connect with BayernCloud Tourismus
Overview

what is MCP Server?

MCP Server is a Proof of Concept project that enables large language models to connect with location-based services, specifically focusing on tourism data from the BayernCloud API and geocoding services from OpenStreetMap.

how to use MCP Server?

To use the MCP Server, clone the repository, install the necessary dependencies, and set up your environment variables with the required API keys. You can then integrate it with AI assistants like Claude to access location-based services.

key features of MCP Server?

  • Provides geocoding and location services through Nominatim MCP Server.
  • Access to tourism events data via BayernCloud Tourism MCP Server.
  • Integration capabilities with large language models for enhanced functionality.

use cases of MCP Server?

  1. Retrieving tourism events near a specific location.
  2. Integrating location services into AI applications.
  3. Enhancing user experience in travel-related applications.

FAQ from MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol that allows large language models to interact with external tools and data sources.

  • Do I need an API key to use the BayernCloud Tourism MCP Server?

Yes, you need to obtain an API key from the BayernCloud website to access tourism event data.

  • Is the MCP Server open-source?

Yes, the MCP Server is available on GitHub and is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
BayernTourismus
Star
1
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago