Mcp client example

Created By
t-shiratoria year ago
This is a sample CLI chat application for an AI assistant using the Anthropic API in conjunction with an MCP client and MCP server.
Overview

what is Mcp client example?

Mcp client example is a sample CLI chat application designed for an AI assistant that utilizes the Anthropic API in conjunction with an MCP client and MCP server.

how to use Mcp client example?

To use the Mcp client example, install the necessary packages using pnpm install, configure your environment variables in the .env file, and run the application with pnpm start.

key features of Mcp client example?

  • CLI interface for easy interaction with the AI assistant.
  • Integration with the Anthropic API for advanced AI capabilities.
  • Ability to handle queries related to date and time.

use cases of Mcp client example?

  1. Assisting users with date and time queries.
  2. Providing information and responses based on user input.
  3. Demonstrating the capabilities of the MCP protocol in a chat application.

FAQ from Mcp client example?

  • What is the MCP protocol?

The Model Context Protocol (MCP) is a protocol designed for AI applications to facilitate communication between clients and servers.

  • Is the Mcp client example free to use?

Yes! The Mcp client example is open-source and free to use.

  • Can I modify the Mcp client example?

Yes! You can modify the code as per your requirements since it is available on GitHub.

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

2 days ago