MCP Connector · Now available
The GLG MCP connector gives any Model-Context-Protocol-compatible client access to the GLG Library and your GLG calls.
Capabilities
Once connected, your AI assistant can fetch your GLG data on demand — inline, in natural conversation, without leaving the tools you already use.
Access the GLG calls you’ve completed and any transcripts tied to them — without switching tabs
Review your engagement history, summarize recent work, and pull context for new briefs from completed consultations.
Pull from GLG Library transcripts where available, with full attribution. Subscription-gated, surfaced only on request.
Just ask
Once connected, your AI assistant can fetch your GLG data on demand — inline, in natural conversation, without leaving the tools you already use.
How it works
The connector implements the open Model Context Protocol. Any MCP-compatible client can connect to GLG with no custom integration on your side.
From your AI client's MCP settings, add the GLG connector endpoint. Exact steps vary by client — the docs cover the most common ones.
A browser window opens for you to authenticate with your GLG account. Credentials never reach your AI client — auth happens directly with GLG.
Your assistant can now query GLG on your behalf. Data is fetched live, scoped to your account. Query results are never stored and your full conversation stays private.
Security & access
Authenticated directly with GLG. Your credentials never touch the AI client.
GLG receives only the specific data requests needed to answer you — never your full conversation or your assistant’s responses.
GLG does not use your data to train or improve any AI model. Data handling by your AI provider is governed by your firm's agreement with that provider.
Setup, authentication, data access, and troubleshooting — everything you need to bring GLG into your AI workflow.