🧳 MCP Travel Desk — A Minimal MCP Client & Server Demo

Created By
ChaitanyaK77a year ago
This project demonstrates how to build a minimal MCP server using the `mcp` Python SDK and connect it to Claude Desktop as a client. It simulates a simple Travel Desk system with tools to submit, view, and track employee travel requests — all accessible directly from Claude's interface.
Overview

What is MCP Travel Desk?

MCP Travel Desk is a minimal demonstration project that showcases how to build an MCP server using the mcp Python SDK and connect it to Claude Desktop as a client. It simulates a Travel Desk system for managing employee travel requests, approvals, and tracking.

How to use MCP Travel Desk?

To use MCP Travel Desk, follow these steps:

  1. Install Claude Desktop from Anthropic.
  2. Install the MCP Python SDK and uv package.
  3. Initialize the MCP server and create a main.py file.
  4. Install the server into Claude and ensure it is running.
  5. Use Claude to submit travel requests and track history.

Key features of MCP Travel Desk?

  • Integration with Claude Desktop as an MCP client.
  • Tools for submitting and tracking employee travel requests.
  • User-friendly interface for managing travel approvals and history.

Use cases of MCP Travel Desk?

  1. Submitting travel requests for employees.
  2. Tracking the history of travel requests and approvals.
  3. Managing travel data directly from Claude's interface.

FAQ from MCP Travel Desk?

  • What is required to run MCP Travel Desk?

You need Claude Desktop and the MCP Python SDK installed.

  • Can I customize the travel request tools?

Yes, you can modify the main.py file to customize the tools available in Claude.

  • Is there any troubleshooting for macOS users?

Yes, if the server doesn't start, ensure you have installed the uv package and check the Claude Developer Settings.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ChaitanyaK77
Star
0
Language
Python
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
Crevio

2 days ago