Multi Context Protocol (MCP) Server

Created By
prakashsankera year ago
Overview

what is Multi Context Protocol (MCP) Server?

The Multi Context Protocol (MCP) Server is a travel planning tool that allows users to ask complex travel-related questions and receive tailored responses, such as flight and hotel recommendations.

how to use MCP Server?

To use the MCP Server, you can either integrate it with Claude Desktop or use it programmatically by setting up the necessary API keys and configurations as outlined in the documentation.

key features of MCP Server?

  • Search for available flights between two airports using Booking.com's API.
  • Provide current date context for travel planning.
  • Search for hotels and accommodations.
  • Future features include car rental searches, hotel reviews, and taxi services.

use cases of MCP Server?

  1. Finding the latest flights to a specific destination.
  2. Recommending hotels near popular tourist attractions.
  3. Planning comprehensive travel itineraries that include flights, hotels, and transportation options.

FAQ from MCP Server?

  • What APIs do I need to use MCP Server?

You need a Booking.com API key and a Google Maps API key to use the server effectively.

  • Can I use MCP Server programmatically?

Yes! The MCP Server can be integrated into your applications using the provided code snippets.

  • What kind of travel questions can I ask?

You can ask about flights, hotels, car rentals, and more, tailored to your specific needs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
prakashsanker
Star
0
Language
JavaScript
License
-
Tags

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