Get笔记 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level for the server | info |
| RATE_LIMIT_QPS | No | Rate limit in queries per second | 2 |
| REQUEST_TIMEOUT | No | Request timeout in milliseconds | 30000 |
| GET_BIJI_API_KEY | Yes | Your Get笔记 API key (required) | |
| RATE_LIMIT_DAILY | No | Daily rate limit for API requests | 5000 |
| GET_BIJI_API_BASE_URL | No | The base URL for the Get笔记 API | https://open-api.biji.com/getnote/openapi |
| GET_BIJI_DEFAULT_TOPIC_ID | No | Your default topic/knowledge base ID |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| knowledge_searchB | 在Get笔记知识库中进行AI增强搜索,返回经过深度处理的答案。支持对话历史追问。 |
| knowledge_recallB | 在Get笔记知识库中召回相关内容,返回未经AI处理的原始结果。可用于快速查找和预览。 |
| get_rate_limit_statsB | 获取当前API速率限制使用情况统计 |
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 with no overlap: get_rate_limit_stats handles API monitoring, knowledge_recall provides raw search results, and knowledge_search delivers AI-processed answers. The descriptions make it impossible to confuse these tools as they target fundamentally different operations.
The naming follows a consistent snake_case pattern throughout, but there's a minor deviation in verb style: 'get_' prefix for one tool versus 'knowledge_' prefix for the other two. This small inconsistency prevents a perfect score, though the overall naming remains highly readable and predictable.
With only 3 tools, the set feels thin for a note-taking/knowledge management server, as it lacks basic CRUD operations like creating, updating, or deleting notes. While the tools cover API monitoring and search functions, the scope appears incomplete, making this borderline appropriate.
There are significant gaps in the tool surface for a note-taking server: no tools for creating, editing, organizing, or deleting notes, which are core to the domain. The tools focus only on search and API monitoring, leaving agents unable to perform essential workflows, likely causing failures in typical use cases.