Skip to main content
Glama
MCP SQLite Server

MCP SQLite Server

by obiokoye

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DB_PATHNoSQLite file to serve, relative to the project folder. The default file is created with sample data if missing.data/shop.db
MAX_ROWSNoRow cap per read_query (max 1000).100
ALLOW_WRITESNoSet to true to add the write_query tool and open a writable connection.false

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Tools for exploring a SQLite database. Call list_tables first, then describe_table, then read_query with a single SELECT. Results are capped at 100 rows. The database is read-only.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_tablesA

List every table in the database with its row count.

describe_tableB

Show a table's columns (name, type, primary key, not null) and foreign keys.

read_queryA

Run ONE SQLite SELECT (or WITH ... SELECT) statement and get rows back as JSON. At most 100 rows are returned; use LIMIT, GROUP BY and aggregates for large tables.

Prompts

Interactive templates invoked by user choice

NameDescription
explore-dataAsk a business question; the assistant explores the schema and answers with SQL.

Resources

Contextual data attached and managed by the client

NameDescription
schemaCREATE statements for every table and index

TDQS

A3.8/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a clearly distinct step of database exploration: enumerating tables, inspecting a single table's schema, and running a query. There is no overlap between schema metadata retrieval and row retrieval, and the descriptions reinforce the boundaries.

Naming Consistency5/5

All three names follow a clean verb_noun snake_case pattern (list_tables, describe_table, read_query), with distinct verbs that map directly to their actions.

Tool Count4/5

Three tools is minimal but well-matched to a narrow read-only database inspection purpose; nothing is redundant. It sits at the thin edge of the ideal range, so a user wanting write access would find the surface small.

Completeness3/5

The read path is well covered (discover tables, inspect schema, query data), but there is no way to mutate data or run non-SELECT statements such as INSERT, UPDATE, DELETE, or DDL. Agents can explore but cannot modify the database, which is a notable gap for a general SQLite server.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues