F
license-
qualityC
maintenanceAutomatically scans SQLite databases and generates typed CRUD tools for each table, allowing natural language database interaction without exposing raw SQL.
Last updated
mcp-server
by com.exoquery
Server Details
Kotlin compile-time SQL library. Docs, code validation, and SQLite execution tools.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.6/5.0
Tool DescriptionsA
Average 4.1/5 across 6 of 6 tools scored. Lowest: 3.2/5.
Server CoherenceB
Disambiguation2/5
There is significant overlap between tools, particularly getExoQueryDocs and getExoQueryDocsMulti which both retrieve documentation with only a single vs. multiple files distinction, and validateAndRunExoquery and validateExoquery which appear to be identical duplicates. This creates confusion about which tool to use for documentation retrieval and query validation, as their purposes are not clearly distinct.
Naming Consistency3/5
The naming is mixed with no clear pattern: getExoQueryDocs and getExoQueryDocsMulti use camelCase, listExoQueryDocs uses camelCase but starts with 'list', runRawSql uses camelCase, and validateAndRunExoquery and validateExoquery use camelCase but are nearly identical. While all are camelCase, the verb choices (get, list, run, validate) are inconsistent in style and some names are overly long or redundant.
Tool Count4/5
With 6 tools, the count is reasonable for a server focused on ExoQuery documentation and SQL validation. However, the presence of duplicate or highly overlapping tools (e.g., two documentation retrieval tools and two validation tools) suggests the count could be optimized by merging or removing redundancies, slightly reducing appropriateness.
Completeness4/5
The tool set covers key areas for ExoQuery: documentation access (single and multi-file), listing documentation, raw SQL execution, and ExoQuery code validation/execution. However, there are minor gaps such as no tool for schema management or direct database connection handling, and the duplication in validation tools creates redundancy rather than extending coverage.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Flicense-qualityDmaintenanceProvides tools for interacting with relational databases (PostgreSQL, MySQL, SQLite), enabling SQL queries, schema inspection, and migration execution.Last updated
- AlicenseAqualityAmaintenanceOperations toolchain for SQLite, Cloudflare D1, and Turso. Every command is available as both a CLI and an MCP tool: inspect, diff, migrate, monitor, back up, and repair databases. 22 stdio tools, read-only by default.Last updated141AGPL 3.0
- Alicense-qualityFmaintenanceRead-only MCP server for SQL databases (SQL Server, Postgres, SQLite) with multi-server support and three-layer safety using AST validation and linting.Last updatedMIT