Datasette MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATASETTE_MCP_CONFIG | No | Path to configuration file. Automatically searched if not set. |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_sqlC | Execute SQL query against a Datasette instance. |
| search_tableC | Full-text search within a table using Datasette's search functionality. |
| list_instancesA | List all configured Datasette instances. Returns: List of instances with their configuration details |
| list_databasesB | List all databases in a Datasette instance. |
| describe_databaseA | Get complete database metadata including all table schemas and column information. |
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 has a clearly distinct purpose: describing a database, executing SQL, listing databases, listing instances, and searching a table. There is no functional overlap.
All tool names follow a consistent verb_noun pattern in snake_case (describe_database, execute_sql, list_databases, list_instances, search_table).
With 5 tools, the server is well-scoped for interacting with a Datasette instance, covering metadata retrieval, SQL execution, and full-text search without unnecessary complexity.
The tool surface covers all core operations expected for a Datasette instance: listing instances and databases, describing schemas, executing arbitrary SQL, and performing full-text search. No obvious gaps for the intended use case.