Moxie CRM MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOXIE_API_KEY | Yes | Your Moxie API key | |
| MOXIE_BASE_URL | Yes | Your Moxie API base URL (e.g., https://pod01.withmoxie.com/api/public) |
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 |
|---|---|
| list_clientsA | List all clients in your Moxie workspace |
| search_clientsA | Search for clients by name or contact information |
| create_clientB | Create a new client in Moxie CRM |
| search_contactsB | Search for contacts in your Moxie workspace |
| create_contactB | Create a new contact associated with a client |
| search_projectsA | Search for projects in your Moxie workspace, optionally filtered by client name |
| create_projectB | Create a new project in Moxie CRM |
| update_projectC | Update an existing project in Moxie CRM |
| list_project_task_stagesA | List all available project task stages in your workspace |
| create_taskC | Create a new task/deliverable in a project |
| approve_deliverableC | Approve a deliverable/task in a project |
| search_payable_invoicesB | Search for payable invoices in your Moxie workspace |
| create_invoiceA | Create a new invoice in Moxie CRM. If sendTo is not provided, the invoice will be created as a draft. |
| apply_paymentB | Apply a payment to an existing invoice |
| create_expenseB | Create a new expense record in Moxie |
| create_time_entryA | Create a time entry to track work. Can optionally auto-create client, project, or deliverable if they don't exist. |
| list_pipeline_stagesA | List all pipeline stages for opportunities in your workspace |
| create_opportunityA | Create a new sales opportunity in the pipeline. Note: This endpoint (/action/opportunities/create) may not be officially documented. The official way to create opportunities is via form submissions with a pipelineStageName using create_form_submission. |
| create_ticketB | Create a new support ticket in your workspace |
| create_ticket_commentB | Add a comment to an existing ticket |
| list_form_namesA | List all available form names in your workspace |
| create_form_submissionB | Create a new form submission with lead information and custom answers. Can optionally create a pipeline opportunity by providing pipelineStageName. |
| attach_file_from_urlA | Attach a file to a Moxie record by providing a URL. The file will be downloaded and attached. |
| create_calendar_eventB | Create a new calendar event |
| update_calendar_eventB | Update an existing calendar event |
| delete_calendar_eventB | Delete a calendar event |
| list_email_templatesA | List all email templates in your workspace |
| list_invoice_templatesA | List all invoice templates in your workspace |
| list_vendor_namesA | List all vendor names for expense tracking |
| list_workspace_usersA | List all users in your Moxie workspace |
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 30 tools
Most tools target distinct resources, but create_opportunity and create_form_submission both can create pipeline opportunities, with create_opportunity explicitly flagged as potentially undocumented. This creates selection ambiguity for agents.
All tool names follow a consistent verb_noun snake_case pattern (e.g., list_clients, create_project, attach_file_from_url). No mixed conventions or camelCase.
With 30 tools, the server exceeds the 25-tool threshold for 'too many'. While a CRM has many entities, several tools could be combined (e.g., list_clients and search_clients) and the count feels bloated.
The tool surface has significant gaps: no update/delete for clients, contacts, tasks, or tickets; no list/read for projects, invoices, or calendar events (only search_payable_invoices and calendar create/update/delete). Agents would frequently hit dead ends for basic operations.