Connect the Moxie MCP Server to a compatible AI assistant so it can securely find workspace context, help organize work, and take supported actions without making you copy information between tools.
Moxie MCP Server URL
https://pod01.withmoxie.com/mcp
Before you begin
MCP access is available for active Pro and Teams workspaces.
A workspace owner must keep the MCP Server enabled in Moxie.
Owners, full users, and eligible restricted users can connect. Restricted users only receive tools and records allowed by their Moxie access. Project collaborators cannot connect during the beta.
Your AI client must support remote MCP servers using Streamable HTTP and OAuth.
During authorization, Moxie asks you to sign in and choose one workspace. Your password remains with Moxie. The connected client receives time-limited access for that user and workspace rather than your Moxie password.
What the Moxie MCP Server can help with
The beta includes more than 180 focused tools plus on-demand workflow guides. The exact tools available to a person depend on their Moxie role and feature access.
Clients and contacts: find and maintain client records, contacts, notes, and client activity.
Sales: work with opportunities, proposals, agreements, and reusable products or services.
Projects and support: review projects, manage tasks, comments, dependencies, time entries, timers, and tickets.
Forms and intake: use form templates, prepare client requests, and review submissions.
Calendar and meetings: inspect calendar context, check availability, and manage supported meeting bookings.
Money: work with invoices, payment plans, expenses, other income, vendors, profit and loss, and supported business reports.
Files and communications: find and maintain files, review email history, and manage reusable bulk-email audiences and scheduled-send status.
Search and guidance: resolve records safely and load Moxie playbooks for workflows such as client review, project delivery, ticket-to-task follow-up, time-to-invoice, and invoice lifecycle management.
Important beta boundaries
MCP is designed to complement the Moxie app, not replace every screen. General or bulk email sending, automatic charges, native calendar-event editing, deep agreement or proposal payment configuration, large file uploads, imports and exports, workflow automation setup, and broad workspace administration remain in Moxie. Some destructive or externally visible actions require an explicit confirmation and should always be reviewed before approval.
Connect Moxie to Claude
Claude supports remote custom connectors on eligible Pro, Max, Team, and Enterprise plans. Team and Enterprise workspaces require a Claude Owner or Primary Owner to add the connector for the organization before members connect it.
In Claude, open Customize → Connectors. For a Team or Enterprise organization, an owner starts from Organization settings → Connectors.
Choose Add custom connector, or choose Add → Custom → Web in organization settings.
Name the connector Moxie and enter
https://pod01.withmoxie.com/mcp.Add the connector, choose Connect, then complete the Moxie sign-in and select the workspace to authorize.
In a conversation, use the + menu and enable the Moxie connector or the specific Moxie tools you want Claude to use.
Claude maintains its current connector instructions in Get started with custom connectors using remote MCP.
Connect Moxie to ChatGPT
ChatGPT currently provides full MCP support, including write and modify actions, on the web for Business and Enterprise/Edu workspaces. An eligible administrator or authorized developer must enable developer mode and create the custom app.
Enable developer mode from the appropriate ChatGPT workspace or user settings.
Open Workspace settings → Apps → Create, or Settings → Apps → Create when your workspace permits it.
Name the app Moxie and enter
https://pod01.withmoxie.com/mcpas the MCP endpoint.Choose OAuth authentication, then select Scan tools.
Complete the Moxie sign-in and workspace selection when prompted, wait for the tool scan to finish, and create the app.
Test the draft app in a new chat. A ChatGPT workspace owner can publish it for other eligible members after reviewing its actions and access.
Plan availability and labels can change while this feature is in beta. Review OpenAI's current developer mode and MCP apps instructions if your menus differ.
Connect Moxie to Cursor
Cursor supports remote Streamable HTTP MCP servers and OAuth. Add Moxie globally when you want it available in every project, or add it to one project only.
Open Cursor's MCP settings and choose New MCP Server.
For a global connection, edit
~/.cursor/mcp.json. For one project, edit.cursor/mcp.jsonin that project.Add the following server entry and save the file:
{
"mcpServers": {
"moxie": {
"type": "http",
"url": "https://pod01.withmoxie.com/mcp"
}
}
}
Choose Connect for Moxie and complete the sign-in and workspace selection in your browser.
Enable the Moxie tools you want Cursor Agent to use. Cursor asks for tool approval by default.
See Cursor's current Model Context Protocol documentation for configuration locations, approval controls, and troubleshooting.
Connect another compatible client
If another client supports remote Streamable HTTP MCP servers and OAuth, add a server named Moxie with https://pod01.withmoxie.com/mcp. The client should discover Moxie's authorization service automatically, open the Moxie sign-in flow, and return to the client after you select a workspace.
A client that only supports local command-based MCP servers cannot connect directly. Follow that client's documentation for a remote-server bridge, or use Claude, ChatGPT, Cursor, or another client with native remote MCP support.
Manage workspace access and connections
Workspace owners can use Settings → Apps & integrations → MCP to control the entire workspace connection.
MCP enabled is the workspace-wide switch. Turning it off blocks MCP tool calls but does not delete saved client authorizations.
MCP connections shows each authorized client connection and the Moxie user who owns it. Multiple connections from the same client remain separate so one can be revoked without affecting the others.
Revoke blocks new authorization and refresh requests for that connection. An already-issued access token may remain valid for up to 15 minutes.
Owners can control workspace access, inspect client connections, and investigate tool activity from one page.
Review tool activity
The Tool activity table shows requests newest first. Filter by Moxie user, MCP client, tool, outcome, or date range to investigate activity. Outcomes distinguish successful calls from denied, invalid, rate-limited, and failed requests, and the duration helps identify unusually slow calls.
Moxie retains MCP audit metadata for 30 days. The audit identifies who called which tool, from which client, when, and with what outcome; it does not retain access tokens, tool arguments, or tool responses.
Useful first prompts
“Use Moxie to summarize the current relationship and open work for Acme.”
“Find my overdue tasks in Moxie and group them by client. Do not update anything.”
“Review this week's tracked time and identify billable work that may be ready to invoice.”
“Find open tickets that need a response and draft a follow-up plan. Ask before changing records.”
“Load the Moxie project-delivery playbook, then help me plan the next steps for Project Atlas.”
Troubleshooting
The client cannot discover Moxie: confirm that the URL is exactly
https://pod01.withmoxie.com/mcpand that the client supports remote Streamable HTTP MCP servers.The workspace is unavailable during sign-in: confirm that you are an active owner, full user, or eligible restricted user in an active Pro or Teams workspace.
Tools are missing or access is denied: Moxie applies the connecting user's current role, restricted-feature access, and record-level permissions. Ask the workspace owner to review the user's Moxie access.
All tool calls say MCP is disabled: a workspace owner must turn on MCP enabled in Moxie settings.
A connection stops refreshing: remove or revoke the affected connection, add it again in the AI client, and complete a fresh Moxie authorization.
A newly released tool is absent: refresh or rescan the app in the AI client. Some managed clients require an administrator to approve newly discovered actions.
Continue exploring Integrations & developer tools