Lenx MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LENX_API_KEY | Yes | Your Lenx API key | |
| LENX_USER_ID | Yes | Your Lenx user ID | |
| LENX_BASE_URL | No | API base URL | https://open.lenx.ai |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lenx_list_tasksA | List monitoring tasks accessible to the authenticated user, with pagination support. |
| lenx_get_taskA | Retrieve configuration and metadata for a single monitoring task by ID. |
| lenx_create_taskA | Create a new monitoring task (live or adhoc). Live tasks run continuously; adhoc tasks require a date_range. |
| lenx_update_taskA | Update an existing task's name and/or search query configuration. At least one field is required. |
| lenx_delete_taskA | Delete a monitoring task. Only the task owner can perform this operation. |
| lenx_get_task_dataB | Retrieve paginated social media post data for a specific task within a time range. |
| lenx_export_task_dataA | Request a CSV or XLSX export of task post data. Results are sent to the specified email address. |
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 7 tools
Each tool targets a distinct operation (create, delete, get, list, update, get data, export data) with no overlap. Descriptions clearly differentiate between task metadata and task post data.
All tool names follow the consistent pattern 'lenx_verb_noun' (e.g., lenx_create_task, lenx_list_tasks) using snake_case and clear verbs.
With 7 tools, the server covers essential CRUD operations, data retrieval, and export for monitoring tasks. The count feels well-scoped for a task management tool.
The tool surface provides full CRUD, listing, data retrieval, and export. Minor gaps like toggling task active state or getting export status are absent but do not severely impact core workflow.