Invoice Pilot

io.github.therealMrFunGuyPublished by GitHub account therealMrFunGuyv1.0.0Updated Oct 24, 2026

PDF invoicing with auto-chase reminders, email delivery, and payment tracking.

The publisher's own server: QuickBooks Connector by Meridian

Overview

AI-generated overview

Lets an assistant create PDF invoices, send them by email, chase unpaid ones automatically, and track payments.

What you can do
Invoice Pilot is a remote MCP server for PDF invoicing. According to its registry description, it covers PDF invoice generation, automatic chase reminders for unpaid invoices, email delivery, and payment tracking. No tool list is published, so the exact operations an assistant can call are not documented here.
When to use it
Consider it when an assistant should handle invoicing end to end: producing PDF invoices, emailing them to clients, following up on overdue ones, and reporting payment status. It is less useful if you only need one-off document generation without delivery or tracking.
Requirements
A remote MCP endpoint reached over SSE at the provider's host; no local package or runtime is declared. An API key is required, supplied in the X-API-Key header and obtained from the provider's auth dashboard. Network access to the endpoint is needed.
Before you install
The server asks for an API key in the X-API-Key header; treat it as a secret and do not share it. It sends invoices and reminders by email to third parties and records payment status, so it handles client contact details and financial data. Because no tool list is published, confirm what it can write, send, or change before connecting it to real invoicing.

Installation

In SourceWeft

  1. Open Invoice Pilot in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.therealMrFunGuy%2Finvoice-pilot/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "invoice-pilot": {
      "type": "sse",
      "url": "https://invoice.rjctdlabs.xyz/sse"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Pilot integrations