Skip to main content
Glama
increff-jatin-gupta

webget-mcp

by increff-jatin-gupta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
webget_list_databasesA

Lists the database server names available in Increff Webget's SQL Query Editor (the same dropdown as https://saas.increff.com/webget/in/sql). Use the returned name as the database argument to webget_run_query. Set refresh: true to re-scrape the live list instead of using the bundled snapshot (slower, but catches newly added servers, and is necessary right after a fresh install since the bundled snapshot starts empty).

webget_run_queryA

Executes a read-only SQL query against a webget database server (a read-replica MySQL DB, per company policy) and returns the result as rows/columns. Only SELECT-style statements are allowed; use webget_list_databases first to find the exact database name. Requires a prior login (run npm run login in the webget-mcp project once) and inherits webget's own row/size/time limits. Before running, the human is always shown the exact query and must explicitly allow it — this is enforced by the server itself and cannot be bypassed by an "always allow" client setting.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 2 tools

Disambiguation5/5

The two tools serve clearly distinct purposes: one lists available databases, the other executes queries against them. There is a clear dependency and no overlap in functionality.

Naming Consistency4/5

Both tools follow the `webget_` prefix and use verb_noun style: `list_databases` and `run_query`. Minor deviation: `list_databases` uses a plural noun while `run_query` uses a singular noun, but the pattern is consistent and predictable.

Tool Count3/5

With only two tools, the set is minimal but appropriate for a focused purpose: listing databases and running queries. It feels slightly thin but is sufficient for the core functionality without unnecessary bloat.

Completeness4/5

The surface covers the primary workflows: discovering databases and executing read-only queries. Minor gaps exist such as no tool to inspect schema or query metadata, but these are not strictly necessary for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources