Skip to content

Connect Claude and ChatGPT (MCP)

Workstation runs an MCP server, so AI apps can work with your CRM in plain language: “find the Acme deal and move it to Negotiation”, “log a call with Sara about the renewal”, “which of my tickets breach SLA today?”.

The app signs in as you. It sees only what your own role and record visibility allow, and it can never do more than you can in Workstation.

https://workstation.repzo.com/mcp
  1. In Claude, open Settings → Connectors and click Add custom connector.
  2. Name it Repzo Workstation and paste the server URL above. Leave the OAuth fields empty.
  3. Click Connect. Workstation opens in your browser.
  4. Pick the workspace, choose Full access or Read only, and click Allow access.

The same connector then works in Claude on the web, the desktop app and mobile.

  1. In ChatGPT, open Settings → Apps & Connectors and create a connector (your workspace admin may need to turn on developer mode first).
  2. Paste the server URL above and choose OAuth as the authentication.
  3. Approve the request in Workstation the same way.

ChatGPT’s deep research uses the search and fetch tools, so it can cite your records with links back to Workstation.

Connect Claude Code, Cursor and other clients

Section titled “Connect Claude Code, Cursor and other clients”

Any client that supports remote MCP servers with OAuth can connect to the same URL. For Claude Code:

Terminal window
claude mcp add --transport http repzo https://workstation.repzo.com/mcp

Then run /mcp in Claude Code and choose Authenticate.

Scripts and CI that can’t open a browser can send a Developer App key instead: Authorization: Bearer foxa-…. See Developer API and CLI.

The server offers a small set of everyday tools, and a way to reach everything else in the public API:

Tool What it’s for
search, fetch Find contacts, accounts, deals, tickets, invoices and more by name, email or number, then read one in full
get_workspace_context Who you are, which workspace, and what the connection may do
list_contacts, list_accounts, list_deals, list_activities, list_tickets Filter records by owner, stage, status, dates and custom properties
get_timeline Everything that happened on a record
get_properties, get_reference_data Field definitions and workspace ids (users, pipelines and stages, sources…)
create_…, update_… Contacts, accounts, deals, activities (linked to their records) and tickets
add_comment Comment on a record for your team
find_actions, run_action, run_write_action Search the rest of the API (products, invoices, accounting, appointments, inbox, Send, reports, settings…) and run what fits

When the AI needs something the everyday tools don’t cover, it describes the goal to find_actions (“record a payment on an invoice”) and gets back the matching actions with their inputs.

  • Read only connections get no tools that change data.
  • Claude and ChatGPT ask you before every change. The server also tells them which actions can’t be undone or reach outside Workstation (sending messages, placing calls, launching campaigns), so they confirm those first.
  • Every change goes through the same checks, validation and activity log as the web app.
  • See and disconnect your AI apps and CLI sessions in Settings → Profile → Signed-in apps. Disconnecting stops the app at once. Changing your password disconnects them all.
  • Transport: Streamable HTTP, stateless. Send JSON-RPC with POST /mcp.
  • Discovery: GET /.well-known/oauth-protected-resource/mcp and GET /.well-known/oauth-authorization-server.
  • OAuth 2.1: authorization code with PKCE (S256), public clients only. Clients register with Dynamic Client Registration at POST /oauth/register, or identify themselves with a Client ID Metadata Document. Authorization responses include iss.
  • Tokens: the same short-lived foxu-* access tokens and rotating foxr-* refresh tokens as the Repzo CLI, from POST /api/v1/oauth/token.
  • Command list: GET /api/v1/cli/manifest.json lists every API operation with its CLI command name, inputs and notes.