Use Your Saved Posts From Claude, ChatGPT or Cursor

A saved post is only worth saving if you can find it again. Search covers the case where you remember a word from it. It does not cover the case you actually have, which is closer to: “someone explained pricing better than I ever have — who, and what did they say?”

That is a question for a language model, not a text box. So SocialClipper now runs an MCP server: your library shows up as a tool inside Claude, ChatGPT or Cursor, and you ask there.

What MCP actually is

The Model Context Protocol is a standard way for an app to hand tools to an AI client. The client already knows how to speak it, so instead of us building a chat window and hoping you like it, your library appears inside the assistant you already use.

Three tools are exposed, and that is the whole surface:

• Search your posts — by words, and optionally narrowed to one board or platform.
• Open one in full — the complete saved text, the author, and the link to the original.
• List your boards — what you file things under, and how much is in each.

All three are read-only. Nothing in the protocol lets an assistant delete a post, publish a board, or change your account.

Why this costs you nothing extra

Worth being plain about, because “AI feature” usually means a price rise. MCP hands over tools; the model doing the thinking is the one you are already paying for. We serve text from your library. There is no separate AI add-on, no usage meter, and no key for you to supply.

It also means the answers are as good as your assistant is. Upgrade your Claude or ChatGPT plan and the same library gets better answers, with nothing to change here.

Connecting it

You need two things, both on your account page: the server URL and your API key.

URL      https://socialclipper.io/mcp
Header   Authorization: Bearer <your API key>

Add those wherever your client takes a custom MCP server. In Cursor that is your MCP settings; in a desktop client it is usually a config file entry. Once it connects, ask it something you know is in your library — the honest test is whether the answer comes back with a link you can click.

What it does not do yet

Three limits, stated up front rather than discovered:

• There is no one-click Connect button. Clients that expect a full OAuth handshake will not set this up for you yet — you paste a URL and a key. That is a real limitation and it is on the list.
• It reads the cloud copy, not your device. Saving is free and unlimited in your own browser, which also means a server cannot see it. Only a Premium library has a copy for this to read.
• It searches words, not meaning.Ask for “pricing” and it finds posts containing “pricing”. Your assistant does the interpreting once the posts are in front of it.

What it is good for

The pattern that works is asking your assistant to do something with what you saved, rather than asking it to find one post:

• “What have I saved about onboarding? Group it by the argument being made.”
• “I am writing about pricing. Pull the posts I saved that disagree with each other.”
• “Summarise my competitor-watch board from the last month and link each point.”

That is the thing a folder of bookmarks has never been able to do: not storage, but recall with the reasoning attached — and every claim traceable to a post you chose to keep.

A note on what leaves your library

Only what you ask about. The assistant searches, gets the matching posts back, and uses them to answer; it is not handed your whole library, and nothing is sent anywhere until a question requires it. Your API key is the only credential involved, and regenerating it on your account page disconnects every client instantly.