Billy MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| billy_get_organizationB | Get organization details from Billy |
| billy_list_contactsA | List contacts with optional filtering and pagination |
| billy_get_contactA | Get a specific contact by ID |
| billy_create_contactB | Create a new contact in Billy |
| billy_update_contactB | Update an existing contact |
| billy_list_invoicesA | List invoices with optional filtering and pagination |
| billy_get_invoiceB | Get a specific invoice by ID |
| billy_create_invoiceB | Create a new invoice in Billy |
| billy_list_productsB | List products with optional filtering and pagination |
| billy_get_productB | Get a specific product by ID |
| billy_create_productB | Create a new product in Billy |
| billy_list_bank_paymentsA | List bank payments with optional filtering and pagination |
| billy_create_paymentB | Create a payment to mark invoices as paid |
| billy_list_billsA | List bills (vendor invoices) with optional filtering and pagination |
| billy_list_accountsB | List chart of accounts |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Every tool targets a distinct resource and action, with clear separation between entities like contacts, invoices, products, payments, bills, and accounts. List/get/create/update operations are specific to their subject, and even similar tools like list_bills and list_invoices are distinguished by the vendor invoice descriptor.
All tool names follow the consistent pattern 'billy_<verb>_<entity>' using snake_case throughout. The verbs (list, get, create, update) are uniform and predictable, making it easy to infer functionality from the name.
With 15 tools, the server is at the upper boundary of the ideal range but remains well-scoped for an accounting/billing API. Each tool represents a meaningful operation across a coherent set of resources without redundancy.
The core accounting workflows are covered: contacts (CRUD minus delete), invoices (create/list/get), products (create/list/get), payments (create), and supporting lists for bills and accounts. Minor gaps like invoice updates or product updates exist, but agents can work around them or these may be deliberately omitted for compliance reasons.