Skip to main content
Glama
Himanshu-Agg12

mcp-mysql-lens

by Himanshu-Agg12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-mysql-lens

Related Servers

  • mysql-mcp

    qxduddes
    F
    license
    A
    quality
    A
    maintenance
    Security-hardened, read-only MySQL MCP server that enables safe, read-only access to MySQL databases for running SELECT queries, exploring schemas, and sampling data via MCP clients.
    9
    -

  • mcp-database

    AimanFadillah
    A
    license
    A
    quality
    C
    maintenance
    Read-only MySQL/MariaDB MCP server for running SELECT queries safely, with automatic read-only enforcement and query limits.
    3
    3 npm
    MIT

  • mysql-mcp

    rlembo06
    A
    license
    Not graded
    quality
    D
    maintenance
    A lightweight MCP server providing safe, read-only access to MySQL databases. It enables users to query multiple MySQL instances securely while preventing write operations.
    630 npm
    MIT

  • mysql-mcp

    zuozhu20100425
    A
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that enables secure, read-only access to MySQL databases with structured query tools, and optional opt-in write operations when explicitly enabled.
    997 npm
    MIT

  • mysql-query

    duxiaoben
    F
    license
    Not graded
    quality
    C
    maintenance
    A read-only MySQL query service that allows SELECT operations, listing tables, and viewing schemas via MCP protocol.
    -
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

A3.5/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: describe_table shows schema, execute_query runs SQL queries, list_databases lists databases, and list_tables lists tables. There is no overlap or ambiguity between these functions.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (describe_table, execute_query, list_databases, list_tables) with clear, descriptive verbs and nouns that match their functions.

Tool Count4/5

With 4 tools, the count is reasonable for a MySQL server interface, though it feels slightly thin as it lacks write operations (e.g., insert, update, delete) which are common in database contexts. However, the tools cover essential read and metadata functions well.

Completeness3/5

The tool surface covers read operations and metadata well (list databases/tables, describe schema, execute queries), but there are notable gaps: no write operations (insert, update, delete), no transaction management, and no user or permission management tools, which limits full database lifecycle coverage.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources