grok-import-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROK_API_KEY | No | API key for admin authentication (optional) | |
| GROK_API_URL | Yes | grok2api server URL (e.g. http://167.114.174.225: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 |
|---|---|
| batch_add_tokensA | Batch add tokens to a specific pool. |
| batch_delete_tokensA | Batch delete tokens from all pools. |
| enable_nsfwA | Enable NSFW for specified tokens, or all tokens if list is empty/None. |
| list_tokensA | List tokens in a specific pool, or all pools if pool_name is empty. |
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
Each tool has a distinct verb: batch_add_tokens adds, batch_delete_tokens deletes, enable_nsfw toggles a flag, and list_tokens lists. The descriptions clarify scope (specific pool vs. all pools), so there is no overlap or ambiguity.
Three tools use a clear verb_noun pattern (list_tokens, enable_nsfw, batch_add_tokens), but the 'batch_' prefix on add/delete creates a slight inconsistency. Still, all names are snake_case and readable, with predictable structure.
Four tools is perfectly scoped for a focused token management utility. Each tool handles a distinct operation without unnecessary bloat or redundancy.
The surface is missing key lifecycle operations: delete only works across all pools (not a specific pool), there is no disable_nsfw counterpart, and no way to update token properties besides NSFW. These are significant gaps for a token management tool.