AI-powered chat system with multiple MCP servers.

Created By
kira1228a year ago
AI-powered Chat System with multiple MCP servers.
Overview

What is the MCP Chat System?

The MCP Chat System is an AI-powered chat application that connects to multiple Model Context Protocol (MCP) servers, enabling seamless interaction with various AI functionalities.

How to use the MCP Chat System?

To use the MCP Chat System, clone the repository, set up your environment with the necessary API keys, and run the client with the desired server arguments.

Key features of the MCP Chat System?

  • Integration with multiple MCP servers for enhanced AI capabilities.
  • Access to local files, Slack conversations, and real-time web search.
  • Intelligent server selection based on user queries.

Use cases of the MCP Chat System?

  1. Accessing and retrieving information from local documents.
  2. Engaging in conversations using Slack integration.
  3. Performing real-time web searches to provide up-to-date information.

FAQ from the MCP Chat System?

  • Can I use the MCP Chat System for different types of queries?

Yes! The system intelligently determines the best server to use based on your query type.

  • Is there a cost associated with using the MCP Chat System?

The MCP Chat System is open-source and free to use under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kira1228
Star
2
Language
Python
License
MIT 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