PrivateGPT MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is PrivateGPT MCP Server?

PrivateGPT MCP Server is a Model Context Protocol (MCP) server implementation that allows seamless integration of PrivateGPT with any MCP-compatible application, enabling powerful AI capabilities.

How to use PrivateGPT MCP Server?

To use the server, clone the repository, configure the pgpt.env.json file, and start the server using the provided script. Interact with the server via API calls to utilize its features.

Key features of PrivateGPT MCP Server?

  • Authentication and Authorization: Secure user login and token management.
  • Chat Management: Initiate and manage conversations with the server.
  • Group and Source Management: Organize knowledge sources and control access.
  • Security Features: Includes TLS encryption, password encryption, and logging.

Use cases of PrivateGPT MCP Server?

  1. Customer Support: Build intelligent conversational agents.
  2. Knowledge Management: Manage and retrieve structured data.
  3. Multi-User Collaboration: Facilitate collaborative workflows.
  4. Customizable Functionality: Tailor features to specific application needs.

FAQ from PrivateGPT MCP Server?

  • Is the server secure?

Yes, it implements various security measures including TLS and password encryption.

  • Can I customize the features?

Yes, you can enable or disable individual server functionalities through the configuration file.

  • How do I install the server?

Clone the repository, install dependencies, and configure the server as per the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
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.

8 hours ago