moxie-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@moxie-mcpshow my recent invoices"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Moxie MCP server
A remote MCP server for the Moxie Public API, deployable to Cloudflare Workers (per the Cloudflare remote MCP guide). Exposes all 29 documented Moxie endpoints as MCP tools — clients, contacts, projects, tasks, invoices, payments, expenses, time entries, opportunities, tickets, calendar, and attachments.
How it works
src/index.ts defines a McpAgent (Durable Object) running an McpServer. Tools are
data-driven from a single TOOLS table; each call proxies to Moxie with the X-API-KEY
header. Two transports are mounted:
POST /mcp— streamable HTTP (use this for new clients)GET /sse— SSE (legacy clients)
Related MCP server: Remote MCP Server on Cloudflare
Available MCP actions
The server exposes the following 29 MCP tools. Arguments described as names (such as
clientName, projectName, templateName, stageName, vendor names, and user emails)
must exactly match the corresponding record in Moxie. Use a list or search tool first
when you do not already know the exact value.
Read and discovery tools
MCP tool | What it can do | Moxie endpoint |
| List all clients as full objects and discover exact client names. |
|
| Search clients by a name prefix, contact email, or contact name. Requires |
|
| Search contacts by first name, last name, or email. The |
|
| Search projects, optionally filtering by client name. |
|
| Search payable invoices, optionally filtering by client name. |
|
| List available email template names. |
|
| List available invoice template names. |
|
| List available vendor names. |
|
| List available form-template names. |
|
| List pipeline stages, including ID, label, color, and stage type. |
|
| List project task/Kanban stages. |
|
| List workspace users, including emails, roles, and access. |
|
Create, update, and delete tools
MCP tool | What it can do | Required inputs | Moxie endpoint |
| Create a client or prospect, optionally with address, payment terms, notes, and contacts. |
|
|
| Create a contact, optionally assigning it to an existing client. | None |
|
| Create an invoice and optionally email it using |
|
|
| Create an expense, optionally assigning a vendor and client. |
|
|
| Create a form submission and optionally create a pipeline opportunity by supplying | None |
|
| Create a project from project details or a template, with an optional fee schedule and portal settings. |
|
|
| Create a project task with optional status, dates, priority, checklist subtasks, assignees, and custom values. |
|
|
| Approve a deliverable that is in Client Workflow/Approval status. |
|
|
| Create a support ticket with optional subject, due date, and form answers. |
|
|
| Add a public or private comment to an existing ticket. Private comments are ignored for client contacts. |
|
|
| Create a pipeline opportunity with optional client, stage, value, close date, lead data, to-dos, and custom values. |
|
|
| Log time for a user against an optional client, project, or deliverable; missing records can be created with the corresponding |
|
|
| Apply a payment to an invoice, with an optional payment type, reference number, and memo. |
|
|
| Upload a base64-encoded file (up to 100 MB) to a client, project, deliverable, opportunity, expense, or ticket. |
|
|
| Ask Moxie to fetch an HTTPS file and attach it to a client, project, deliverable, opportunity, expense, or ticket. |
|
|
| Create a calendar event or update it by reusing its |
|
|
| Delete a calendar event using the |
|
|
Attachment tools return signed URLs that expire after 15 minutes. Moxie's API does not provide a tool to void or delete an invoice; that action must be completed in the Moxie UI.
Configure
Get MOXIE_API_KEY + MOXIE_BASE_URL from Moxie:
Workspace settings → Connected Apps → Integrations → Enable Custom Integration.
npm install
# Secrets (encrypted, per Cloudflare):
npx wrangler secret put MOXIE_API_KEY # your Moxie workspace API key
npx wrangler secret put MCP_LOGIN_PASSWORD # password you'll type when connecting
# One-time: KV namespace for OAuth tokens (already created if id is in wrangler.jsonc):
npx wrangler kv namespace create OAUTH_KV # paste the id into wrangler.jsoncMOXIE_BASE_URL is a plain var in wrangler.jsonc — change the pod to yours.
Auth
The server is an OAuth 2.1 provider (@cloudflare/workers-oauth-provider): /mcp and
/sse require a valid token, and connecting clients hit a login screen that checks
MCP_LOGIN_PASSWORD. This is what makes it usable as a Claude custom connector
(claude.ai / Desktop / mobile), which authenticate via OAuth, not static headers.
Run & deploy
cp .dev.vars.example .dev.vars # fill in, then:
npm run dev # local at http://localhost:8787/mcp
npm test # helper self-checks
npm run typecheck
npm run deploy # → https://moxie-mcp.<subdomain>.workers.dev/mcpConnect a client
Claude custom connector (cross-platform — claude.ai, Desktop, mobile, Cowork):
Settings → Connectors → Add custom connector → paste the deployed /mcp URL
(https://moxie-mcp.<subdomain>.workers.dev/mcp). Claude runs the OAuth flow and shows
the login screen; enter your MCP_LOGIN_PASSWORD. Requires a Pro/Max/Team/Enterprise plan.
Claude Code speaks HTTP MCP natively and will do the same OAuth flow:
claude mcp add --transport http moxie https://moxie-mcp.<subdomain>.workers.dev/mcpClients that only support stdio (e.g. older Claude Desktop) need the mcp-remote bridge, which handles the OAuth login:
{
"mcpServers": {
"moxie": { "command": "npx", "args": ["-y", "mcp-remote", "https://moxie-mcp.<subdomain>.workers.dev/mcp"] }
}
}Notes
Exact-name rule: write tools reference other records by exact name. Call a
*_list/*_searchtool first and copy the value verbatim — the #1 cause of failures.Rate limit: 100 requests / 5 min → tools surface a clear 429 message.
Auth: OAuth 2.1 via
@cloudflare/workers-oauth-provider, gated by a singleMCP_LOGIN_PASSWORDlogin (one user). For real multi-user access, swap the password screen inauthHandlerfor an upstream IdP (GitHub/Google) per the Cloudflare guide.Attachments:
attachments_createtakes base64 (no local FS on Workers);attachments_create_from_urlis preferred when the file is already at an HTTPS URL. Signed URLs returned expire after 15 min.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityCmaintenanceA remote MCP server template for deployment on Cloudflare Workers without authentication. Provides a foundation for building custom MCP tools that can be accessed from Claude Desktop or Cloudflare AI Playground.Last updated
- Flicense-qualityCmaintenanceA Model Context Protocol server implementation designed to run on Cloudflare Workers with integrated OAuth authentication. It enables hosting and securely accessing MCP tools remotely via SSE transport from clients like Claude Desktop.Last updated
- Alicense-qualityDmaintenanceProvides 55 tools for managing QuickBooks entities like customers, invoices, and bills via any MCP-compatible client, built on Cloudflare Workers with OAuth 2.0 authentication.Last updated8Apache 2.0
- Alicense-qualityAmaintenanceA hosted HTTP MCP server for Cloudflare Workers that exposes a bundle of tools via a remote /mcp endpoint, enabling Claude-compatible clients to connect without a local server.Last updated141BSD Zero Clause
Related MCP Connectors
ClickUp MCP — wraps the ClickUp REST API v2 (BYO API key)
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Markdown-first MCP server for Notion API with 8 composite tools and 39 actions.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Joshlucpoll/moxie-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server