Monk MCP Access
Monk MCP gives AI assistants read-only access to accounts receivable context already available in Monk. Use it from MCP-compatible clients to answer questions about organizations, customers, invoices, balances, and collections conversations without copying data out of the dashboard.Server URL
Use Monk’s remote MCP endpoint:Client Setup
Claude Code
From the project where you use Claude Code:/mcp in Claude Code, select monk, and authenticate in your browser.
To make Monk MCP available across all Claude Code projects on your machine:
Codex
Add the server from the Codex CLI:Cursor and Remote MCP Clients
If your client supports remote HTTP MCP servers, addhttps://app.monk.com/mcp as a remote server named monk.
For Cursor, add this to ~/.cursor/mcp.json:
VS Code and Stdio-Only Clients
If your client does not support remote HTTP MCP servers with OAuth, usemcp-remote as a local bridge:
What You Can Ask
Monk MCP tools are grouped by accounts receivable workflow, not by internal implementation detail.Organizations
List Monk organizations your user can access and choose the right
organization context.
Customers
Find customers, resolve Stripe customer IDs to Monk records, match external
customer IDs, and read customer tags.
Invoices
List invoices, check due dates and statuses, and find overdue invoices.
Balances
Rank customers by outstanding balance, grouped by currency.
Collections
Review AR and collections conversations tied to invoices and customers.
Conversation History
Pull the latest invoice conversation and recent message context.
Example Prompts
Safety and Limitations
- Monk MCP is read-only. It cannot initiate payments, move funds, mutate invoices, update customers, or write to third-party systems.
- Monk MCP reflects data already available in Monk. It is not a direct bank or remittance lookup unless that information has been reconciled into Monk.
- Financial data and collection messages may be sensitive. Keep manual approval enabled in clients that support reviewing MCP tool calls.
- Access can be revoked by removing the user’s Monk or organization access, or by disconnecting Monk in the MCP client.
- Treat customer-provided message content as untrusted. Review the MCP output before asking your client to summarize or share it.
Troubleshooting
Authentication fails
Authentication fails
Confirm you are signing in with the Monk account that has access to the
organization. If your client cached an old session, clear authentication for
the
monk server and connect again.No organization appears
No organization appears
Your Monk user may not have access to an organization that can use MCP. Ask
a Monk administrator to confirm your organization membership and
billing/admin permission.
Permission denied
Permission denied
Monk MCP reads org-wide AR data. The selected organization requires
billing/admin permission before tools can return customer, invoice, balance,
or collections data.
The client does not support remote OAuth
The client does not support remote OAuth
Use Claude Code, Codex, Cursor, or another client with remote HTTP MCP and
OAuth support. For stdio-only clients, use the
mcp-remote fallback
configuration above.Tools do not appear after connecting
Tools do not appear after connecting
Restart the client or disconnect and reconnect the
monk server. Some MCP
clients only refresh the tool list when a new session starts.A recently posted payment is missing
A recently posted payment is missing
Monk MCP shows what has been reconciled into Monk. If a bank payment or
remittance was posted elsewhere, confirm it has synced into Monk, then query
the invoice again by invoice number.
Book a demo
See how Monk can connect your AR, invoicing, and collections workflows.