biji-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BIJI_MCP_DEBUG | No | Set to '1' to enable debug logging. |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| biji_searchC | 在Get笔记知识库中搜索,返回AI生成的答案和引用来源 |
| biji_recallA | 召回知识库原始内容片段,不经AI处理,返回相关度排序的结果列表 |
| biji_list_kbA | 列出所有已配置的Get笔记知识库 |
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 3 tools
Each tool has a clearly distinct purpose: biji_search returns AI-generated answers with citations, biji_recall returns raw content snippets ranked by relevance, and biji_list_kb lists configured knowledge bases. There is no overlap between these operations, so an agent can confidently choose the right tool based on whether it needs processed or raw results.
All tool names follow the biji_ prefix and a simple verb pattern: search, recall, list_kb. This is consistent and predictable. The only minor deviation is that list_kb uses an underscore while the others are single verbs, but the overall convention is uniform.
With 3 tools, the server is well-scoped for a knowledge base search service. Each tool serves a distinct need—AI search, raw recall, and KB discovery—without unnecessary extras. This is within the ideal 3-15 range and feels complete for its niche purpose.
The server covers the core functionality of searching and recalling knowledge base content, plus listing available KBs. A minor gap is the lack of a tool to retrieve metadata or browse specific documents within a KB, but that is beyond the primary search/recall workflow and can be worked around.