Skip to main content
EnglishDeutschFrançaisEspañolPolski
Start free

Model Context Protocol

MCP server setup for Claude, Cursor and other clients

Set up the QuickBilling MCP server in Claude Desktop, Cursor or another MCP client that supports remote servers. Add one URL and sign in with your QuickBilling account.

What is the QuickBilling MCP server?

A hosted remote MCP server that exposes QuickBilling as typed tools for AI assistants.

Model Context Protocol (MCP) lets AI assistants call structured tools instead of scraping a UI.

QuickBilling runs a hosted remote MCP server at https://mcp.quickbilling.io/mcp (streamable HTTP). You add it to an MCP client that supports remote servers and sign in with your QuickBilling account.

What that means in practice

  • Your assistant can create invoices, log expenses, manage customers and pull reports from chat
  • 149 tools across billing, expenses and reports
  • Sign-in uses OAuth 2.1 with PKCE and your QuickBilling account, not an API key
  • Every call runs with your account's permissions

Best for: freelancers and teams who already live in Claude Desktop, Cursor or another MCP client and want invoicing without switching to a dashboard.

API for products, MCP for assistants

Same data underneath, two ways in.

Use the REST API when you embed billing into your own product or automation pipeline. API keys are part of the Unlimited plan.

Use the MCP server when a person drives an AI assistant and wants natural-language access to the same data.

QuickBilling MCP is built for

  • Claude Desktop, added as a custom remote connector
  • Cursor and other clients with remote MCP server support
  • Any MCP client that supports remote servers with OAuth sign-in

Every tool maps to a real authenticated call with the permissions of the signed-in account.

Quick start

Add one URL and sign in.

Prerequisites: a QuickBilling account and an MCP client that supports remote servers with OAuth sign-in.

Steps

  1. Open your MCP client's settings and add a remote MCP server
  2. Use the URL https://mcp.quickbilling.io/mcp
  3. Sign in with your QuickBilling account when the client asks you to authorise the connection
  4. Ask your assistant: “List my QuickBilling workspaces” or “Which invoices are overdue?”

You do not need an API key. If your account has more than one workspace, ask the assistant to list them and pick one.

Config for clients that read a JSON file (for example Cursor)

mcp.json
{
  "mcpServers": {
    "quickbilling": {
      "url": "https://mcp.quickbilling.io/mcp"
    }
  }
}

In Claude Desktop, add the same URL as a custom connector (a remote MCP server). Menu names differ by client, so check your client's documentation for adding a remote server.

Set up the MCP server in Claude Desktop

Add QuickBilling as a custom connector.

Steps

  1. Open Claude Desktop and go to Settings, then Connectors
  2. Choose Add custom connector
  3. Name it QuickBilling and paste the URL https://mcp.quickbilling.io/mcp
  4. Select Connect and sign in with your QuickBilling account in the browser window that opens
  5. In a new chat, turn on the QuickBilling connector and ask: “List my QuickBilling workspaces”

Menu names can change between Claude Desktop versions, and custom connectors can depend on your Claude plan.

Set up the MCP server in Cursor

Add the server in settings or in mcp.json.

Steps

  1. Open Cursor Settings, then the MCP section
  2. Choose to add a new MCP server. Cursor opens your mcp.json file
  3. Add an entry named quickbilling with the url https://mcp.quickbilling.io/mcp, as in the minimal config under Quick start
  4. Save the file. When Cursor asks you to sign in, finish the sign-in in your browser
  5. In the Agent chat, ask: “Which invoices are overdue?”

To use the server in one project only, put the same entry in .cursor/mcp.json inside that project.

Connection details

What your MCP client needs.

  • Server URL: https://mcp.quickbilling.io/mcp
  • Transport: streamable HTTP, a remote server with nothing to install
  • Authentication: OAuth 2.1 with PKCE, signing in with your QuickBilling account
  • Discovery: OAuth protected resource metadata is served at /.well-known/oauth-protected-resource on the same host

