Connect GoCSM to Your AI Assistant

This article explains how to connect your ChatGPT or Claude agents to GoCSM using GoCSM MCP.

Written By Karthik Anand

Last updated About 11 hours ago

Bring GoCSM's customer-success intelligence into any MCP-aware AI tool. Once connected, your agent can answer questions like "Which accounts are at risk of churning this month?", "Who hasn't logged in to AcmeCo in 30 days?", or "Trigger the renewal-outreach workflow for these three accounts" — using your own live data, scoped to your agency.

This guide covers Claude (the recommended setup), ChatGPT, and any other MCP client.

What You Get

The GoCSM MCP server exposes 22 tools across five categories. Your AI assistant chooses the right tool automatically based on what you ask.

Category

What it surfaces

Discovery

Find and inspect tracked sub-accounts and users

Risk & Triage

At-risk accounts, inactive users, failed payments, upcoming renewals

Product Adoption

Per-feature usage, adoption gaps, metric movers

Revenue & Expansion

MRR/NRR/churn summaries, upsell candidates

Actions

Trigger HighLevel workflows, request feedback, update priority/key-user flags

Read-only by default. Action tools (trigger workflow, request feedback, set priority/key-user) only run when you explicitly authorize the write:* scopes during sign-in.

Before You Start

You need:

  • An active GoCSM sub-account (sign-in is the same email/password you use at app.gocsm.com).

  • Create and copy a Private Integration Token from your GoCSM sub-account. Click here to know more.

  • An AI client that speaks MCP — Claude (Desktop, Code, or claude.ai web), ChatGPT (Pro/Business/Enterprise with Connectors), or any other MCP-capable agent.

Connection is OAuth 2.1 with PKCE — your AI client opens a browser, you paste your GoCSM Sub-account’s PIT in this page, approve permissions(scopes), and you're done.

Server endpoint (one URL to remember):

https://mcp.gocsm.com/api/mcp 

1. Claude (Recommended)

Claude has the most mature MCP support and is the fastest setup.

1A. Claude Desktop

  1. Open Claude Desktop → Settings → Connectors (or Developer → MCP Servers on older builds).

  2. Click Add custom connector.

  3. Enter:

    • Name: GoCSM

    • Server URL: https://mcp.gocsm.com/api/mcp

  4. Click Connect. A browser tab opens to mcp.gocsm.com/authorize.

  5. Sign in to GoCSM. Review the requested scopes and click Allow.

  6. The tab closes itself. Claude Desktop now shows GoCSM with a green dot and the 22 tools.

Test it:

"Show me the five accounts most at risk of churning."

Claude will call list_accounts_at_risk, display the table, and explain the drivers.

1B. Claude on the Web (claude.ai)

  1. Go to claude.ai → Settings → Connectors → Add custom connector.

  2. Paste https://mcp.gocsm.com/api/mcp and click Connect.

  3. Sign in to GoCSM, approve scopes.

  4. Start a new chat. The GoCSM connector is now available in every conversation on your account.

1C. Claude Code (CLI)

For developers using the Claude Code CLI:

claude mcp add gocsm https://mcp.gocsm.com/api/mcp 

On first invocation Claude Code opens your browser for the OAuth handshake. Subsequent runs reuse the cached token.


2. ChatGPT

