MCP Host Client Server SSE

Created By
HanShan006a year ago
手搓MCP样例,使用SSE模式,访问本地数据。从Hosts到server全部代码演示。
Overview

what is MCP Host Client Server SSE?

MCP Host Client Server SSE is a natural language SQL database query system based on the Model Context Protocol (MCP). It allows users to convert natural language queries into SQL queries using a server-client architecture integrated with OpenAI for intelligent querying.

how to use MCP Host Client Server SSE?

To use the project, clone the repository, install the required dependencies, configure your OpenAI API key, create a sample database, and run the MCP server and client applications.

key features of MCP Host Client Server SSE?

  • 🚀 Server-client architecture based on MCP protocol
  • 📝 Natural language to SQL query support
  • 🔄 Real-time communication using Server-Sent Events (SSE)
  • 📊 Integration with SQLite database
  • 🤖 OpenAI/DeepSeek API integration
  • 📝 Complete logging system
  • ⚡ Support for asynchronous operations

use cases of MCP Host Client Server SSE?

  1. Querying user information in a database using natural language.
  2. Displaying orders for specific users.
  3. Summarizing user spending across orders.
  4. Retrieving user information based on order amounts.

FAQ from MCP Host Client Server SSE?

  • Can I use any natural language for queries?

Yes! The system supports various natural language queries.

  • What are the prerequisites to run this project?

You need Python 3.8+, pip, and an OpenAI API key.

  • Is there a logging feature?

Yes! The project includes a complete logging system to track queries and responses.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
HanShan006
Star
1
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

6 hours ago