What the connector does
Sandstorm runs a hosted MCP server (Model Context Protocol, the open standard Claude uses for connectors). Add it to Claude and Claude gets the same toolset Sandstorm's own agent uses: brand context and memory, offers and the asset library, image and video generation, competitor research through Watchtower, and ad account management across Meta, TikTok, Google, and X. It works in claude.ai, Claude Desktop, Claude Code, and across a whole Claude Team or Enterprise organization.
The server URL
The Sandstorm MCP server URL is https://mcp.sandstormapp.com/mcp. Every setup below uses this one URL. The server is hosted by Sandstorm, speaks MCP over HTTPS (streamable HTTP transport), and handles sign-in with OAuth. There are no API keys to manage, and you never need a client ID or secret: leave any advanced OAuth fields blank and Claude registers itself automatically.
https://mcp.sandstormapp.com/mcpAdd to claude.ai and Claude Desktop
1. Open Settings, then Connectors, and click 'Add custom connector'. 2. Name it Sandstorm, paste the server URL above, and click Add. 3. Click Connect and sign in with your Sandstorm account (Google, Facebook, or email/password). 4. In any chat, open the tools menu in the composer and make sure Sandstorm is toggled on. Claude Desktop and claude.ai share the same connector settings, so setting it up in one covers both.
Claude Team & Enterprise (whole organization)
To roll Sandstorm out to a Claude Team or Enterprise organization, an org Owner adds it once: open Organization settings, then Connectors, click 'Add custom connector', and paste the same server URL. No OAuth client ID or secret is needed. The connector then appears in every member's own Connectors list, where each person clicks Connect and signs in with their own Sandstorm account. Everyone acts as themselves, with their own brand access, and their work is attributed correctly in Sandstorm.
Claude Code
Add the server from your terminal with the command below, then run /mcp inside a session and choose Authenticate to sign in (your browser opens once). Add --scope user to make it available in every project, or commit a .mcp.json to a repo to share the config with your whole team. 'claude mcp list' shows connection status at any time.
claude mcp add --transport http sandstorm https://mcp.sandstormapp.com/mcpSign-in and security
Authentication is standard OAuth: Claude opens a browser window, you sign in on sandstormapp.com, and Claude stores the resulting token securely. Your Sandstorm password never passes through Claude, and access is scoped to your own account. Tokens refresh automatically; if you haven't used the connector in over a week you may be asked to sign in again. To revoke access, remove the connector from Claude's settings (or run 'claude mcp remove sandstorm' in Claude Code). You can re-add it anytime.
Brands, credits, and where outputs land
Every request names the brand it's for, so say it: 'make three statics for Crockett Coffee'. With one brand you can leave it out. With several, Claude asks which one when you don't say, and suggests the brand you last worked on; ask it to 'list my brands' to see them all. Each result says which brand it ran for. Anything you generate is saved to that brand's asset library and returned as a permanent link, so nothing lives only in the chat. Generation spends your organization's Sandstorm credits, exactly like working in the app.
Open Brand ContextTroubleshooting
'Needs authentication' in Claude Code: run /mcp, pick sandstorm, and choose Authenticate. A tool returns NOT_CONNECTED: that integration (Meta, Shopify, and so on) isn't linked to that brand yet; connect it from the brand's Integrations tab in Sandstorm. The connector won't add: check the URL is exactly https://mcp.sandstormapp.com/mcp, with the /mcp path included. Anything else: team@sandstormapp.com.