MCP (Model Context Protocol) servers enable AI assistants like Claude to interact directly with the Measure API. With an MCP server, you can manage customers, subscriptions, invoices, and billing operations through natural language conversations with your AI assistant.
The official Measure MCP server will be released in Q2 2026.
Building your own MCP server
In the meantime, you can build a custom MCP server using our OpenAPI specification. The OpenAPI spec provides a complete definition of all Measure API endpoints, making it straightforward to generate an MCP server that works with any AI assistant that supports the Model Context Protocol.
Options for building
There are several approaches you can take to build an MCP server for Measure:
1. Generate with AI assistants
You can use Claude or other AI assistants to automatically generate an MCP server from the Measure OpenAPI specification. Simply provide the specification and ask the AI assistant to create an MCP server implementation in your preferred language.
2. Use MCP SDKs
The Anthropic MCP SDK provides tools and libraries for building MCP servers in TypeScript and Python. You can use these SDKs to create a custom server that wraps the Measure API.
3. Use OpenAPI-to-MCP conversion tools
Several community tools can automatically convert OpenAPI specifications into MCP servers, allowing you to generate a working server with minimal effort.
Setting up your MCP server
To build and configure your own MCP server:
- Download the Measure OpenAPI specification
- Create an API token from the Measure dashboard under Developers > API Token
- Use your preferred method to generate the MCP server from the OpenAPI specification
- Configure the server with your API token for authentication
Your API token should be kept secret and secure. Anyone with access to your token will be able to access Measure resources on your behalf.
Once your MCP server is configured and running, you can connect it to AI assistants like Claude to interact with Measure through natural language. You’ll be able to perform operations like creating customers, managing subscriptions, generating invoices, processing payments, and more.
Important considerations for bulk operations
Exercise caution with bulk write operations. When using an MCP server with AI assistants, it’s easy to execute bulk operations through natural language commands. However, certain actions—such as canceling multiple subscriptions, deleting customers, or applying changes to large sets of records—can be irreversible and may have significant business impact.We recommend:
- Always review bulk operations before confirming execution
- Test bulk operations with a small subset of data first
- Be explicit about which customers or subscriptions should be affected
- Consider the downstream effects of bulk changes (e.g., invoice generation, payment processing)
- Maintain backups or records of data before performing bulk modifications
Some operations that require extra care include:
- Bulk subscription cancellations: Canceling multiple subscriptions at once will immediately stop billing for those customers
- Bulk pricing changes: Changing pricing for multiple subscriptions simultaneously will affect future invoices
- Bulk refunds: Processing refunds in bulk will immediately credit customer accounts and impact your revenue
- Bulk status changes: Changing subscription or customer status in bulk can affect access to your services
Always confirm the scope and impact of bulk operations before proceeding. When in doubt, perform operations one at a time or on a small test set first.
What you can do with an MCP server
With a Measure MCP server connected to your AI assistant, you can perform operations such as:
- Create and manage customers
- Set up and modify subscriptions
- Generate and send one-off invoices
- Process payments and refunds
- Manage products, pricing, and plans
- Handle credits, discounts, and promotions
The MCP server provides a conversational interface to the full Measure API, allowing you to manage your billing operations through natural language interactions.