TiDB RAG MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USE_MOCK | No | Set to 'true' to use mock data without database, 'false' to use TiDB database | true |
| TIDB_HOST | No | TiDB host address (required when USE_MOCK=false) | |
| TIDB_PORT | No | TiDB port (required when USE_MOCK=false) | |
| TIDB_USER | No | TiDB user (required when USE_MOCK=false) | |
| TIDB_DATABASE | No | TiDB database name (required when USE_MOCK=false) | |
| TIDB_PASSWORD | No | TiDB password (required when USE_MOCK=false) |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tidb_list_knowledgeA | List knowledge entries from TiDB RAG knowledge base with pagination. This tool retrieves knowledge entries from the database, supporting filtering by category and pagination. Args:
Returns: For JSON format: { "total": number, // Total entries matching criteria "count": number, // Entries in this response "offset": number, // Current pagination offset "items": [...], // Array of knowledge entries "has_more": boolean, // Whether more results exist "next_offset": number // Offset for next page (if has_more) } Examples:
|
| tidb_get_knowledgeA | Get a single knowledge entry by ID from TiDB RAG knowledge base. This tool retrieves the full content of a specific knowledge entry. Args:
Returns: For JSON format: { "id": string, "title": string, "content": string, "category": string | null, "metadata": object | null, "created_at": string, "updated_at": string } Examples:
|
| tidb_search_knowledgeA | Search knowledge entries by keyword in TiDB RAG knowledge base. This tool searches for knowledge entries matching a query string in title or content. Args:
Returns: For JSON format: { "total": number, // Total matching entries "count": number, // Entries in this response "offset": number, // Current pagination offset "items": [...], // Array of matching knowledge entries "has_more": boolean, // Whether more results exist "next_offset": number // Offset for next page (if has_more) } Examples:
|
| tidb_vector_searchA | Search knowledge entries by vector similarity in TiDB (requires vector embeddings). NOTE: This is a placeholder for future TiDB vector search functionality. Currently returns a not-implemented message. Args:
Returns: Vector search results with similarity scores. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The four tools have clear, non-overlapping purposes: paginated listing, single-item retrieval by ID, keyword search, and vector similarity search. Even though list and search both return multiple entries, one is for browsing and the other requires a query, so an agent can reliably distinguish them.
Three tools follow a consistent tidb_verb_noun pattern: tidb_list_knowledge, tidb_get_knowledge, and tidb_search_knowledge. tidb_vector_search breaks the verb-first convention somewhat, but the shared prefix and parallel structure keep the naming readable.
Four tools is a well-scoped size for a read-focused knowledge base server. Each tool earns its place by covering a distinct retrieval need without unnecessary redundancy.
List, get, and keyword search form a functional read path, but the only semantic retrieval tool is explicitly a placeholder that always returns a not-implemented message. For a server claiming RAG capabilities, the missing working vector search and the lack of knowledge-entry management operations are significant gaps.