Connect an AI tool

SnowDots runs a remote MCP server over Streamable HTTP. The endpoint is:

https://app.snowdots.com/mcp/snowdots

You’ll also find it, with a copy button and setup snippets, under AI connections in your agency.

A connection always acts as you, in one agency, with only the permissions you grant it. It can create drafts and upload versions — it can never publish or share.

Sign in with OAuth (recommended)

Most AI tools connect by signing in: there’s no token to copy. When the tool asks, you sign in to SnowDots, pick the agency and tick the permissions to allow.

Claude

1. In Claude (web or desktop), open Settings → Connectors → Add custom connector.

2. Name it SnowDots, paste the endpoint and add it:

   https://app.snowdots.com/mcp/snowdots

3. Click Connect, sign in to SnowDots and pick your agency.

Claude Code

1. Add the server from your terminal:

   claude mcp add --transport http snowdots https://app.snowdots.com/mcp/snowdots

2. In Claude Code, run /mcp, choose snowdots and sign in.

Cursor

1. Add this to ~/.cursor/mcp.json:

   {
     "mcpServers": {
       "snowdots": {
         "url": "https://app.snowdots.com/mcp/snowdots"
       }
     }
   }

2. Sign in when Cursor asks.

VS Code

1. Add this to .vscode/mcp.json:

   {
     "servers": {
       "snowdots": {
         "type": "http",
         "url": "https://app.snowdots.com/mcp/snowdots"
       }
     }
   }

2. Start the server and sign in when asked.

SnowDots supports OAuth 2.1 with discovery and dynamic client registration, so any MCP client that implements the MCP authorization spec can connect the same way. OAuth access tokens last 60 minutes and are refreshed automatically (refresh tokens last 30 days).

Note

A tool keeps one connection per member. Approving it again — for another agency or different permissions — replaces the earlier approval and invalidates its old tokens.

Connect with a token

For clients that can’t sign in, create a bearer token instead.

1. In your agency, open AI connections and choose New token.

2. Give it a name (for example Build server) and pick its permissions.

3. Copy the token. It’s stored hashed and shown only once.

4. Configure your client to send it on every request:

   Authorization: Bearer <token>

Tokens expire after 24 hours. Create a new one when it runs out.

For a client that takes headers in its config, for example:

{
  "mcpServers": {
    "snowdots": {
      "url": "https://app.snowdots.com/mcp/snowdots",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Permissions

Each connection gets one or more permissions (scopes):

Permission	Scope	Allows
Read artifacts	artifacts:read	Listing artifacts, clients, contacts, spaces, comments, inbox and context; checking publish status.
Create artifacts and upload versions	artifacts:write	Creating artifacts, uploading versions, commenting, resolving threads, tagging and filing.
Submit artifacts for review	artifacts:submit	Asking a publisher to review a version.
Create and edit clients and contacts	clients:write	create_client, update_client, create_contact, update_contact.

The tools reference lists the permission each tool needs.

Permissions never widen your role. A connection with clients:write still needs a member whose role may manage clients, and it only reaches the clients and artifacts that member can reach. No permission allows publishing or sharing.

Call whoami to check which account, agency and permissions a connection has.

Manage and revoke connections

AI connections lists every connection you’ve made in the agency — name, status, sign-in method, permissions, last use and expiry. Revoke one and the tool loses access immediately. Each member manages their own connections; how many you can keep active depends on your plan.

Requests to the MCP server are rate limited to 60 per minute.