Connect your assistant to website technology data.

1. Use a Glympt workspace with API access. Pro includes 500 monthly credits; Business includes 5,000. Free includes a dashboard CSV trial, but has no MCP or API access.
2. Add the URL below in your client using Streamable HTTP and OAuth.
3. Sign in to Glympt, select an eligible workspace, and review the requested permissions.
4. Ask: “Show my Glympt query balance and workspace limits.” This calls get_usage without spending query credits.

https://mcp.glympt.com/mcp

The hosted endpoint uses OAuth. Leave custom bearer headers empty and follow sign-in. A dashboard API key belongs in the local adapter, not the hosted URL.

Public beta verification · October 4, 2026: production API-key testing passed all 14 tools. Hosted OAuth discovery, token refresh, and Codex disconnect checks passed. ChatGPT, Claude web, Codex, and Cursor desktop completed live usage checks. These application checks cover connection and balance reads; the full workflow suite was tested separately.

1. Open Settings → Security and login and enable Developer mode if your account and workspace policy allow it.
2. Open Plugins → Add → Create custom MCP server. Enter a name such as Glympt, a short description, and the hosted MCP URL.
3. Choose OAuth. Allow automatic discovery to finish; advanced settings should select Client ID Metadata Document (CIMD) without a manual client ID or secret. Complete Glympt sign-in, workspace selection, and consent.
4. Review the discovered tools. Select Try in chat, keep Glympt attached to the conversation, and ask for your query balance.

After tool changes, refresh the connection metadata and start a new conversation. See OpenAI’s connection guide.

For Claude’s custom remote connectors, add the hosted URL in the connector settings and complete Glympt consent. Availability and administrator approval depend on the Claude plan and workspace. For Claude Code:

claude mcp add --transport http glympt https://mcp.glympt.com/mcp

Run /mcp in Claude Code and authenticate the Glympt server. Ask for your query balance to verify the connection. Claude web has passed this check; Claude Code CLI remains unverified. See Claude Code’s MCP guide.

codex mcp add glympt --url https://mcp.glympt.com/mcp
codex mcp login glympt

Finish browser sign-in and consent. Use /mcp in a new Codex session to inspect the connection, then ask for your query balance. See Codex’s MCP guide.

Add this entry to your project’s .cursor/mcp.json or your global ~/.cursor/mcp.json. Merge it with your existing servers.

{
  "mcpServers": {
    "glympt": {
      "url": "https://mcp.glympt.com/mcp"
    }
  }
}

Open Cursor’s MCP settings, connect Glympt, and complete the OAuth flow. Enable the server’s tools, use Agent mode, and ask for your query balance. Ask mode may block MCP tool calls. See Cursor’s MCP guide.

The MIT-licensed @glympt/[email protected] npm adapter runs without a source checkout. It requires Node.js 22 or newer and a scoped key from an API-enabled paid workspace. Create the key in API key settings and provide it as GLYMPT_API_KEY in the adapter’s private process environment.

npx --yes @glympt/[email protected]

For Codex, merge this table into your private ~/.codex/config.toml and start Codex with the key in its environment. env_vars forwards the key to the adapter.

[mcp_servers.glympt-local]
command = "npx"
args = ["--yes", "@glympt/[email protected]"]
env_vars = ["GLYMPT_API_KEY"]

Alternatively, install the package in a private directory and save the key in a private environment file outside your repository. Restrict the file to your user; the adapter does not load .env automatically.

GLYMPT_API_KEY=replace_with_your_own_key
GLYMPT_API_BASE_URL=https://api.glympt.com

npm install --prefix /absolute/private/glympt-adapter @glympt/[email protected]
codex mcp add glympt-local -- node --env-file=/absolute/private/glympt.env /absolute/private/glympt-adapter/node_modules/@glympt/mcp/dist/stdio.js

For JSON-configured stdio clients, use npx as the command and ["--yes", "@glympt/[email protected]"] as its arguments. Supply the key through your private global configuration or process environment. Restart the client and inspect its tools. Revoke the API key to disconnect. Keep credentials out of chat prompts, source control, and shared configuration.

Both connection methods are published in the official MCP Registry entry. See the public adapter source and directory submission status for details.

Show my Glympt query balance. Find up to 10 Shopify websites likely in Germany. Include scan timestamps, confidence, and the geography caveat. Ask before enriching any domains.

Queued enrichment returns job or batch IDs. Poll those IDs to continue. Mutation tools require an idempotencyKey: reuse the same key and identical input when recovering a timeout or lost response. A new key can create a new billable operation.

CSV exports expire after seven days. The assistant retrieves authenticated base64 chunks in byte-offset order and decodes them into a file if its host supports file creation. There is no public download URL. Data shows detected technologies and estimated geography; it does not include contact or firmographic enrichment.

• Single enrichment uses one query credit. Batches charge each unique normalized domain, including cache hits. Duplicate rows in a batch do not double-charge; separate observed subdomains may count separately.
• Polling, search, balance checks, list actions, and exports use no query credits. All product requests count toward your workspace’s API rate limit.
• Hard technical failures with no usable result are refunded under the normal scan policy. A valid fetch that detects no technologies still consumes a credit. A client-side timeout alone does not prove a failure or refund; check the original operation.
• Hosted consent binds access to the selected workspace. Requested scopes control enrichment, batches, list read/write, and exports. offline_access allows token refresh, subject to session and grant validity.
• Disconnect hosted clients in account settings → MCP connections. This revokes their access and refresh tokens. The local adapter is disconnected by revoking its API key.

Still stuck? Contact support with the client version, tool name, and request ID. Keep API keys, access tokens, authorization codes, and private CSV contents out of the report.