Skip to main content
Glama

Related Servers

Alternatives to Portward

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants and LLM agents to query operational databases through a read-only MCP gateway with table whitelisting, automatic row limits, sensitive-data masking, and audit logging.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude or any MCP client to explore and query a SQL database in natural language through a governed, read-only layer. Every request is checked against per-user table permissions, column masking, enforced row limits, daily quotas, and a full audit log.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients such as Claude, ChatGPT and Cursor to answer business questions about sales, customers, orders and spreadsheets in natural language by reading live Postgres/SQLite databases and Google Sheets without exporting files or gaining write access. Guardrails include AST-based read-only SQL validation, read-only database roles, row/byte caps with pagination, PII masking, bearer-token auth for remote HTTP use, and a full JSONL audit log of every tool call.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      This local, read-only MCP server allows AI to interact with diverse data sources, including SQLite, CSV, Excel, Postgres, and MySQL. It enables controlled data viewing within a chat environment while strictly enforcing read-only access and user-defined visibility rules.
      77
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to securely explore and query connected databases and business tools through MCP, with access controls, semantic schema metadata, memory, and streaming or CSV export of large results.
      603 PyPI
      8
      Apache 2.0

    TDQS

    B3.2/5.0

    Scored across 55 tools

    Disambiguation3/5

    Many tools overlap in purpose: set_note vs column_note, block vs keep_from_claude, rerun vs run_saved vs tweak, history vs saved_pulls vs kept_rows, and share vs share_confirm vs share_sign_in vs share_link/share_mail. The rich descriptions help separate them (and many are marked app-only), but from the agent's vantage the set contains several near-duplicates that require careful reading to disambiguate.

    Naming Consistency3/5

    Most tools use verb_noun (set_note, save_pull, add_source, list_rules), but a large minority are bare verbs (block, share, query, rerun, compare, tweak, export) or bare nouns (history, lineage, shares, account_status, saved_pulls). The conventions are readable but mixed, and pairs like share/shares and keep_rows/kept_rows are easy to confuse.

    Tool Count2/5

    55 tools is far past what an agent can comfortably navigate, and much of the count comes from ~14 app-only panel/UI tools (panel_rows, put_in_chat, value_source, share_link, share_mail, usage_seen, column_menu, level_preview, etc.) that the model never invokes. The real model-facing surface is closer to 30-35, still heavy for the domain.

    Completeness4/5

    Coverage is unusually thorough: source connect/browse/test/remove, read-only query, pull history/rerun/tweak/compare/lineage, saved pulls, block rules, sharing lifecycle, account, usage counts, secrets, exports, and row-keeping. Minor gaps remain, e.g. no delete/rename for saved pulls or history entries, and no dedicated tool for viewing or managing stored definitions (only free-text notes/assumptions).

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues