User Intent MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USERINTENT_API_KEY | Yes | 用户 API Key（用于认证） | |
| USERINTENT_DB_PATH | No | SQLite 数据库路径 | data/intent.db |
| USERINTENT_TIMEOUT | No | 请求超时时间（秒） | 3000 |
| USERINTENT_WEB_HOST | No | Web 服务器主机 | 0.0.0.0 |
| USERINTENT_WEB_PORT | No | Web 服务器端口 | 8000 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| collect_user_intentA | Send a message to the user and collect their response. This tool displays content in a web interface and waits for user input. Users can provide text responses and optionally attach images. IMPORTANT: This tool accepts ONLY the 'question' parameter. Do NOT pass any other parameters such as 'intent', 'message', or 'prompt'. Use cases:
|
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 1 tool
There is only one tool, so there is no possibility of confusion between tools. The tool's purpose is completely unambiguous.
The tool name 'collect_user_intent' follows a clear verb_noun pattern and is descriptive. With only one tool, there is no inconsistency to evaluate.
The server has a single tool, which feels thin compared to the typical 3-15 range. However, the tool is well-scoped for the server's narrow purpose of collecting user intent, so the count is borderline but not problematic.
For the stated purpose of collecting user intent, the tool covers the full interaction loop: sending a message, displaying it, and collecting a response with optional images. There are no obvious gaps within this narrow domain.