Use your ST workspace in Claude.

You need an ST account with an active workspace membership and a Claude account that supports custom connectors. This guide covers a custom connection, not a promise that SaaS Tracker is already listed in Claude’s public directory. Available tools depend on your current role, workspace service state and permissions.

Sign in at ST’s Claude connection page. For each workspace, read the sharing notice, select only the permissions you want, and click Connect this workspace or Update workspace permission. Basic read access is the default. Source addition, extended details, generation, review actions, on-demand checks and exports are separate choices. New memberships are not connected automatically. ChatGPT permissions remain separate.

In Claude, open Settings → Connectors → Add custom connector. Name it SaaS Tracker and enter https://saastracker.co/api/claude-mcp. If Claude asks for your own OAuth client, use client ID client_01M4K2CD46DM0W5N43Y8TDTGVH and leave the client secret blank. This is a public client identifier, not a password. Complete the WorkOS sign-in with the same ST account and review the consent screen. Claude’s interface and account availability may vary.

“List my connected ST workspaces.” Then: “For [workspace], list monitored sources and show a saved Current Terms Brief with capture date, citations and limitations.” When more than one workspace is connected, name the intended workspace explicitly. A saved Current Terms Brief explains one captured document; it is not a before/after change analysis.

With the corresponding permissions, request public-source additions and baseline checks, new ST briefs or change analyses, review status and notes, reviewer assignments and deadlines, source-context updates, on-demand checks, archive search, and evidence exports. Actions run without a separate ST confirmation page, though Claude may ask for approval. New sources must finish capturing before a brief can be generated. Pending or failed captures are not successful baselines. Human review outcomes must come from the responsible human, not an AI assertion.

For example: “Prepare my weekly review briefing for [workspace] for the last complete week in my timezone. Summarize new changes, overdue decisions and evidence gaps. Do not change anything.” This uses existing records; it does not create a schedule or silently resolve decisions.

The ST saved brief is the cited foundation. Claude’s additional explanation is separate, is not validated or saved by ST, and is not legal advice. Optional ST generation uses ST’s configured AI processing described in its Privacy Policy.

Basic reads share workspace and source names, capture dates, saved briefs with quotations, and pending change notices. Extended access can also share source business context, preserved excerpts, internal review notes, reviewer display names, assignments and deadlines. Evidence downloads require ST sign-in and current permission. No tool exposes teammate email fields, payment credentials or billing records. ST receives bounded tool arguments needed for your request, not automatic access to unrelated Claude conversation history, memory or files.

Information delivered to Claude becomes subject to your applicable Anthropic account terms, settings and privacy controls. Review those controls before sharing confidential, privileged or regulated information. ST’s business/API safeguards do not establish the same safeguards for a customer’s independently selected Claude account.

At the connection page, disconnect one workspace or all your ST workspaces from Claude. You can also remove the connector in Claude. ST disconnect blocks new requests, but an action already accepted for execution may finish. It does not erase copies already in conversations or downloads; manage those through the receiving service. Billing, account deletion, member invitations, roles, credentials, retention, backups and Platform administration are not connector tools. Document uploads remain on the ST website.

If no workspaces appear, check that both sign-ins use the same ST identity, the workspace is explicitly connected, and membership is still active. For action failures, check the relevant permission and execution receipt before retrying. Expired or revoked access fails closed. Contact hello@saastracker.co for support; never email passwords or OAuth tokens.