GoCSM is exposed as a custom connector for ChatGPT Pro, Team, Business, and Enterprise plans (Connectors aren't available on Free).

  1. Sign in at chatgpt.com and open Settings → Connectors.

  2. Click Create (or Add custom connector).

  3. Fill in:

    • Name: GoCSM

    • MCP Server URL: https://mcp.gocsm.com/api/mcp

    • Authentication: OAuth (ChatGPT auto-discovers the rest from our well-known endpoints)

  4. Click Connect, sign in to GoCSM in the popup, approve scopes.

  5. In any chat, enable the GoCSM connector in the composer and start asking.

"Pull a list of upcoming renewals over $500/mo in the next 30 days and flag any that are in the 'Watch' health band."

ChatGPT will chain list_upcoming_renewals with the appropriate filters and summarize.

Note on Workspace deployment: Workspace admins (Business / Enterprise) can pre-approve the GoCSM connector for the whole workspace under Admin → Connectors → Allowed apps. Once approved, individual users don't see the connector approval prompt — only the OAuth sign-in.


3. Any Other MCP Client (Generic)

Cursor, Windsurf, Cline, Continue, Goose, Zed, and other MCP-aware tools all work the same way because GoCSM exposes the standard MCP discovery contract:

  • MCP descriptor: https://mcp.gocsm.com/.well-known/mcp.json

  • OAuth Authorization Server metadata (RFC 8414): https://mcp.gocsm.com/.well-known/oauth-authorization-server

  • Protected Resource Metadata (RFC 9728): https://mcp.gocsm.com/.well-known/oauth-protected-resource

Most clients only need the server URL — they discover everything else automatically.

Manual configuration

If your client requires explicit config, use these values:

FieldValue

Server URL

https://mcp.gocsm.com/api/mcp

Transport

streamable-http

Auth type

OAuth 2.1 (PKCE required, S256)

Authorization endpoint

https://mcp.gocsm.com/authorize

Token endpoint

https://mcp.gocsm.com/token

Dynamic client registration

https://mcp.gocsm.com/register (RFC 7591)

Revocation endpoint

https://mcp.gocsm.com/revoke

Dynamic Client Registration is supported, so your client can register itself on first run — no manual client-ID provisioning needed.

Example: minimal mcp.json snippet

For clients that take a JSON config file:

{ "mcpServers": { "gocsm": { "url": "https://mcp.gocsm.com/api/mcp", "transport": "streamable-http" } } } 

OAuth Permissions

When you sign in, your AI client requests a subset of these Permissions. You see and approve them in the consent screen.

Permissions (Scopes)

What it allows

Read or Write

read:accounts

List/search accounts, health scores, risks, opportunities

Read

read:users

List/search users, login activity, key-user flags

Read

read:revenue

MRR/NRR/churn, renewals, upsell candidates

Read

read:feedback

View feedback responses + NPS data

Read

write:workflows

Trigger HighLevel workflows from chat

Write

write:feedback

Send feedback-request to account owners

Write

write:metadata

Set account priority, mark/unmark key users

Write

Most assistants ship with read scopes pre-selected. Approve write scopes only if you want your AI to take actions on your behalf. You can revoke at any time from your GoCSM dashboard (Settings → Connected Apps).


Tool Catalog

The 22 tools your assistant has access to:

Discoverylist_tracked_accounts, search_accounts, get_account, search_users, get_user, get_agency_overview

Risk & Triagelist_accounts_at_risk, list_inactive_users, list_failed_payments, list_upcoming_renewals

Adoptionget_feature_metrics, list_feature_adoption_gaps, list_feature_metric_movers

Login Activityget_login_activity

Revenueget_revenue_summary, list_upsell_candidates

Feedbacklist_feedback_responses, request_feedback

Actionslist_workflows, trigger_workflow, set_account_priority, set_user_key_status

You don't need to memorize these — your AI picks the right tool from your natural-language question. Listed here for reference.


Example Conversations

Use these as starter prompts to gauge whether GoCSM is wired in correctly:

Pulse check

"Give me a one-paragraph agency health summary, then the three accounts most likely to churn."

Outreach prep

"Find accounts with renewals in the next 14 days that are in the Watch or At Risk band, sorted by MRR. For each, give me the top risk signal."

Adoption coaching

"Which features are seeing the biggest drop in usage week-over-week across my tracked accounts?"

Action

"List the workflows available for AcmeCo, then trigger the 'Renewal Reminder — 30 day' workflow on the account owner." (Requires write:workflows)


Security & Data Handling

  • Tenancy isolation: every request is scoped to the agency tied to your OAuth token. You cannot see another agency's data, and an agency admin's token cannot reach data outside their tenant.

  • Training: GoCSM does not use your data to train models.

  • Data residency: US.

  • Audit log: every tool call is logged with timestamp, tool name, account_id (when applicable), and outcome — retained for 90 days. Available to agency admins in the dashboard.

  • Rate limits: per-agency limits prevent runaway agents from exhausting capacity. Clients receive standard 429 responses with Retry-After when limits are hit; AI clients handle this transparently.

  • Token revocation: revoke any connected client from your GoCSM dashboard (Settings → Connected Apps) or via the /revoke endpoint.


Troubleshooting

Symptom

Likely cause

Fix

"Authorization with the MCP server failed"

Client probed a discovery URL we returned 404 on

Confirm your client speaks MCP spec ≥ 2025-03-26; reach out if it persists

Browser sign-in tab opens but never returns

Pop-up blocker / OAuth redirect URI mismatch

Allow pop-ups for mcp.gocsm.com; for self-built clients, register your redirect_uri via /register

429 Too Many Requests

Per-agency rate limit hit

Your AI will retry after the Retry-After window. If sustained, contact support to raise limits.

Tool calls return empty results

Token scope missing the right read:* scope

Re-connect and approve the missing scope; or your agency simply has no matching data

403 Forbidden on account_id

Account isn't in your tracked-accounts set

Verify the account is tracked in the GoCSM dashboard


Support


Version 1.0 · Last updated 2026-05-17