Sight / docs

Connect your agent

Sight provides a remote Streamable HTTP MCP endpoint:

https://api.usesight.dev/mcp

Your client must support remote MCP with OAuth. Clients differ in how they add servers: use their MCP settings, or let your coding agent update its configuration if it can.

Two steps

Add the server once — your client's own OAuth support takes it from there:

claude mcp add --transport http sight https://api.usesight.dev/mcp

Then just ask your agent, in plain language:

Add Sight analytics tracking to my site.

No API key, no manual OAuth instructions — Claude Code detects Sight's OAuth requirement on its own and opens your browser to sign in.

What authorization does

Your client discovers Sight's authorization server, registers its callback, and starts OAuth with PKCE. Sight opens /authorize, where you sign in with Google or email and approve access. The client receives a short-lived authorization code and exchanges it for tokens automatically. There is no project to pick on the consent screen.

Access is scoped to your account. The agent lists and creates projects itself and names which project each action targets (list_projects, create_project, and a project_id argument on the other tools). It can read analytics and subscription metrics, record events and spend, create goals and funnels, obtain install-only tracking configuration, and set a project's domain allowlist. It cannot manage payment secrets, account settings, or other Sight accounts.

Access tokens expire after one hour. Refresh tokens rotate automatically and expire after 30 days without renewal. You can revoke a connection in Dashboard → Setup → Connected agents.

Manual client configuration

For clients using the mcpServers configuration shape:

{
  "mcpServers": {
    "sight": {
      "type": "http",
      "url": "https://api.usesight.dev/mcp"
    }
  }
}

Select Connect / Authenticate in the client after adding the server. No env API key is needed. Some clients use a different config shape; use the same remote URL and their OAuth support.

Troubleshooting

  • 401: authorize Sight or reconnect if access was revoked.
  • Invalid callback: restart connection from the client; do not edit its authorization URL.
  • Request expired: restart authorization. Codes are valid for five minutes and work once.
  • No projects yet: ask the agent to create one — it calls create_project (and asks you for the site's domain if it can't determine it).
  • "pass project_id": the account has more than one project; the agent should call list_projects and pass the right project_id.
  • No browser opens: follow the authorization link shown by your client.
  • Client does not support OAuth: use a client with remote MCP OAuth support. The legacy local stdio server is a separate developer option, not the keyless flow.

Never paste OAuth access or refresh tokens into website code or source control.