Beginner's Guide to MCP Servers

Created By
astensbya year ago
Overview

What is Gritai Basic MCP Server?

Gritai Basic MCP Server is a beginner-friendly project designed to help users understand and build Model Context Protocol (MCP) servers with minimal coding experience. It serves as a bridge for AI assistants to connect to external tools and data sources.

How to Use Gritai Basic MCP Server?

To use the Gritai Basic MCP Server, clone or download the project, set up a virtual environment, install dependencies, and configure it with your AI assistant. Detailed instructions are provided in the README file.

Key Features of Gritai Basic MCP Server?

  • Two example MCP servers demonstrating local file operations and API integrations.
  • Motivational Quotes & Task Manager Server for local task management.
  • Any API Server for fetching real-time data from external APIs.

Use Cases of Gritai Basic MCP Server?

  1. Managing personal tasks with motivational quotes.
  2. Fetching real-time police incidents from Norway.
  3. Accessing stock market data through API integration.

FAQ from Gritai Basic MCP Server?

  • What is MCP?
    MCP stands for Model Context Protocol, which allows AI assistants to connect to external tools and data sources.

  • What are the prerequisites?
    You need Python 3.11 or higher installed on your computer.

  • How do I customize the servers?
    You can add new quotes by editing the quotes.json file and add new tools using the @mcp.tool() decorator in the code.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
astensby
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