Add API key to .env file

Created By
heureux831a year ago
A simplest MCP system implemented in Python, including a client and several servers.
Overview

What is MCP-Demo?

MCP-Demo is a minimal implementation of a Multi-Client-Server (MCP) system in Python, designed to help users understand the operation of the entire MCP system.

How to use MCP-Demo?

To use MCP-Demo, you need to set up a virtual environment, install dependencies, create a .env file with your API key, and run the client with the specified server configuration.

Key features of MCP-Demo?

  • Simple and minimalistic design for easy understanding of MCP systems.
  • Supports integration with various LLM services by configuring the .env file.
  • Includes a client and multiple server implementations for demonstration purposes.

Use cases of MCP-Demo?

  1. Learning about the architecture and functioning of MCP systems.
  2. Testing and developing applications that require a client-server model.
  3. Experimenting with different LLM services by modifying the .env configuration.

FAQ from MCP-Demo?

  • What programming language is MCP-Demo written in?

MCP-Demo is implemented in Python.

  • How do I add my API key?

You can add your API key by creating a .env file and including the line: OPENAI_API_KEY=your_api_key.

  • Can I use other LLM services?

Yes, you can use other LLM services by adding the appropriate API keys in the .env file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
heureux831
Star
0
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
Voyei

3 hours 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.

13 hours ago