Glympt MCP server

Glympt MCP

Glympt MCP exposes paid technographic enrichment, filtered prospect search, saved lists and CSV snapshots through the official TypeScript SDK v2. It supports the stateless 2026-07-28 protocol and the SDK’s 2025-11-25 compatibility mode.

Both connection paths are implemented: API-key stdio for developer clients, and hosted OAuth with explicit Glympt workspace consent. Production API-key workflows, hosted OAuth discovery/refresh/disconnect, and actual ChatGPT, Claude web and Codex usage calls have been verified. Cursor desktop 3.23.12 also passed OAuth, 14-tool discovery and an actual usage call after the loopback registration fix was deployed. Claude Code remains unverified.

Hosted OAuth

Add this Streamable HTTP URL to a client that supports OAuth:

https://mcp.glympt.com/mcp

Sign into Glympt, choose an API-enabled paid workspace and consent to the requested scopes. Each client receives its own workspace authorization. Disconnect it under Account settings → MCP connections to revoke its access and refresh tokens.

Hosted OAuth requires no local installation or customer API key. Start with “Show my Glympt query balance and workspace limits.” See the public setup guide for client-specific steps and current verification limits.

Local stdio adapter

Requires Node.js 22 or newer. Create a scoped API key in Glympt API key settings for an API-enabled paid workspace. Pro, Business and eligible custom plans support API access. Free CSV trial credits do not grant API or MCP access.

Put GLYMPTAPIKEY in the server process environment using your client's private credential settings, then run:

npx --yes @glympt/mcp@0.1.0

The executable is glympt-mcp. For an explicit persistent installation:

npm install --global @glympt/mcp@0.1.0
glympt-mcp

A typical stdio client configuration is:

{
  "mcpServers": {
    "glympt": {
      "command": "npx",
      "args": ["--yes", "@glympt/mcp@0.1.0"],
      "env": {
        "GLYMPT_API_KEY": "tk_live_replace_with_your_key"
      }
    }
  }
}

The placeholder is not a working credential. Store real keys only in private local configuration, never in shared repositories or chat prompts. The package does not automatically read .env files. Revoke the dashboard key to disconnect this adapter.

Missing configuration exits with a useful error on stderr. Runtime diagnostics use stderr; stdout carries MCP protocol messages only. No tsx, source checkout or development dependencies are required to run the npm package. Detailed stdio setup.

Build and verify from source

Requires Node.js 22+ and pnpm 10.28.2.

pnpm install --frozen-lockfile
pnpm check
pnpm lint
pnpm test
pnpm build
pnpm test:package

Tests use a mock paid API and real SDK clients. Socket tests need loopback access in restricted environments. Package verification inspects the actual tarball, installs only production dependencies into a clean temporary directory, and checks the installed executable and npx command under modern and legacy protocols. These tests spend no production credits.

Shortened. The full README is on GitHub.