Turso documents a built-in Model Context Protocol server in the Turso CLI (`tursodb`) at docs.turso.tech/cli/mcp-server, started with `tursodb /path/to/database.db --mcp` over stdio JSON-RPC. Tools include `open_database`, `current_database`, `list_tables`, `describe_table`, `execute_query` (SELECT-only), `insert_data`, `update_data`, `delete_data`, and `schema_change` (CREATE/ALTER/DROP) per the Mintlify MCP reference. Turso's launch blog at turso.tech/blog/introducing-the-turso-database-mcp-server shows Claude Desktop and Claude Code configuration via `claude mcp add` with the same `--mcp` flag—no separate npm package required for local embedded databases.
Use cases
- Let Cursor agents inspect and mutate local SQLite schemas during feature work
- Prototype agent SQL workflows on `:memory:` databases without cloud credentials
- Teach MCP tool boundaries with read-only SELECT vs mutating insert/update tools
- Pair embedded Turso files with offline coding agents on laptops
- Register per-project databases via `claude mcp add` for Claude Code sessions
Key features
- Cursor
- Claude Desktop
- Claude Code
- VS Code
- Codex
Frequently Asked Questions
- Does this MCP cover Turso Cloud remote databases?
- Official docs focus on local `tursodb --mcp`; hosted Turso Cloud access may use community MCP servers—verify against docs.turso.tech before production.
- Which statements can agents run?
- Turso splits tools: `execute_query` accepts SELECT only; inserts/updates/deletes/schema changes use dedicated tools with statement-type guards.
- Is a separate npm package required?
- No for embedded mode—the MCP ships inside `tursodb` per Turso's MCP server documentation.
Related
Related
3 Indexed items
Convex MCP Server
Convex documents a Model Context Protocol server shipped in the Convex CLI at docs.convex.dev/ai/convex-mcp-server, started locally with `npx -y convex@latest mcp start` over stdio after linking a project via `npx convex dev`. Tools include `status` (deployment selector), `tables` (declared and inferred schemas), `data` (paginated documents), `runOneoffQuery` (sandboxed read-only JS), `functionSpec`, `run` (invoke deployed functions), `logs`, `insights` (72-hour OCC and resource-limit health), and `envList`/`envGet`/`envSet`/`envRemove`. Flags such as `--prod`, `--preview-name`, `--deployment-name`, and `--disable-tools` restrict scope; production writes require `--dangerously-enable-production-deployments` per changelog defaults.
Weaviate MCP Server
Weaviate documents a built-in Model Context Protocol server in the main `weaviate/weaviate` binary from v1.37.1 onward at docs.weaviate.io/weaviate/mcp/mcp-server, exposed as a Streamable HTTP endpoint at `/v1/mcp` on the same port as the REST API (default 8080). Enable with `MCP_SERVER_ENABLED=true`; optional `MCP_SERVER_WRITE_ACCESS_ENABLED=true` registers `weaviate-objects-upsert`. Tools include `weaviate-collections-get-config`, `weaviate-tenants-list`, `weaviate-query-hybrid`, and `weaviate-objects-upsert` (write-gated). Authentication uses existing API keys/Bearer tokens with RBAC permissions `read_mcp`, `create_mcp`, and `update_mcp` per Weaviate 1.37 release notes. The standalone weaviate/mcp-server-weaviate repository is deprecated in favor of this built-in server.
Neo4j MCP Server
Neo4j documents an official Model Context Protocol server at neo4j.com/docs/mcp/current and in the neo4j/mcp repository. It gives MCP clients structured access to a Neo4j graph: get-schema introspects labels, relationship types, and property keys; read-cypher runs read-only Cypher checked with EXPLAIN and Neo4j query-type classification; write-cypher runs writes unless NEO4J_MCP_READ_ONLY=true; list-gds-procedures lists Graph Data Science procedures when GDS is installed. Prerequisites are a running Aura, Neo4j Desktop, or self-managed database plus the APOC plugin. Local clients use stdio via uvx neo4j-mcp-server or the Homebrew/binary neo4j-mcp, with NEO4J_MCP_URI, NEO4J_MCP_USERNAME, NEO4J_MCP_PASSWORD, and NEO4J_MCP_DATABASE. Aura uses HTTP at https://<instance-id>.mcp-instances.neo4j.io after Tool authentication is enabled in the Aura console. Docs also describe an HTTP transport mode that takes URI and credentials per request and selects the database from the /db/{databaseName}/mcp path.