Add TileSet to Cursor

Add the TileSet server to Cursor's MCP settings, sign in once in the browser, then ask the agent to put a Google reviews wall or a YouTube feed into the page you are working on.

Before you start

Cursor, with your website’s project open.
A Google account. Your TileSet account is created the first time you sign in, free, with no card.
Access to the account you want to show: your Google Business listing or your YouTube channel handle.

Set it up

Open Cursor’s MCP settings and add a server, or edit ~/.cursor/mcp.json (every project) or .cursor/mcp.json in your project (this project only):
```
{
  "mcpServers": {
    "tileset": { "url": "https://app.tileset.com/mcp" }
  }
}
```
Cursor lists TileSet and asks you to sign in. A browser tab opens: sign in with Google or by email, and approve access. There is no key to paste.
In the agent chat, ask: “Add my YouTube channel @yourchannel to my homepage with TileSet”.

The agent connects the source, creates the widget, and adds one script tag and one div to your page. Ask it to check the published page afterwards and it will confirm the widget is there and serving posts.

What to ask for next

“Add a Google reviews wall to the contact page. Here is our Maps link: …”
“Make the feed a carousel and hide the captions.”
“Put the same YouTube widget on the about page too.”

Showing one feed on several pages costs nothing extra. It is one widget, pasted twice.

Is it safe?

Cursor gets a TileSet key for your widgets and sources, never your social passwords or platform tokens. TileSet also never hands it your content, from any source: Cursor 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 under Agents & API in your dashboard; revoke it there and Cursor loses access at once. Deleting a widget or a source cannot be undone, so keep an eye on what you approve.

Common questions

Does the snippet need a React component or a useEffect? No. Load the script once per page and put the div where the feed goes. The script finds widgets added later on its own.

Can I use an API key instead of the sign-in? Yes, for CI or a headless setup. Create one under Agents & API and send it as Authorization: Bearer <key>.

Start freeFree plan, no credit card. Sign in with Google.