The Librarian MCP server
Connect your AI to Thingy
Bring Jamie Thingelstad’s whole archive into Claude, ChatGPT or Claude Code. Your AI gets the same tools Thingy uses: it can search, read, count and trace across twenty-five years of writing, and link you to every source it uses. Weekly Thing subscribers sign in with their email; there is no password.
Building with it, or curious how it works? The Librarian MCP reference documents every tool with its parameters and results, the OAuth flow, budgets and protocol conventions, generated from the server’s own declarations.
The card catalog
What your AI can read
- The Weekly Thing 352 Weekly Thing issues since 2017
- thingelstad.com 10,444 blog posts since 2000
- Links 38,925 links Jamie shared
- Photos 15,038 photos, searchable by what they show
Plus the audio editions of the newsletter, the Another Thing podcast with its transcripts, and every Currently entry: what Jamie was reading, watching, playing and building, week by week. It is Jamie’s published writing only; nothing private is in it.
Try these in your AI
Five things to ask
-
“What did Jamie publish on this day in past years?” The archive’s on this day, across the newsletter, the blog and the podcast, newest year first.
-
“How has Jamie’s thinking about RSS changed since 2017?” A dated account in Jamie’s own words, from the first mention to the latest.
-
“Has Jamie ever linked to this?” Paste a URL or name a site: every time it appeared, and what Jamie said about it.
-
“Show me photos of bike rides along Minnehaha Creek.” Photos found by what they show, linked to the post or issue they appeared in.
-
“What books was Jamie reading in 2024?” Straight from the Currently section of every issue that year.
MCP prompts
Clients that support MCP prompts also offer ready-made asks: a year in review, a reading path through a theme, and a research brief on a person or product.
Pick your client
Claude (claude.ai or the apps)
-
Settings → Connectors → Add custom connector, then paste:
MCP URLhttps://librarian.thingelstad.com/mcp -
Claude walks you through sign-in: enter your Weekly Thing email, type the six-digit code from the email (your Mac or iPhone will offer it automatically), and approve access.
-
If you added the connector before, disconnect and reconnect it once so Claude picks up the current tools.
ChatGPT
-
Custom MCP connectors need Developer mode (Plus, Pro, Business or Enterprise, on the web): Settings → Apps → Advanced settings → enable Developer mode.
-
Then add a connector and paste:
MCP URLhttps://librarian.thingelstad.com/mcp -
ChatGPT walks through the same email and six-digit-code sign-in.
Claude Code
-
Terminal
claude mcp add --transport http librarian https://librarian.thingelstad.com/mcp -
Then run
/mcpinside Claude Code to sign in.
Any other MCP client
https://librarian.thingelstad.com/mcp
-
The endpoint speaks MCP streamable HTTP with OAuth 2.1 discovery.
-
Point your client at the URL above and it finds the sign-in flow on its own.
-
The reference walks through the flow step by step.
Apps that ask for a client ID
Some apps don’t sign up on their own. Instead they show a callback (redirect) URL and ask you for a
client ID, an authorization URL and a token URL. Sign in to Thingy, open your profile, and under
MCP connections choose Set up an app. Paste the app’s callback URL
there, and Thingy gives you every value to copy back: the client ID, the two URLs, the scope
(archive:read), and the MCP server URL. Leave the client secret blank and turn PKCE (code
challenge) on. A client ID you set up works only for your own account, and deleting it disconnects the app.
Agents in your browser (WebMCP, beta)
betaWhile you are signed in on the Thingy chat page, the page also registers its archive tools with your browser’s model context (the emerging WebMCP standard). An agent working in your browser, such as Gemini in Chrome or a desktop MCP client connected through a WebMCP bridge extension, can then search the archive with your session and no connector setup. The tools appear when you sign in and go away when you sign out; they only read, and they see nothing the chat itself cannot.
House rules
Fair use
Each reader can make 500 tool calls a day (1,000 for Supporting Members) and up to 300 an hour. That budget is separate from Thingy’s own chat. A busy research session uses a few dozen calls.