datasette/datasette-mcp

Adds a /-/mcp MCP server to any Datasette instance

About datasette-mcp

Adds a /-/mcp MCP server to any Datasette instance

Install this plugin in the same environment as Datasette.

Start Datasette as normal, then configure an MCP client to connect to:

The endpoint uses MCP Streamable HTTP and exposes three read-only tools by default:

- listdatabases lists the databases available to the current Datasette actor. - getdatabaseschema returns the complete SQL schema for a database, including tables, indexes, views, and triggers. - executesql executes one read-only SQL statement and returns structured columns, rows, and a truncation indicator.

Datasette database visibility and execute-sql permissions are enforced for every tool call. SQL uses the same validatesqlselect() and read-only Database.execute() path as Datasette's custom SQL interface.

Other Datasette plugins can add tools to this MCP server by implementing the registermcptools(datasette, mcp) plugin hook. The mcp argument is the MCPServer for that Datasette instance, so implementations use the MCP Python SDK's normal @mcp.tool() decorator:

The hook itself is synchronous because tools are registered while the MCP server is being constructed. Tool functions can be synchronous or asynchronous and can use all of the input, output, context, and annotation features provided by the MCP Python SDK.

Datasette-mcp registers listdatabases, getdatabaseschema, and executesql through this same hook.

To set up this plugin locally, first checkout the code. You can confirm it is available like this:

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/datasette--datasette-mcp.html)

Related MCP servers