# SnapWidget MCP server > Create Instagram, social feed and Google review widgets and get embed code to add them to your website. - Listing: https://mcp.tc/i/snapwidget - Connect: use the server's own URL `https://snapwidget.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Marketing & SEO](https://mcp.tc/c/marketing-seo) - Vendor: SnapWidget - Homepage: - Repository: - Package: npm `snapwidget` ## About SnapWidget connects an AI assistant to the SnapWidget service. It can sign up an account, connect social accounts (Instagram, Facebook, TikTok, X, YouTube), build feed and review widgets (Google, G2, testimonials) and return the embed code for a website. It runs as a hosted Streamable HTTP endpoint at https://snapwidget.com/mcp. Users sign in with their email and a code SnapWidget sends them, through OAuth in the browser. A token can also be sent in the Authorization header. No separate API key is needed. ## What it can do - Sign up for a SnapWidget account with an emailed code - Connect Instagram, Facebook, TikTok, X and YouTube accounts - Create social feed and review widgets - Show Google and G2 reviews and testimonials - Get embed code for WordPress, Wix, Shopify, Squarespace and JS frameworks ## Example prompts - "Add my Instagram feed to the home page." - "Show our Google reviews on the contact page." - "Put the videos of my YouTube channel on this site." - "List my SnapWidget widgets and give me the embed code for Next.js." ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http snapwidget https://snapwidget.com/mcp ``` 2. Start Claude Code, type `/mcp`, pick **snapwidget** and choose **Authenticate**. A browser window opens for the SnapWidget sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**. 2. Name it **SnapWidget** and paste this URL: ```url https://snapwidget.com/mcp ``` 3. Click **Add**, then **Connect**, and sign in when SnapWidget asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://snapwidget.com/mcp` and click **Add**. 3. Click **Connect** and sign in when SnapWidget asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**. 2. Enter a name for the server. 3. Under **Connection**, paste `https://snapwidget.com/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to SnapWidget to sign in. 4. Check **I understand and want to continue**, then select **Create as a plugin**. Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can). ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "snapwidget": { "url": "https://snapwidget.com/mcp" } } } ``` Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"snapwidget","type":"http","url":"https://snapwidget.com/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "snapwidget": { "type": "http", "url": "https://snapwidget.com/mcp" } } } ``` VS Code asks you to sign in the first time the server starts. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "snapwidget": { "serverUrl": "https://snapwidget.com/mcp" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add snapwidget --url https://snapwidget.com/mcp codex mcp login snapwidget ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.snapwidget] url = "https://snapwidget.com/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http snapwidget https://snapwidget.com/mcp ``` Then, inside Gemini CLI, run `/mcp auth snapwidget` to sign in. This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "snapwidget": { "type": "http", "url": "https://snapwidget.com/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://snapwidget.com/mcp`. ## Details - Server version: 1.0.0 - Last checked: 2026-11-10 (reachable, asks for credentials) - Listed: 2026-11-04 - Updated: 2026-11-04 --- Source: https://mcp.tc/i/snapwidget (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report