Terminal-based Chat Client with MCP Server Integration

Created By
alan-meigsa year ago
MCP Client and Server Experiments
Overview

What is MCP_EXP?

MCP_EXP is a terminal-based chat client that integrates with an MCP server and OpenAI's API, allowing users to interact with an AI and access weather information through a chat interface.

How to use MCP_EXP?

To use MCP_EXP, set up the project by installing the required packages, create a .env file with your OpenAI API key, start the MCP server, and run the chat client to interact with the AI and get weather updates.

Key features of MCP_EXP?

  • Real-time chat interface with OpenAI integration
  • MCP server integration for extensible functionality
  • Weather service providing alerts and forecasts
  • Asynchronous operation for improved performance
  • Environment variable configuration for API keys

Use cases of MCP_EXP?

  1. Engaging in conversations with an AI assistant
  2. Retrieving real-time weather information and alerts
  3. Integrating with Cursor's Agent mode for enhanced functionality

FAQ from MCP_EXP?

  • What programming language is used for MCP_EXP?

MCP_EXP is built using Python.

  • Do I need to run the MCP server locally?

Yes, the MCP server must be running on your local machine to interact with the chat client.

  • Can I use MCP_EXP for other types of queries?

While it is primarily designed for weather queries, you can engage in general conversations with the AI.

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

20 hours ago
Gpt Scrambler

2 days ago