mcpserve-py
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcpserve-py list all tables in the database"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcpserve-py
A Model Context Protocol (MCP) server built in Python ā exposes database query tools and document resources over JSON-RPC 2.0 stdio transport, enabling AI assistants to interact with SQLite databases and markdown documents.
What is MCP?
The Model Context Protocol is an open standard for connecting AI assistants to external tools and data sources. MCP servers expose tools (functions the AI can call) and resources (data the AI can read) over a JSON-RPC 2.0 transport.
This server implements the MCP protocol from scratch using raw JSON-RPC 2.0 over stdio ā no SDK dependency required.
Related MCP server: rag-mcp-agent-demo
Features
š§ 8 tools ā database queries, document CRUD, search, date/time
š Resource providers ā documents and database schemas as readable resources
š”ļø SQL injection protection ā only SELECT queries allowed, with regex validation
š YAML frontmatter ā documents stored as markdown with structured metadata
š Stdio transport ā line-delimited JSON-RPC 2.0 over stdin/stdout
ā” Zero SDK dependency ā hand-rolled MCP protocol implementation
ā Well-tested ā 113 tests covering protocol, tools, resources, and integration
Quick Start
# Clone and install
git clone https://github.com/devaloi/mcpserve-py.git
cd mcpserve-py
pip install -e ".[dev]"
# Run the server
python -m mcpserve_py
# Run tests
python -m pytest -vEnvironment Variables
Variable | Default | Description |
|
| Directory for documents and data |
|
| Path to SQLite database |
|
| Log level (DEBUG, INFO, WARNING, ERROR) |
Claude Desktop Configuration
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"mcpserve-py": {
"command": "python",
"args": ["-m", "mcpserve_py"],
"env": {
"MCPSERVE_DATA_DIR": "./data",
"MCPSERVE_DB_PATH": "./data/mcpserve.db"
}
}
}
}Tools
Tool | Description | Parameters |
| Execute read-only SQL query |
|
| List all tables in database | ā |
| Get table schema |
|
| Create a markdown document |
|
| Read document by title |
|
| List all documents |
|
| Full-text search across documents |
|
| Current date/time |
|
Resources
URI Pattern | Description | MIME Type |
| Document content |
|
| Full database schema |
|
| Single table schema |
|
Architecture
src/mcpserve_py/
āāā __main__.py # Entry point: python -m mcpserve_py
āāā server.py # MCP server: receive ā dispatch ā respond
āāā protocol.py # JSON-RPC 2.0 types and encoding
āāā transport.py # Stdio transport (line-delimited JSON)
āāā config.py # Pydantic settings
āāā tools/
ā āāā registry.py # Tool registry
ā āāā database.py # SQLite tools (query, list_tables, describe)
ā āāā documents.py # Document tools (CRUD + search)
ā āāā system.py # System tools (get_datetime)
āāā resources/
āāā provider.py # Resource provider interface + registry
āāā documents.py # Document resource provider
āāā database.py # Database schema resource providerDesign Decisions
No MCP SDK ā The protocol is implemented directly using JSON-RPC 2.0 dataclasses. This demonstrates deep understanding of the protocol rather than SDK usage.
Synchronous ā Stdio is inherently sequential; async adds complexity without benefit here.
Pydantic Settings ā Configuration via environment variables with type validation and
.envfile support.Tool registry pattern ā Tools register themselves with a central registry, keeping the server dispatch clean.
Read-only SQL ā Mutations are rejected via regex before reaching SQLite, preventing data corruption by AI assistants.
YAML frontmatter ā Documents use the same format as static site generators (Jekyll, Hugo), making them human-readable and tool-friendly.
Development
# Install with dev dependencies
pip install -e ".[dev]"
# Run tests
make test
# Lint
make lint
# Type check
make typecheck
# Format
make format
# All checks
make allLicense
MIT
Contributing
See CONTRIBUTING.md. PRs welcome ā run make all before submitting.
Available Tools
8 toolscreate_documentB
Create a new markdown document with optional tags.
Inputs: title (required), content (required), tags.
describe_tableB
Get the schema of a specific table including column names, types, and constraints.
Inputs: table (required).
get_datetimeA
Get the current date and time, optionally in a specific timezone.
Inputs: timezone.
list_documentsB
List all documents, optionally filtered by tag.
Inputs: tag.
list_tablesB
List all tables in the SQLite database.
Inputs: no named parameters.
query_databaseA
Execute a read-only SQL query against the SQLite database. Only SELECT statements are allowed.
Inputs: sql (required), params.
read_documentC
Read a document by its title.
Inputs: title (required).
search_documentsC
Search documents by content and title.
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogā¦
TDQS
Scored across 8 tools
Most tools target clearly distinct resources and actions, so an agent can pick correctly with little hesitation. The only mild overlap is between list_documents (tag filter) and search_documents (content/title query), which descriptions do disentangle.
Every tool follows a clean verb_noun snake_case pattern: query_database, list_tables, describe_table, create_document, read_document, list_documents, search_documents, get_datetime. No deviations or mixed conventions.
Eight tools is well-scoped for a lightweight multi-purpose server covering database introspection, document management, and a datetime utility. Each tool earns its place with no redundancy.
Document handling lacks update and delete operations, and the database surface is read-only with no insert/update/delete, so lifecycle coverage is partial. The lone get_datetime tool also sits outside either domain, leaving a somewhat heterogeneous surface.
Maintenance
Related MCP Connectors
Persistent memory, hybrid search and a goal graph for AI agents, over stdio or remote HTTP.
Serve a folder of Markdown notes as an MCP server: hybrid search, reading, and sourced answers.
Text-to-SQL MCP server: read-only queries on PostgreSQL, MySQL and SQL Server with your real schema
PostgreSQL, MySQL, and SQL Server in one session. 26 read-only MCP tools for AI agents.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceProvides AI agents read-only analytical access to a SQLite database over stdio, with tools for listing tables, describing schemas, and running paginated SQL queries.-
- AlicenseAqualityCmaintenanceEnables read-only document retrieval and SQLite exploration through tools over stdio, enforcing a safety gate before SQL execution.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI models to securely analyze SQLite datasets and read local text documents through a local stdio interface. It provides read-only querying, schema discovery, pagination, and timeout protections to prevent data leaks or destructive changes.MIT
- AlicenseNot gradedqualityFmaintenanceExposes a stdio MCP server that indexes a markdown vault (such as an Obsidian folder of notes) into SQLite FTS5 and answers BM25-ranked section-level queries, with filters for note type. It also exposes reindexing so notes edited on disk become searchable again, giving coding agents persistent, durable memory across sessions.MIT