FeedGPT connects to your social channels, cleans and structures the data, and hands it to Claude, ChatGPT, or your own agent over MCP — no proprietary chatbot to learn, no dashboard to babysit.
// works with Claude, ChatGPT, and any MCP-compatible client

FeedGPT isn't a dashboard you check or a chatbot you talk to instead of the ones you already use. It's the plumbing between your feeds and the AI you already have open.
Every source gets its own endpoint. Send data straight from the platform, or automate it through Zapier, Make, Apify, or a custom script — anything that can POST JSON works.
Field mapping, deduplication, and schema healing turn inconsistent raw payloads into a standard shape — with a confidence score and audit entry for every decision.
Connect the FeedGPT MCP server to Claude, ChatGPT, or your own agent. The intelligence is whichever model you're already using — FeedGPT just gives it something reliable to read.
Copy any prompt, paste it into Claude, run it against Demo mode. No configuration.
→ Replaces every dashboard login with one question.
→ Finds the high-share content your likes-sorted dashboard buries.
→ Same prompt monthly, same quality from every account manager.
→ Your best client becomes the sales deck for the rest.
→ Evidence-based creative briefs instead of intuition.
→ Every answer backed by FeedGPT's audit trail. Show clients the log behind their report.
Demo mode gives you a sample agency portfolio (three clients, six months of data) the moment you sign up. Free tier, no card.
Social platforms change their payload shapes without warning. FeedGPT is built to notice, adapt, and show its work — not to fail silently.
When a payload doesn't match the expected shape, FeedGPT proposes a fix and only applies it once confidence clears your threshold. Below that, it's flagged for review — never guessed silently.
Every ingestion, healing decision, and type mismatch is logged with a timestamp and confidence score — so "why does this say 42 likes" always has a real answer.
Roadmap: schema-healing inference moving to infrastructure we control (via the NVIDIA Inception Program), so payload diagnosis never has to leave our own environment. This is separate from the AI you connect over MCP to analyze your data — that's still your Claude or ChatGPT, on your terms.
The webhook endpoint is a standard HTTP target. If your tool can send a POST request, it can feed FeedGPT.
Because we can't control what shape of payload an automation tool sends, schema healing isn't a nice-to-have here — it's what makes "connect anything" safe to promise.
Agencies and regulated teams don't get to say "the dashboard looked right." FeedGPT keeps the evidence: what came in, what changed, and why.
Recognized by the NVIDIA Inception Program and INSEAD AI Venture Lab for the underlying data-infrastructure approach.
No per-seat chatbot license — you already pay for Claude or ChatGPT. FeedGPT prices on sources and ingestion volume.
Events = webhook deliveries received, including from Zapier, Make, or Apify. Overages billed per 1,000 events; no source ever silently stops ingesting because of a cap.
Connect a source, point Claude or ChatGPT at the MCP server, and ask your first question.