
Glasser
ai.glasserPublished by glasser.aiOfficial publisherv0.1.3Updated Oct 24, 2026
One key to 1,000+ paid data APIs: enrichment, SEO/SERP, scraping, places, news. Pay per call.
Overview
Remote MCP gateway that lets an assistant search, inspect and run 1,000+ paid data APIs (enrichment, SEO/SERP, scraping, places, news) on a pay-per-call…
- What you can do
- Search the catalog of paid data APIs and inspect an endpoint's price and charge clauses before use
- Run an endpoint as a Run and get its result plus the charge it incurred
- List, retrieve and stop past Runs
- Check the Workspace balance
- Follow a bundled workflow skill that searches, inspects, runs and reports the charge
- When to use it
- Useful when an assistant needs paid third-party data such as enrichment, SEO/SERP, scraping, places or news without signing separate contracts with each provider, and you are comfortable with per-call spending from a prepaid Workspace balance.
- Requirements
- Remote MCP endpoint at api.glasser.ai/mcp; OAuth sign-in is required and opens a browser on the first tool call, where you pick the Workspace whose balance may be spent. Clients that cannot open a browser can send a Key instead. An optional CLI is installed from npm and uses the same Key and balance.
Installation
In SourceWeft
- Open Glasser in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.glasser%2Fglasser/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"glasser": {
"type": "http",
"url": "https://api.glasser.ai/mcp?utm_source=mcp-registry&utm_medium=mcp_directory"
}
}
}README
Glasser plugins
One key, no contract, pay per call, across paid APIs bought wholesale.
Official agent plugins for Glasser. This repository is a distribution package: configuration plus markdown. It ships no executable code and no install script.
Works with Cursor, Claude Code, Grok Build, and any client that reads the Agent Plugins format.
Install
Cursor
Search glasser under Customize → Plugins, or open the listing on the
Cursor Marketplace. The first call opens
your browser to sign in.
Claude Code
Any supported agent
Detects every agent installed on the machine and installs to all of them.
Grok Build
/marketplace inside Grok Build once the plugin is listed. Until then, add
this repository under [[marketplace.sources]] in ~/.grok/config.toml; the
Grok Build docs have the syntax.
MCP only
Any MCP client that signs in with OAuth needs just the URL:
Clients that cannot open a browser can send a Key instead — client-by-client snippets: https://glasser.ai/docs/mcp-server
Authentication
Nothing to create or paste. The first tool call opens your browser: sign in
to Glasser, choose the Workspace whose balance the agent may spend, and click
Allow. That mints a Key named MCP · <client> for that Workspace — it is
listed at https://app.glasser.ai/keys like any other Key, and revoking it
there disconnects the client. Disconnecting inside the client does not
revoke the Key; the next sign-in reuses it.
The optional CLI authenticates on its own with glasser login (browser
device authorization). That stores a Key for the CLI only.
What you get
MCP tools — search, inspect, run, runs_get, runs_list,
runs_stop, balance. Only run creates a Run and charges the Workspace
balance; the other tools read the catalog, past Runs and the Balance. Every
Run reports its own charge.
Skill — the workflow the agent follows: search the catalog, inspect an Endpoint's Price and charge clauses before running, run, then report the result and the charge. It uses the MCP tools by default and the CLI for results too large for the context window, for scripting and for CI.
Rule (Cursor only) — always-on spending guardrails.
Optional CLI — npm install -g @glasser-ai/cli. Same Key, same
Workspace, same Balance. Docs: https://glasser.ai/docs/cli
Network endpoints and credentials
For reviewers and anyone auditing what this plugin reaches.
Nothing in this repository executes. The plugin sends no telemetry of its own. The service behind these endpoints is governed by Glasser's terms of service and privacy policy.
Repository layout
Releasing: see DISTRIBUTION.md.
License
MIT — see LICENSE. The Glasser service has its own terms.
Source: README.md at commit 991badf
Tools
0Version history
2- v0.1.3LatestOct 12, 2026
- v0.1.2Sep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts