Chat Nextjs Mcp Client

Created By
shricodeva year ago
⚡ Chat MCP Client for Remote hosted MCP Servers (with Composio) and locally hosted MCP servers. 📡
Overview

what is Chat Nextjs Mcp Client?

Chat Nextjs Mcp Client is a chat application designed for both remote hosted MCP servers (with Composio) and locally hosted MCP servers, built using Next.js.

how to use Chat Nextjs Mcp Client?

To use the Chat Nextjs Mcp Client, first run the development server using the command npm run dev or any of the alternative commands provided. Then, open your browser and navigate to http://localhost:3000 to see the application in action.

key features of Chat Nextjs Mcp Client?

  • Supports both remote and local MCP servers.
  • Built with Next.js for optimized performance.
  • Easy to set up and run with simple commands.

use cases of Chat Nextjs Mcp Client?

  1. Connecting to remote MCP servers for chat functionalities.
  2. Hosting chat services locally for development and testing.
  3. Utilizing Next.js features for enhanced user experience.

FAQ from Chat Nextjs Mcp Client?

  • What is MCP?

MCP stands for Multi-Channel Platform, which allows for various communication methods.

  • Is this project open-source?

Yes! The Chat Nextjs Mcp Client is available on GitHub for contributions and feedback.

  • How do I deploy the application?

The easiest way to deploy is using the Vercel platform, as detailed in the deployment documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shricodev
Star
0
Language
TypeScript
License
-

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.

18 minutes ago