LimeAI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIMEAI_ACCESS_TOKEN | Yes | Your LimeAI access token, obtained from www.limeai.net personal profile |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_user_infoA | 获取当前用户信息 |
| save_markdownB | 保存文本内容（markdown格式）到 LimeAI |
| save_htmlC | 保存 html 代码到 LimeAI |
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: retrieving user info, saving markdown, and saving HTML. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern using snake_case: get_user_info, save_markdown, save_html. The pattern is predictable and uniform.
With just 3 tools, the server is tightly scoped to its apparent purpose of saving content in markdown/HTML and retrieving user info. No unnecessary tools are present, and the count feels appropriate.
Core save workflows for both markdown and HTML are covered, along with user info retrieval. However, there are no tools for list, get, update, or delete saved content, which is a minor gap that agents might need to work around.