moxie-mcp
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 |
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
} |
| resources | {
"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_clientC | Create a new client in Moxie CRM |
| search_contactsB | Search for contacts in your Moxie workspace |
| create_contactB | Create a new contact record and optionally associate with a client |
| search_projectsA | Search for projects in your Moxie workspace, optionally filtered by client name |
| create_projectC | 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_taskB | Create a new task/deliverable in a project |
| approve_deliverableA | Approve a deliverable/task that is in Client Workflow / Approval status in the Project Kanban |
| 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_opportunityB | Create a new sales opportunity in the pipeline |
| create_ticketB | Create a new support ticket in your workspace |
| create_ticket_commentC | 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_or_update_calendar_eventA | Create or update a calendar event in the Moxie Homebase calendar. Use eventId to update an existing event. |
| delete_calendar_eventA | Delete a calendar event by its event ID |
| 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 |
| moxie_health_checkA | Check if the Moxie MCP server is properly configured and can connect to the Moxie API |
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
Each tool targets a distinct action on a specific entity (e.g., clients vs. contacts, creation vs. listing). Even related tools like list_clients and search_clients have clear differences in scope.
All tool names follow a consistent verb_noun pattern in snake_case, with occasional compound verbs (e.g., create_or_update_calendar_event) but no mixing of conventions.
30 tools cover a broad domain (CRM, projects, invoicing, support, calendar, forms) and mostly justify their count, though some could be consolidated (e.g., list_clients and search_clients).
Many entities lack update/delete operations (e.g., clients, contacts, tasks). Read operations are limited (no get single client or task). Gaps may cause agent failures for typical workflows.