Demo de MCP Servers con Chainlit

Created By
0GiS0a year ago
Overview

what is Chainlit Demo?

Chainlit Demo is a project that allows developers to test MCP (Model Context Protocol) Servers using Chainlit, providing a seamless environment for integration with Azure Open AI.

how to use Chainlit Demo?

To use Chainlit Demo, clone the repository, add your Azure Open AI credentials in the .azure.env file, and run the application using the command chainlit run app.py -w.

key features of Chainlit Demo?

  • Easy setup with Dev Containers, no local installation required.
  • Integration with Azure Open AI for model context.
  • Ability to add and configure MCP Servers directly in the chat interface.

use cases of Chainlit Demo?

  1. Testing and deploying custom AI models with Azure Open AI.
  2. Creating interactive applications that utilize MCP Servers.
  3. Experimenting with different configurations of MCP Servers for various tasks.

FAQ from Chainlit Demo?

  • Do I need to install anything locally to use Chainlit Demo?

No! You can use Dev Containers to run the project without local installations.

  • How do I add my Azure Open AI credentials?

You need to fill in the .azure.env file with your API key and endpoint.

  • Can I use Chainlit Demo for any type of AI model?

Yes! As long as it is compatible with Azure Open AI, you can integrate it.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
0GiS0
Star
0
Language
Python
License
-
Tags

Recommend Servers

View All
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.

8 hours ago