API keys are not accepted by the remote server. API keys are for the REST API and are part of the Unlimited plan: see https://quickbilling.io/docs/api

Workspaces

How an assistant picks the workspace to work in.

If your account has one workspace, the assistant uses it without any setup.

If you have several, ask the assistant to list your workspaces and choose one.

Workspace tools

  • list_workspaces, returns your workspaces
  • get_active_workspace, shows the workspace in use
  • set_active_workspace, selects a workspace for the calls that follow

Tools

What an assistant can do once connected.

The server exposes 149 tools

  • Invoices and estimates (19): list, get, create, save, delete, duplicate, convert an estimate to an invoice, reissue, status, mark paid, email preview and send, share links, PDF link, activity, view analytics, reminders
  • Recurring invoices (7): list, get, create, update, pause, resume, delete
  • Customers (8): list, search, get, statement, create, quick create, update, delete
  • Billing profiles and item library (7)
  • Templates (6): list templates, built-in templates, default, get, set the default, presets
  • Expenses (23): list, get, create (one or several), update, delete, submit, resubmit, approve, reject, mark paid, void, bulk actions, billable expenses, invoice links, attachments and receipt files, activity
  • Expense reports (9): stats, summary, monthly, quarterly, yearly, trends, cost analysis, spend, tax-deductible
  • Categories, vendors and tags (12)
  • Budgets (5), recurring expenses (7) and income (6)
  • Projects and milestones (10), including invoicing a milestone
  • Triage, reports and search (4): what needs attention, daily, weekly and monthly digest, personal money check-in, workspace search
  • Plain-words expense logging (1): quick_log_expenses records up to 25 expenses from plain words
  • Notifications (2): list_notifications, mark_notifications_read
  • HTML reports (9): create, upload, list, get, update, share by link, email, revoke a share, delete
  • Reports and dashboards (7): overview stats, workspace reports, profit and loss, cash flow, profit by customer, customer profitability, net position
  • Workspace and profile (5): get_profile, list_workspaces, get_active_workspace, set_active_workspace and attach_receipt_to_expense
  • Workspace settings (1): get_workspace_settings
  • Plan usage (1): get_subscription_usage

Not available over MCP: team members and invitations, account export, subscription plans, template design, colour palettes, and avatar or logo uploads. Use the web app for those.

The same data is available through the REST API: https://quickbilling.io/docs/api

Example workflows

Requests that map cleanly onto the tools.

Create and send an invoice

“Create an invoice for Bluebird Café for 3 hours of design at $120/hour and send it.” The assistant finds or adds the customer, builds the invoice and sends it by email.

Log an expense with a receipt

“Log this receipt as a Software expense.” The assistant reads the receipt and creates the expense in that category. Files you share in your chat are not stored by QuickBilling; to keep the original on the expense, ask for an upload link, a signed link that works for 30 minutes.

Check what is overdue

“Which invoices are overdue?” The assistant lists unpaid invoices past their due date.

Work across workspaces

“List my workspaces and switch to Northwind Studio.” Then continue with invoice or expense requests.

Sign-in and security

Your account, your permissions.

  • Sign-in uses OAuth with your QuickBilling account, and the remote server does not accept API keys
  • Every call runs with your account's permissions, including changing and deleting records
  • Check what your assistant proposes before you confirm a change
  • Remove the connection in your MCP client to stop access
  • What an assistant does with the data it receives is governed by its provider's own policy, see the privacy policy section on AI assistants

Troubleshooting

Common setup issues.

The client cannot connect

Check that your client supports remote MCP servers with OAuth sign-in and that the URL is exactly https://mcp.quickbilling.io/mcp.

The sign-in step does not complete

Remove the server from your client, add it again and follow the sign-in prompt with your QuickBilling account.

Wrong workspace data

Ask the assistant which workspace is active, then list your workspaces and select the right one.

More help: https://quickbilling.io/contact, info@quickbilling.io