GST MCP Server

Use GST's advisory tools (opens in new window) with your AI agents. Supercharge your analysis to accelerate and lower costs of decision-making.

What it does

Your analysts already screen targets, portfolio companies and deals with AI agents; connect those AI agents to GST's MCP server to accelerate assessment, benchmarking, and project administration.

Deal Screening

During initial screening, an analyst's agent calls the diligence agenda tool with the target's profile and returns a starter agenda the IC memo is built around, recovering 2 to 4 hours per screened deal.

Cost Benchmarking

A portfolio operating partner benchmarks total technology spend against stage-adjusted ranges and prices the carrying cost of technical debt, turning "engineering feels slow" into a number the board can act on.

Regulatory Exposure

Before bidding on a healthtech target, an agent scopes which frameworks are in play by jurisdiction and effective date, so counsel starts from an exposure list instead of an open question.

Programmatic Access

A client's internal tooling (Retool, a Slack bot, a custom dashboard) calls the server directly, treating GST's frameworks as a managed API rather than a site somebody has to visit.

What's exposed

The server implements all three MCP server primitives: Tools, Resources, and Prompts. Together they give an agent what a good analyst needs on day one: instruments to run the numbers, the reference material to run them against, and a method for what order to do it in.

16
Tools
133
Resources
12
Prompts

Tools

16

The work an associate would otherwise build in a spreadsheet, or wait on an advisor to deliver. Each tool runs a GST model against your deal's parameters and returns figures defensible enough for an IC memo: a scoped diligence agenda, a cost benchmark, a debt estimate, a regulatory exposure list. The model invokes them on its own as the conversation calls for them, so an analyst asks in plain English instead of learning an API. Radar tools are granted separately. Tools in the MCP spec

Browse all 16 tools

Diligence agenda

Turns a target profile into a prioritized diligence agenda with scope and timeline estimates.

  • generate_diligence_agenda
Try it in a browser

Engagement history

Searches GST's engagement record by sector, deal type, stage, and scale, and lists the values each filter accepts.

  • search_portfolio
  • list_portfolio_facets
Try it in a browser

Regulatory exposure

Queries 123 regulatory frameworks by jurisdiction, category, and effective date.

  • search_regulations
  • list_regulation_facets
Try it in a browser

Infrastructure cost

Scores cloud cost governance maturity across six domains and returns a prioritized improvement list.

  • assess_infrastructure_cost_governance
Try it in a browser

Technology spend

Benchmarks total technology cost against stage-adjusted ranges and projects a 36-month trajectory.

  • compute_techpar
Try it in a browser

Technical debt

Estimates the annual carrying cost of technical debt from team size, salary, and delivery metrics.

  • estimate_tech_debt_cost
Try it in a browser

Information requests

Builds a fillable information request list, populates it from evidence already in hand, then ingests the completed file and checks every answer back to its source.

  • generate_information_request_list_xlsx
  • fill_information_request_list_xlsx
  • list_irl_requests
  • prepare_irl_body
  • validate_irl_provenance
  • compose_dossier_envelope
Try it in a browser

Radar search

Searches curated PE, M&A, and enterprise-technology intelligence, filtered by category and recency.

  • search_radar
  • get_latest_insights
Try it in a browser

Resources

133

The frameworks behind the numbers, readable in full. An agent working from GST's actual VDR taxonomy, diligence checklists, and regulation corpus grounds its answers in a published method rather than in whatever it absorbed during training, which is the difference between a citation you can check and a confident guess. The host application loads these as context, so they are in the conversation before the model needs them. Resources in the MCP spec

Browse all 133 resources

Library 4

The reference guides behind GST's diligence method, in full.

  • Business & Technology Architectures
  • Virtual Data Room Structure Guide
  • Information Request List
  • IRL to tool-input mapping
gst://library/<slug>

Regulatory frameworks 123

One document per framework, each with its requirements, penalties, and effective dates.

  • Data privacy
  • AI governance
  • Cybersecurity
  • Industry compliance
