Connect and authorize
Start by choosing your AI client on the overview. Each client uses the same hosted InvoicePig endpoint:
https://invoicepig.com/mcpUse the exact URL above. Do not add an API key, bearer token, command, local package, or manual Authorization header.
What your client needs
Your AI client must support:
- Remote Streamable HTTP MCP servers
- Browser-based OAuth authorization
- OAuth protected-resource metadata discovery
The settings may be named remote MCP, HTTP MCP, or custom MCP server. A client that cannot open the browser sign-in flow is not compatible.
Connect your own account
- Add the InvoicePig endpoint in your AI client.
- Start the connection and wait for your browser to open.
- Sign in to your own InvoicePig account.
- Review and approve the connection.
- Return to your AI client and confirm that the InvoicePig tools are available.
Each person should complete these steps with their own account. Do not share a connection, access token, or connected client between people.
What InvoicePig can access
InvoicePig uses the connected account to verify your identity and determine which invoice layouts are available. The connection does not expose saved invoice history to the AI client, and MCP generation does not create or update drafts or history entries.
Your AI client stores and refreshes its authorization. Never copy an access token into chat, source control, client configuration, or a URL.
Reconnect
If authorization expires or is rejected, clear InvoicePig authentication in your client and connect again. Reconnecting is safer than copying or manually replacing a token.
In Claude Code, run /mcp, select InvoicePig, and choose Clear authentication before reconnecting. Other clients provide a similar clear-authentication or remove-server action.
Disconnect
Remove InvoicePig from your client’s MCP settings or clear its saved authentication. You can reconnect later with the same endpoint.
If the browser does not open or the tools remain unavailable, see Get help.