Pocket Invoice MCP
Company-scoped invoice, customer and PDF tools for AI assistants.
Sources and review
Checked against public documentation on . Suitability guidance is our editorial judgment; this is not a performance benchmark or an endorsement.
Independent businesses that want an AI client to prepare invoice documents within an existing account.
You need payment collection or independently verified permission and send-confirmation enforcement.
About Pocket Invoice MCP
Pocket Invoice MCP connects an authorized AI assistant to invoices, estimates, customer records and PDFs in a Pocket Invoice account. Its guide describes Streamable HTTP with company-scoped OAuth permissions, account limits and confirmation before sending documents. Recording a received payment updates a record and does not charge or refund a customer. This documentation review did not authorize an account or create, send or modify a document.
Before connecting: access and data
This record's specific permissions have not been reviewed by ASE. Read the publisher's documentation before copying setup or connecting.
- List the accounts, files and services the enabled tools can read, change or execute. Check your actual credentials and discovered tools.
- Use narrowly scoped credentials and read-only mode where supported. Review proposed writes before approving them; a generated configuration does not apply these limits for you.
- Local launch is not local-only data processing. External services receive requests, and your client may pass tool results to its model provider. Check both destinations before sharing private data.
- Keep keys and browser session files out of shared config, repositories and screenshots. Know how to disconnect the server and separately revoke its credentials or account sessions.