gst://regulations/<jurisdiction>/<framework>

Radar feeds 6

FYI carries GST-annotated highlights; Wire carries the full stream, whole or by category.

  • FYI, annotated highlights
  • Wire, all categories
  • PE & M&A
  • Enterprise tech
  • AI & automation
  • Security
gst://radar/fyi|wire/<category>

Prompts

12

Knowing which tool to call is not the hard part. Knowing the order is, and that is what a firm's experience actually buys. Each prompt captures a GST workflow as a sequence, so a first-year associate running a diligence kickoff follows the same progression a GST engagement would. They surface as slash commands in the client, chosen deliberately by a person rather than guessed at by a model. Prompts in the MCP spec

Browse all 12 prompts

Deal workflow

Open a diligence engagement, size up a target quickly, and produce the memos a deal team hands onward.

  • gst_diligence_kickoff
  • gst_target_quick_look
  • gst_diligence_handoff_memo
  • gst_comparable_engagements_memo

Information requests

Issue a request list to a target, populate it from evidence in hand, then sweep what comes back into a cited dossier without rekeying it.

  • gst_irl_create
  • gst_irl_populate
  • gst_irl_ingestion
  • gst_irl_sweep
  • gst_irl_extract

Review & briefing

Standing reviews: architecture by layer, regulatory exposure, and the day's radar.

  • gst_architecture_layer_review
  • gst_regulatory_exposure_brief
  • gst_radar_brief_today

Capability tiers

Tiers differ by who is using the server and how broadly, not by which tools you get. Scopes are set per client during provisioning.

Pilot

free-pilot

Evaluation access for a single team. Narrow scopes, radar excluded by default.

Request this tier →

Deal Team

Typical
paid

Production access for a deal team, invoiced per agreement.

Request this tier →

Firm

enterprise

Firm-wide access across multiple clients, compliance capabilities on request.

Request this tier →
Calls / min3060120
Calls / day3002,00010,000
Radar / min3510
Radar / day2050150

On these numbersThese are tunable, non-contractual capability ceilings, NOT ratified SLA quotas. They are abuse and capacity limits, adjustable per client, and nothing here is a promised allowance.

How access works

Provisioning
  • Access is operator-provisioned. There is no self-serve signup and no dynamic client registration. A client record is created by GST, with scopes and a tier assigned deliberately.
  • Radar tools are granted separately and are excluded from a typical grant, because they draw on a shared third-party research budget.
Authentication
  • Machine-to-machine clients authenticate with OAuth 2.1 client_credentials, using a client secret or a registered signing key.
  • The interactive authorization-code flow, for a person connecting Claude on the web or Desktop or another AI client, requires PKCE with S256, with no exceptions and no plaintext challenge.
Operations
  • A tamper-evident, hash-chained audit log with seven-year retention exists as built-and-tested capability. It is activated for a client whose contract requires it, as part of onboarding.
  • Operational health (dependency status, per-tool latency, request volume) is published on the status page.

For your engineers

One endpoint to configure, once a client record exists. Credentials arrive with provisioning.

Endpointhttps://mcp.globalstrategic.tech/mcp

Statushttps://status.mcp.globalstrategic.tech/

Guides

Four guides take a provisioned client from credential to everyday use: connect the server, drive it well, ingest a completed information request list, and look up any capability's contract.

Get started

Connector setup for Claude on the web and Claude Desktop: prerequisites, quick start, and how to verify the connection.

Open guide

Using the server

First query, prompt argument forms, pinned resources, and what each failure means.

Open guide

Advanced operations

Ingest a completed information request list and drive nine engines in one turn.

Open guide

Documentation

Every capability's contract: arguments, a worked example, what comes back, and which workflows use it.

Open reference

Request access

Tell GST who you are, what you are building, and roughly how much you expect to call. Provisioning is a conversation, not a signup form, which is also how scopes and a tier get set correctly the first time.

REQUEST_MCP_ACCESS()