Webget MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEBGET_BASE_URL | No | Webget API base URL (change for staging environments) | https://saas.increff.com/webget/in/api |
| WEBGET_CHROME_PATH | No | Chrome binary location on Linux/Windows (macOS default is used otherwise) | /Applications/Google Chrome.app/Contents/MacOS/Google Chrome |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_databasesA | List database servers the user can access, with dbId and dbType (MYSQL or MONGODB). |
| get_schemasA | List schemas (MySQL) or databases (MongoDB) on a server. Use list_databases first to get dbId. |
| get_tablesA | List tables->columns (MySQL) or collections->fields (MongoDB) in one schema. Returns a map of object name to column/field list. |
| run_queryA | Run a SQL or MongoDB query against a server. MySQL: full SQL, must start with 'use ;' or reference schema-qualified names. Returns TSV text. MongoDB: db.collection.find()/aggregate() style query, returns JSON text. |
| loginA | Open browser for Webget Google login. Only needed if calls fail with auth errors; normally the first API call auto-triggers this. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct level of database interaction: servers, schemas, tables, query execution, and authentication. No two tools overlap in purpose, and the descriptions clearly delineate their roles.
All tool names follow a consistent verb_noun snake_case pattern (list_databases, get_schemas, get_tables, run_query). The single exception 'login' is a standard verb-only action but does not create confusion, and the overall style is uniform.
Five tools is ideal for a database access server: three for navigation, one for execution, and one for auth. Each tool serves a necessary purpose without redundancy or bloat.
The toolset covers the full discovery-to-query workflow across both MySQL and MongoDB. It provides schema enumeration, table/collection inspection, and arbitrary query execution, with login as a fallback for auth. There are no obvious gaps for the stated purpose.