My First Mcp Server

Created By
Raj-ML16a year ago
Overview

what is My First MCP Server?

My First MCP Server is a project designed to help users set up a management control panel (MCP) server using Python.

how to use My First MCP Server?

To use My First MCP Server, follow these steps:

  1. Go to your desired project folder.
  2. Initialize the project using (uv init my-first-mcp-server).
  3. Move into the new project folder (cd my-first-mcp-server).
  4. Create and activate a virtual environment (if not already done) [python -m venv .venv & then .venv\Scripts\Activate.ps1].
  5. Install MCP CLI inside this project using uv add "mcp[cli]".
  6. pip install --upgrade typer.
  7. Add your main.py leave management code.
  8. Install your server using (uv run mcp install main.py). Finally, Restart Claude Desktop if needed.

key features of My First MCP Server?

  • Easy setup for a management control panel server.
  • Utilizes Python for server management.
  • Supports virtual environments for project isolation.

use cases of My First MCP Server?

  1. Setting up a leave management system for organizations.
  2. Developing custom management tools using Python.
  3. Learning server management and Python development.

FAQ from My First MCP Server?

  • What is MCP?

MCP stands for Management Control Panel, a tool for managing various aspects of a project or organization.

  • Is this project suitable for beginners?

Yes! This project is designed to be beginner-friendly, with clear steps to follow.

  • Can I customize the server?

Absolutely! You can modify the main.py file to suit your specific management needs.

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

2 days ago