Summary
A research dataset you interrogate in SQL instead of through whatever endpoints someone anticipated.
The query surface is whatever the tables allow rather than a fixed set of lookups, which is the difference between answering the question you have and the question the API author expected. opengenes_db_query says so directly: check the schema and example tools before the first call. Three tools is the whole server, and all three read — there is no write path into the dataset.
What it is
A SQL interface to the OpenGenes database, with schema and worked examples alongside the query tool.
What you get
- Arbitrary SQL against the OpenGenes tables, covering genes involved in longevity, lifespan extension experiments on model organisms, and changes in humans and other organisms with aging
- The database schema, so a query can be written against the real column names
- A list of example SQL queries to start from
Requirements
MCP_TRANSPORT selects how the server is reached. No account, key or database credential is configured, and no connection string is asked for.
Setup effort
One command — uvx opengenes-mcp