Skip to main content
Glama
enesjakozh
isaacgounton

SQLite MCP Server

by isaacgounton
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

SQLite MCP サーバー

標準化されたインターフェースを通じて SQLite データベース操作を提供するモデル コンテキスト プロトコル (MCP) サーバー。

特徴

  • インメモリ SQLite データベース (ファイルベースのストレージ用に構成可能)

  • SQL 操作 (SELECT、INSERT、UPDATE、DELETE)

  • テーブル管理（CREATE、LIST、DESCRIBE）

  • ビジネスインサイトメモ追跡

  • 簡単に導入できるDockerサポート

Related MCP server: SQLite MCP Server

開発と展開

地域開発

# Install dependencies and build
npm install
npm start

Docker デプロイメント

# Build and run with Docker
docker build -t sqlite-mcp-server .
docker run -d --name sqlite-mcp sqlite-mcp-server

Nixpacks の展開

アプリケーションは、Railway、Coolify、Render などのプラットフォームで Nixpacks を使用して簡単にデプロイできます。

# Deploy with Nixpacks
nixpacks build . --name sqlite-mcp-server

プロジェクトには Dockerfile が含まれているため、追加の構成は必要ありません。

利用可能なツール

  1. read_query : SELECTクエリを実行する

  2. write_query : INSERT、UPDATE、または DELETE クエリを実行する

  3. create_table : 新しいテーブルを作成する

  4. list_tables : データベース内のすべてのテーブルを一覧表示する

  5. describe_table : テーブルのスキーマ情報を表示する

  6. append_insight : メモにビジネスインサイトを追加する

リモートサーバー接続

n8n で SSE を使用して接続するには:

  1. MCPクライアントノードを追加する

  2. SSE 接続を構成します。

    • SSE URL: http://localhost:3000/sse

    • メッセージ投稿エンドポイント: http://localhost:3000/messages

    • 追加のヘッダーは不要

使用例

// Create a table
await callTool('create_table', {
  query: 'CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT)'
});

// Insert data
await callTool('write_query', {
  query: 'INSERT INTO users (name) VALUES ("John Doe")'
});

// Query data
const result = await callTool('read_query', {
  query: 'SELECT * FROM users'
});

環境変数

デフォルトでは必要ありません。ファイルベースのストレージを使用する場合は、 src/index.tsのデータベースパスを変更してください。

貢献

  1. リポジトリをフォークする

  2. 機能ブランチを作成します（ git checkout -b feature/amazing-feature ）

  3. 変更をコミットします ( git commit -m 'Add some amazing feature' )

  4. ブランチにプッシュする ( git push origin feature/amazing-feature )

  5. プルリクエストを開く

ライセンス

ISC

Available Tools

1 tool
create_tableB

Create a new table in the database with a full CREATE TABLE SQL statement.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesCREATE TABLE SQL statement

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It fails to mention side effects (e.g., if table exists), permission requirements, or that it modifies state, which is critical for a write operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single efficient sentence with no wasted words, though minor expansion for behavioral details would improve it without harming conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with no output schema, the description covers the essential purpose but lacks details on error handling, permission requirements, or SQL dialect support.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already describes the 'query' parameter fully. The description adds the word 'full', implying a complete statement, but no additional meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'create', the resource 'table', and specifies it uses a full CREATE TABLE SQL statement, effectively distinguishing it from sibling tools like drop_table or list_tables.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for creating a table but provides no explicit guidance on when to use this tool versus alternatives like write_query, nor when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 6 tool updatesv1.1.0
    • Removedappend_insight
    • Removeddescribe_table
    • Removeddrop_table
    • Removedlist_tables
    • Removedread_query
    • Removedwrite_query
  2. 7 tool updates
    • Addedappend_insight
    • Addedcreate_table
    • Addeddescribe_table
    • Addeddrop_table
    • Addedlist_tables
    • Addedread_query
    • Addedwrite_query
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The single tool's purpose is clearly distinct by default.

Naming Consistency5/5

With a single tool, naming consistency is trivially maintained. The name 'create_table' follows a clear verb_noun pattern.

Tool Count2/5

A single tool for a SQLite server is far too few for the apparent scope. Typical database operations are missing, making the tool set feel extremely thin.

Completeness2/5

The server only supports table creation, lacking essential operations like querying, inserting, updating, deleting, or dropping tables. This represents significant gaps for any database interaction.

Maintenance

ActivitySlowing
ResponsivenessSlow

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Database MCP Server

    georgi-terziyski
    F
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that provides tools for connecting to and interacting with various database systems (SQLite, PostgreSQL, MySQL/MariaDB, SQL Server) through a unified interface.
    3
    -

  • SQLite MCP Server

    santos-404
    A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server implementation that enables AI assistants to execute SQL queries and interact with SQLite databases through a structured interface.
    7
    MIT

  • Memory MCP

    drdee
    A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server that allows users to store, retrieve, update, and delete memories using SQLite storage.
    5
    10
    MIT

  • SQLite MCP Server

    sam2332
    A
    license
    B
    quality
    D
    maintenance
    A Model Context Protocol server that enables AI assistants to interact with SQLite databases by connecting to database files, listing tables, describing schemas, and executing queries.
    6
    188
    2
    MIT

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/isaacgounton/sqlite-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server