Add TileSet to Claude Code
One command gives Claude Code the TileSet tools. Then ask it to put your Google reviews or YouTube videos on the site you are building, and it connects the source, builds the widget and pastes the snippet.
Before you start
- Claude Code installed and working in the project for your website.
- A Google account. Your TileSet account is created the first time you sign in, on the free plan, with no card.
- Access to the account you want to show: your Google Business listing or your YouTube channel handle.
Set it up
-
Run this once in a terminal.
--scope usermakes TileSet available in every project on this machine, so you only do it once.claude mcp add tileset --scope user --transport http https://app.tileset.com/mcp -
Start Claude Code in your site’s folder and ask it to add a feed, for example: “Add my YouTube channel @yourchannel to my homepage with TileSet”.
-
The first time Claude uses TileSet, a browser tab opens. Sign in with Google or by email, and approve access. There is no key to copy. You can also start this sign-in yourself from
/mcpinside Claude Code.
Claude connects the source, creates the widget, and pastes two lines into your page: one script tag and one div. It can then check the live page for you, which confirms the snippet is there and the widget is serving posts.
What to ask for next
- “Show my Google reviews under the booking form, 4 stars and up.” (Star filters are on Growth and up.)
- “Make the YouTube feed 3 columns and switch it to the dark theme.”
- “Add my YouTube channel @yourhandle to the videos page, regular uploads only, no Shorts.”
- “Which TileSet widgets do I have, and where is each one used?”
A change to a widget shows up on every page that already has it. Nothing needs re-pasting.
Is it safe to give Claude access?
The sign-in gives Claude a TileSet key for your widgets and sources, and nothing more. It never sees your Google password or any platform password, and it never gets the platform access tokens either: those stay encrypted on our side. TileSet also never hands it your content, from any source: Claude sees which sources and widgets you have, their settings and counts such as how many reviews a source holds, and a preview of the widget as visitors see it. You read the posts and reviews themselves in your dashboard.
The key shows up in your dashboard under Agents & API, named after the app that asked for it. Revoke it there and Claude loses access straight away.
Deleting a source or a widget cannot be undone, and a page that still has the widget on it shows nothing in its place. If you want Claude to check with you first, say so in your project instructions.
Common questions
Do I need an API key? No. The browser sign-in replaces it. API keys exist for scripts and CI jobs, and you create them under Agents & API if you need one.
Does my site need to call your API? No. The page needs the script tag and the div, nothing else. The script loads after your page and sets no cookies.
What if YouTube or Google is down? Your widget keeps showing the last posts we fetched and picks up new ones on the next refresh.