Integration guide

Get started with the GST MCP Server

Three steps between a provisioned credential and a connector Claude can call. Work down the page; each one tells you how to know it worked.

  1. Checkpoint 01
    Credential in hand

    A client record exists, with your tier and scopes set deliberately.

  2. Checkpoint 02
    Connector approved

    Claude, on the web or in Claude Desktop, lists the GST MCP tools in its connector menu.

  3. Checkpoint 03
    Capabilities resolved

    Tools, prompts and resources all appear by name, nothing missing.

01 Before you start

Access is operator-provisioned: there is no self-serve signup and no dynamic client registration. If you do not have a client record yet, that is the first step; everything below assumes credentials have arrived.

  • GST creates it with your tier and scopes set deliberately. Ask for radar tools explicitly: they are granted separately.

    Request access →

  • It arrives over a secure channel. Paste the key at the consent page if you are working interactively; take the OAuth 2.1 client_credentials id and secret if you are building headless.

    Keep it in a password manager, never in a committed config file.

  • Either client works, and a connector added in one appears in the other. As of September 2026 custom connectors are available on every Claude plan, with the Free plan allowing one; Claude's help center has the current matrix. On Desktop, run the current version first. Skip any bridge or proxy: the server speaks OAuth 2.1 natively.

    On a Team or Enterprise plan an organization Owner adds the connector under Organization settings. Ask them before you start.

Building a headless integration?The Quick Start below is the interactive path. Pipelines, Slack bots and internal dashboards authenticate machine-to-machine with client_credentials against the same endpoint; the wire detail lives in the technical documentation.

02 Quick Start

Claude's native custom connector flow, the same on claude.ai and in Claude Desktop. Four steps; the only value you type is the endpoint URL. Where web and Desktop differ, the step says so.

  1. 01

    Open the connector dialog

    In the chat input, open the + menu and choose Connectors → Add connector → Add custom connector. Settings → Connectors reaches the same dialog, and Claude Desktop has the same menu. You do not need a client ID or secret: Claude registers itself with the server.

  2. 02

    Enter the GST endpoint

    Name the connector and paste the production URL. Call it GST MCP to match the rest of this guide, since you address the connector by that name in a prompt. Choose Continue: Claude checks the server, then shows an Authentication and an OAuth client section with both settings already detected. Leave those defaults and choose Add.

    https://mcp.globalstrategic.tech/mcp
    GST MCP
    See the connector added
    Screen capture: adding the custom connector on claude.ai. The dialog is the same in Claude Desktop
  3. 03

    Approve at the consent page

    A browser tab opens on the GST consent page, shown below. It asks for one thing: your provisioned key. Paste it into the field and approve. That paste is how the grant learns who you are; your access is bounded by the scopes on your record. Tokens last an hour and refresh silently, and the same connector then works on web, Desktop and mobile.

    If the page comes back with That MCP key was not recognized, paste again from your password manager rather than retyping. Deny returns you to Claude with nothing granted.

    See the consent round trip
    Screen capture, at twice the recorded speed: approving at the consent page and returning to Claude
    See the consent page
    The GST consent page: a heading reading Authorize access to the GST MCP server, a list of the six scopes Claude is requesting with a one-line description of each, one password field labelled Your MCP key, and Approve and Deny buttons
    The GST consent page as Claude opens it, listing the scopes the connector requests. Approving grants those, bounded by your key's own scopes
  4. 04

    Confirm the tools are there

    On the web, start a new conversation; no restart is needed. In Claude Desktop, quit fully first (it stays in the tray) and relaunch. The chat input's + → Connectors menu should list GST MCP with the GST tools and prompts under it.

03 Verify the connection

Two checks. If both pass, the client is talking to the server and every capability resolved.

  • + → Connectors shows GST MCP, toggled on and without a warning badge, as below.

    See it in Claude Desktop
    Screen capture: the connector list with GST MCP enabled, in Claude Desktop
    See it on claude.ai
    Screen capture: the same menu on claude.ai, with GST MCP toggled on

  • Open Add from GST MCP and expect the twelve GST prompts by name, with the resource library below them.

    See how it works
    Screen capture: the prompt list, then the resource library

Server-side health (dependency status, per-tool latency, request volume) is published at status.mcp.globalstrategic.tech. Check it before assuming your own config is at fault.

Neither check passing?The five failures a first connection runs into, and what each one means, are catalogued under Troubleshooting in the practitioner guide.

04 Where to go next

Three routes on from a working connector: everyday use, the wire detail, and a wider grant.

Using the GST MCP Server

First query, prompt argument forms, and pinned resources.

Open guide

Technical documentation

Tool and prompt reference, OAuth scopes, and rate limits.

Read docs

Widen your access

Add radar scope, raise a tier, or provision a client.

Contact GST