Skip to main content
Glama
Read-only SQLite MCP

Read-only SQLite MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ALLOW_WRITENoSet to 'true' to enable write_query (INSERT/UPDATE/DELETE/DDL). Equivalent to starting the server with the --allow-write flag. Defaults to read-only mode.false
SQLITE_MCP_DBSYesPath(s) to SQLite database files the server is allowed to access. Can be provided via the repeatable --db flag or this environment variable. At least one database path is required.

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_databasesA

List the SQLite databases this server is allowed to access.

list_tablesB

List tables and views in a database.

describe_tableB

Show a table's columns, types, keys and indexes.

table_statsB

Show row counts for every table in a database.

read_queryB

Run a read-only SQL query (SELECT / WITH / PRAGMA / EXPLAIN only). Results are capped.

sample_rowsC

Fetch a few example rows from a table.

export_csvC

Run a read-only query and return the result as CSV text.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 7 tools

Disambiguation4/5

Each tool targets a distinct inspection level (databases, tables, columns, row counts, sample data) and descriptions make the boundaries clear. The only real overlap is read_query vs export_csv, which both execute a read-only query and differ only in output format, and sample_rows is a thin convenience wrapper around a SELECT.

Naming Consistency4/5

Six of seven tools follow a clear verb_noun pattern (list_databases, list_tables, describe_table, read_query, sample_rows, export_csv). table_stats breaks the pattern with a noun_noun form, but it is still readable and unambiguous.

Tool Count5/5

Seven tools is well-scoped for a read-only database inspection server. Every tool covers a distinct exploration step with no filler, and nothing feels missing from the count perspective.

Completeness4/5

The surface covers the full read-only lifecycle: discover databases, enumerate tables, inspect schema, gauge size, and pull sample or exported data. Minor gaps remain, such as finding which tables contain a given column name or dumping a full schema, but agents can work around these with read_query.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues