meGPT - upload an author's content into an LLM

Created By
adriancoa year ago
Code to process many kinds of content by an author into an MCP server
Overview

What is meGPT?

meGPT is a project designed to process an author's diverse content into a Model Context Protocol (MCP) server, enabling the creation of a personalized language model that can answer questions and generate summaries in the author's voice.

How to use meGPT?

To use meGPT, clone the repository, set up the Python environment, and run the build script to process the author's content. You can also contribute your own content by adding it to the repository and submitting a pull request.

Key features of meGPT?

  • Supports various content types including books, blog posts, podcasts, and videos.
  • Automatic processing of YouTube content, including individual videos, playlists, and channels.
  • Integration with an MCP server for AI applications, allowing semantic search and content filtering.
  • Robust error handling and logging for content processing.

Use cases of meGPT?

  1. Authors can create a personalized chatbot that answers questions based on their published content.
  2. Researchers can utilize the MCP server to access a wide range of processed content for analysis.
  3. Educators can leverage the content to develop teaching materials or interactive learning tools.

FAQ from meGPT?

  • Can I use meGPT for any author?

Yes! You can clone the repository and add your own content to create a personalized model.

  • Is there a cost to use meGPT?

No, meGPT is free to use and encourages contributions from other authors.

  • What types of content can be processed?

meGPT supports a variety of content types including text, audio, and video, making it versatile for different authors.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
adrianco
Star
256
Language
Python
License
Apache-2.0 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