leximo-ai-call-assistant-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEXIMO_API_TOKEN | Yes | JWT token from concierge.leximo.ai/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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profileA | Get the authenticated user's profile information including email, credits, and account details |
| get_creditsA | Get credit balance, monthly allowance, usage history, and subscription summary for the authenticated user |
| get_subscriptionA | Get the active Stripe subscription details for the authenticated user |
| get_plansA | List available subscription plans with pricing information |
| create_checkout_sessionA | Create a Stripe checkout session to subscribe to a plan. Returns a URL the user should open in their browser to complete payment. |
| list_agentsA | List all available AI calling agents. IMPORTANT: Always call this BEFORE creating an assignment. Present the returned agents to the user so they can choose which one should make the call, or recommend one based on the user's task. The agent's ID is required for create_assignment. |
| get_agentB | Get details of a specific AI calling agent by ID |
| list_assignmentsB | List assignments (call tasks) for the authenticated user with pagination. Returns data, total, page, limit, and totalPages. |
| get_assignmentA | Get a single assignment by its ID, including call results, transcript, and recording URL |
| create_assignmentA | Create a new phone call assignment. Do NOT call this tool immediately. Follow this workflow:
|
| delete_assignmentB | Delete an assignment by its ID |
| get_assignment_proposalsA | Get AI-generated enhancement proposals for a task description. IMPORTANT: Always call this BEFORE create_assignment to improve the task instructions. Pass the user's task description and present the enhanced suggestions to the user for approval before proceeding with assignment creation. |
| list_notificationsA | Get paginated list of notifications for the current user. Includes call completion events and system notifications. |
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 13 tools
All 13 tools have clearly distinct purposes. There is no overlap; each tool targets a unique resource or action, such as creating vs. listing assignments, retrieving agents, or managing subscriptions.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_assignment, list_agents, get_credits). No mixing of conventions or ambiguous verbs.
With 13 tools, the set is well-scoped for the server's purpose (AI calling assignments and subscription management). Each tool has a clear role, and there are no extraneous tools.
The tool surface covers core workflows: assignment CRUD (except update), agent management, subscription management, and notifications. Missing an update_assignment tool is a minor gap, but the design intentionally uses creation via proposals.