@metronome/mcp 2.1.0 → 3.0.0

package/src/tools/v1/customers/plans/list-price-adjustments-customers-v1-plans.ts

@@ -1,59 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers.plans',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/v1/customers/{customer_id}/plans/{customer_plan_id}/priceAdjustments',
-  operationId: 'getPlanPriceAdjustments-v1',
-};
-
-export const tool: Tool = {
-  name: 'list_price_adjustments_customers_v1_plans',
-  description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nLists a customer plans adjustments. See the [price adjustments documentation](https://plans-docs.metronome.com/pricing/managing-plans/#price-adjustments) for details. This is a Plans (deprecated) endpoint. New clients should implement using Contracts.\n\n\n# Response Schema\n```json\n{\n  type: 'object',\n  properties: {\n    data: {\n      type: 'array',\n      items: {\n        $ref: '#/$defs/plan_list_price_adjustments_response'\n      }\n    },\n    next_page: {\n      type: 'string'\n    }\n  },\n  required: [    'data',\n    'next_page'\n  ],\n  $defs: {\n    plan_list_price_adjustments_response: {\n      type: 'object',\n      properties: {\n        charge_id: {\n          type: 'string'\n        },\n        charge_type: {\n          type: 'string',\n          enum: [            'usage',\n            'fixed',\n            'composite',\n            'minimum',\n            'seat'\n          ]\n        },\n        prices: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              adjustment_type: {\n                type: 'string',\n                description: 'Determines how the value will be applied.',\n                enum: [                  'fixed',\n                  'quantity',\n                  'percentage',\n                  'override'\n                ]\n              },\n              tier: {\n                type: 'number',\n                description: 'Used in pricing tiers.  Indicates at what metric value the price applies.'\n              },\n              value: {\n                type: 'number'\n              }\n            },\n            required: [              'adjustment_type'\n            ]\n          }\n        },\n        start_period: {\n          type: 'number'\n        },\n        quantity: {\n          type: 'number'\n        }\n      },\n      required: [        'charge_id',\n        'charge_type',\n        'prices',\n        'start_period'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      customer_plan_id: {
-        type: 'string',
-      },
-      limit: {
-        type: 'integer',
-        description: 'Max number of results that should be returned',
-      },
-      next_page: {
-        type: 'string',
-        description: 'Cursor that indicates where the next page of results should start.',
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['customer_id', 'customer_plan_id'],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  const response = await client.v1.customers.plans.listPriceAdjustments(body).asResponse();
-  return asTextContentResult(await maybeFilter(jq_filter, await response.json()));
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/customers/preview-events-v1-customers.ts

@@ -1,75 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customers/{customer_id}/previewEvents',
-  operationId: 'previewCustomerEvents-v1',
-};
-
-export const tool: Tool = {
-  name: 'preview_events_v1_customers',
-  description:
-    "Preview how a set of events will affect a customer's invoices. Generates draft invoices for a customer using their current contract configuration and the provided events.  This is useful for testing how new events will affect the customer's invoices before they are actually processed. Customers on contracts with SQL billable metrics are not supported.\n",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      events: {
-        type: 'array',
-        description:
-          'Array of usage events to include in the preview calculation. Must contain at least one event in `merge` mode.\n',
-        items: {
-          type: 'object',
-          properties: {
-            event_type: {
-              type: 'string',
-            },
-            properties: {
-              type: 'object',
-              additionalProperties: true,
-            },
-            timestamp: {
-              type: 'string',
-              description: 'RFC 3339 formatted. If not provided, the current time will be used.',
-            },
-            transaction_id: {
-              type: 'string',
-              description:
-                'Optional unique identifier for event deduplication. When provided, preview events are automatically deduplicated against historical events from the past 34 days.  Duplicate transaction IDs within the same request will return an error.\n',
-            },
-          },
-          required: ['event_type'],
-        },
-      },
-      mode: {
-        type: 'string',
-        description:
-          "Controls how the provided events are combined with existing usage data. Use `replace` to calculate the preview as if these are the only events for the customer, ignoring all historical usage.  Use `merge` to combine these events with the customer's existing usage.  Defaults to `replace`.",
-        enum: ['replace', 'merge'],
-      },
-      skip_zero_qty_line_items: {
-        type: 'boolean',
-        description: 'When `true`, line items with zero quantity are excluded from the response.',
-      },
-    },
-    required: ['customer_id', 'events'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  return asTextContentResult(await client.v1.customers.previewEvents(body));
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/customers/retrieve-billing-configurations-v1-customers.ts

@@ -1,50 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/getCustomerBillingProviderConfigurations',
-  operationId: 'getCustomerBillingProviderConfigurations-v1',
-};
-
-export const tool: Tool = {
-  name: 'retrieve_billing_configurations_v1_customers',
-  description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nReturns all billing configurations previously set for the customer. Use during the contract provisioning process to fetch the `billing_provider_configuration_id` needed to set the contract billing configuration.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/customer_retrieve_billing_configurations_response',\n  $defs: {\n    customer_retrieve_billing_configurations_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'array',\n          items: {\n            type: 'object',\n            properties: {\n              id: {\n                type: 'string',\n                description: 'ID of this configuration; can be provided as the billing_provider_configuration_id when creating a contract.'\n              },\n              archived_at: {\n                type: 'string',\n                format: 'date-time'\n              },\n              billing_provider: {\n                type: 'string',\n                description: 'The billing provider set for this configuration.',\n                enum: [                  'aws_marketplace',\n                  'stripe',\n                  'netsuite',\n                  'custom',\n                  'azure_marketplace',\n                  'quickbooks_online',\n                  'workday',\n                  'gcp_marketplace',\n                  'metronome'\n                ]\n              },\n              configuration: {\n                type: 'object',\n                description: 'Configuration for the billing provider. The structure of this object is specific to the billing provider.',\n                additionalProperties: true\n              },\n              customer_id: {\n                type: 'string'\n              },\n              delivery_method: {\n                type: 'string',\n                description: 'The method to use for delivering invoices to this customer.',\n                enum: [                  'direct_to_billing_provider',\n                  'aws_sqs',\n                  'tackle',\n                  'aws_sns'\n                ]\n              },\n              delivery_method_configuration: {\n                type: 'object',\n                description: 'Configuration for the delivery method. The structure of this object is specific to the delivery method.',\n                additionalProperties: true\n              },\n              delivery_method_id: {\n                type: 'string',\n                description: 'ID of the delivery method to use for this customer.'\n              }\n            },\n            required: [              'id',\n              'archived_at',\n              'billing_provider',\n              'configuration',\n              'customer_id',\n              'delivery_method',\n              'delivery_method_configuration',\n              'delivery_method_id'\n            ]\n          }\n        }\n      },\n      required: [        'data'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      include_archived: {
-        type: 'boolean',
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['customer_id'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  return asTextContentResult(
-    await maybeFilter(jq_filter, await client.v1.customers.retrieveBillingConfigurations(body)),
-  );
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/customers/retrieve-v1-customers.ts

@@ -1,47 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers',
-  operation: 'read',
-  tags: [],
-  httpMethod: 'get',
-  httpPath: '/v1/customers/{customer_id}',
-  operationId: 'getCustomer-v1',
-};
-
-export const tool: Tool = {
-  name: 'retrieve_v1_customers',
-  description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nGet detailed information for a specific customer by their Metronome ID. Returns customer profile data including name, creation date, ingest aliases, configuration settings, and custom fields. Use this endpoint to fetch complete customer details for billing operations or account management.\n\nNote: If searching for a customer billing configuration, use the `/getCustomerBillingConfigurations` endpoint.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/customer_retrieve_response',\n  $defs: {\n    customer_retrieve_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/customer_detail'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    customer_detail: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'the Metronome ID of the customer'\n        },\n        created_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was created.',\n          format: 'date-time'\n        },\n        custom_fields: {\n          type: 'object',\n          description: 'Custom fields to be added eg. { \"key1\": \"value1\", \"key2\": \"value2\" }',\n          additionalProperties: true\n        },\n        customer_config: {\n          type: 'object',\n          properties: {\n            salesforce_account_id: {\n              type: 'string',\n              description: 'The Salesforce account ID for the customer'\n            }\n          },\n          required: [            'salesforce_account_id'\n          ]\n        },\n        external_id: {\n          type: 'string',\n          description: '(deprecated, use ingest_aliases instead) the first ID (Metronome or ingest alias) that can be used in usage events'\n        },\n        ingest_aliases: {\n          type: 'array',\n          description: 'aliases for this customer that can be used instead of the Metronome customer ID in usage events',\n          items: {\n            type: 'string'\n          }\n        },\n        name: {\n          type: 'string'\n        },\n        updated_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was last updated.',\n          format: 'date-time'\n        },\n        archived_at: {\n          type: 'string',\n          description: 'RFC 3339 timestamp indicating when the customer was archived. Null if the customer is active.',\n          format: 'date-time'\n        },\n        current_billable_status: {\n          type: 'object',\n          description: 'This field\\'s availability is dependent on your client\\'s configuration.',\n          properties: {\n            value: {\n              type: 'string',\n              enum: [                'billable',\n                'unbillable'\n              ]\n            },\n            effective_at: {\n              type: 'string',\n              format: 'date-time'\n            }\n          },\n          required: [            'value'\n          ]\n        }\n      },\n      required: [        'id',\n        'created_at',\n        'custom_fields',\n        'customer_config',\n        'external_id',\n        'ingest_aliases',\n        'name',\n        'updated_at'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['customer_id'],
-  },
-  annotations: {
-    readOnlyHint: true,
-  },
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  return asTextContentResult(await maybeFilter(jq_filter, await client.v1.customers.retrieve(body)));
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/customers/set-billing-configurations-v1-customers.ts

@@ -1,86 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/setCustomerBillingProviderConfigurations',
-  operationId: 'setCustomerBillingProviderConfigurations-v1',
-};
-
-export const tool: Tool = {
-  name: 'set_billing_configurations_v1_customers',
-  description:
-    "Create a billing configuration for a customer. Once created, these configurations are available to associate to a contract and dictates which downstream system to collect payment in or send the invoice to. You can create multiple configurations per customer. The configuration formats are distinct for each downstream provider.\n\n### Use this endpoint to:\n- Add the initial configuration to an existing customer. Once created, the billing configuration can then be associated to the customer's contract.\n- Add a new configuration to an existing customer. This might be used as part of an upgrade or downgrade workflow where the customer was previously billed through system A (e.g. Stripe) but will now be billed through system B (e.g. AWS). Once created, the new configuration can then be associated to the customer's contract.\n- Multiple configurations can be added per destination. For example, you can create two Stripe billing configurations for a Metronome customer that each have a distinct `collection_method`.\n\n### Delivery method options:\n- `direct_to_billing_provider`: Use when Metronome should send invoices directly to the billing provider's API (e.g., Stripe, NetSuite). This is the most common method for automated billing workflows.\n- `tackle`: Use specifically for AWS Marketplace transactions that require Tackle's co-selling platform for partner attribution and commission tracking.\n- `aws_sqs`: Use when you want invoice data delivered to an AWS SQS queue for custom processing before sending to your billing system.\n- `aws_sns`: Use when you want invoice notifications published to an AWS SNS topic for event-driven billing workflows.\n\n### Key response fields: \nThe id for the customer billing configuration. This id can be used to associate the billing configuration to a contract.\n\n### Usage guidelines:\nMust use the `delivery_method_id` if you have multiple Stripe accounts connected to Metronome.\n",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      data: {
-        type: 'array',
-        items: {
-          type: 'object',
-          properties: {
-            billing_provider: {
-              type: 'string',
-              description: 'The billing provider set for this configuration.',
-              enum: [
-                'aws_marketplace',
-                'stripe',
-                'netsuite',
-                'custom',
-                'azure_marketplace',
-                'quickbooks_online',
-                'workday',
-                'gcp_marketplace',
-                'metronome',
-              ],
-            },
-            customer_id: {
-              type: 'string',
-            },
-            configuration: {
-              type: 'object',
-              description:
-                'Configuration for the billing provider. The structure of this object is specific to the billing provider and delivery method combination. Defaults to an empty object, however, for most billing provider + delivery method combinations, it will not be a valid configuration.  For AWS marketplace configurations, the aws_is_subscription_product flag can be used to indicate a product with usage-based pricing.  More information can be found [here](https://docs.metronome.com/invoice-customers/solutions/marketplaces/invoice-aws/#provision-aws-marketplace-customers-in-metronome).',
-              additionalProperties: true,
-            },
-            delivery_method: {
-              type: 'string',
-              description:
-                'The method to use for delivering invoices to this customer. If not provided, the `delivery_method_id` must be provided.',
-              enum: ['direct_to_billing_provider', 'aws_sqs', 'tackle', 'aws_sns'],
-            },
-            delivery_method_id: {
-              type: 'string',
-              description:
-                'ID of the delivery method to use for this customer. If not provided, the `delivery_method` must be provided.',
-            },
-            tax_provider: {
-              type: 'string',
-              description:
-                'Specifies which tax provider Metronome should use for tax calculation when billing through Stripe. This is only supported for Stripe billing provider configurations with auto_charge_payment_intent or manual_charge_payment_intent collection methods.',
-              enum: ['anrok', 'avalara', 'stripe'],
-            },
-          },
-          required: ['billing_provider', 'customer_id'],
-        },
-      },
-    },
-    required: ['data'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  const response = await client.v1.customers.setBillingConfigurations(body).asResponse();
-  return asTextContentResult(await response.text());
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/customers/set-ingest-aliases-v1-customers.ts

@@ -1,45 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customers/{customer_id}/setIngestAliases',
-  operationId: 'setIngestAliases-v1',
-};
-
-export const tool: Tool = {
-  name: 'set_ingest_aliases_v1_customers',
-  description:
-    'Sets the ingest aliases for a customer. Use this endpoint to associate a Metronome customer with an internal ID for easier tracking between systems. Ingest aliases can be used in the `customer_id` field when sending usage events to Metronome. \n\n### Usage guidelines:\n- This call is idempotent and fully replaces the set of ingest aliases for the given customer.\n- Switching an ingest alias from one customer to another will associate all corresponding usage to the new customer.\n- Use multiple ingest aliases to model child organizations within a single Metronome customer.\n',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      ingest_aliases: {
-        type: 'array',
-        items: {
-          type: 'string',
-        },
-      },
-    },
-    required: ['customer_id', 'ingest_aliases'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  const response = await client.v1.customers.setIngestAliases(body).asResponse();
-  return asTextContentResult(await response.text());
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/customers/set-name-v1-customers.ts

@@ -1,50 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customers/{customer_id}/setName',
-  operationId: 'setCustomerName-v1',
-};
-
-export const tool: Tool = {
-  name: 'set_name_v1_customers',
-  description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nUpdates the display name for a customer record. Use this to correct customer names, update business names after rebranding, or maintain accurate customer information for invoicing and reporting. Returns the updated customer object with the new name applied immediately across all billing documents and interfaces.\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/customer_set_name_response',\n  $defs: {\n    customer_set_name_response: {\n      type: 'object',\n      properties: {\n        data: {\n          $ref: '#/$defs/customer'\n        }\n      },\n      required: [        'data'\n      ]\n    },\n    customer: {\n      type: 'object',\n      properties: {\n        id: {\n          type: 'string',\n          description: 'the Metronome ID of the customer'\n        },\n        external_id: {\n          type: 'string',\n          description: '(deprecated, use ingest_aliases instead) the first ID (Metronome or ingest alias) that can be used in usage events'\n        },\n        ingest_aliases: {\n          type: 'array',\n          description: 'aliases for this customer that can be used instead of the Metronome customer ID in usage events',\n          items: {\n            type: 'string'\n          }\n        },\n        name: {\n          type: 'string'\n        },\n        custom_fields: {\n          type: 'object',\n          description: 'Custom fields to be added eg. { \"key1\": \"value1\", \"key2\": \"value2\" }',\n          additionalProperties: true\n        }\n      },\n      required: [        'id',\n        'external_id',\n        'ingest_aliases',\n        'name'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      name: {
-        type: 'string',
-        description:
-          'The new name for the customer. This will be truncated to 160 characters if the provided name is longer.',
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['customer_id', 'name'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  return asTextContentResult(await maybeFilter(jq_filter, await client.v1.customers.setName(body)));
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/customers/update-config-v1-customers.ts

@@ -1,48 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.customers',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/customers/{customer_id}/updateConfig',
-  operationId: 'updateCustomerConfig-v1',
-};
-
-export const tool: Tool = {
-  name: 'update_config_v1_customers',
-  description:
-    'Update configuration settings for a specific customer, such as external system integrations (e.g., Salesforce account ID) and other customer-specific billing parameters. Use this endpoint to modify customer configurations without affecting core customer data like name or ingest aliases.\n',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      leave_stripe_invoices_in_draft: {
-        type: 'boolean',
-        description:
-          'Leave in draft or set to auto-advance on invoices sent to Stripe. Falls back to the client-level config if unset, which defaults to true if unset.',
-      },
-      salesforce_account_id: {
-        type: 'string',
-        description: 'The Salesforce account ID for the customer',
-      },
-    },
-    required: ['customer_id'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const body = args as any;
-  const response = await client.v1.customers.updateConfig(body).asResponse();
-  return asTextContentResult(await response.text());
-};
-
-export default { metadata, tool, handler };

package/src/tools/v1/dashboards/get-embeddable-url-v1-dashboards.ts

@@ -1,132 +0,0 @@
-// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
-
-import { maybeFilter } from '@metronome/mcp/filtering';
-import { Metadata, asTextContentResult } from '@metronome/mcp/tools/types';
-
-import { Tool } from '@modelcontextprotocol/sdk/types.js';
-import Metronome from '@metronome/sdk';
-
-export const metadata: Metadata = {
-  resource: 'v1.dashboards',
-  operation: 'write',
-  tags: [],
-  httpMethod: 'post',
-  httpPath: '/v1/dashboards/getEmbeddableUrl',
-  operationId: 'embeddableDashboard-v1',
-};
-
-export const tool: Tool = {
-  name: 'get_embeddable_url_v1_dashboards',
-  description:
-    "When using this tool, always use the `jq_filter` parameter to reduce the response size and improve performance.\n\nOnly omit if you're sure you don't need the data.\n\nGenerate secure, embeddable dashboard URLs that allow you to seamlessly integrate Metronome's billing visualizations directly into your application. This endpoint creates authenticated iframe-ready URLs for customer-specific dashboards, providing a white-labeled billing experience without building custom UI.\n\n### Use this endpoint to:\n- Embed billing dashboards directly in your customer portal or admin interface\n- Provide self-service access to invoices, usage data, and credit balances\n- Build white-labeled billing experiences with minimal development effort\n\n### Key response fields:\n- A secure, time-limited URL that can be embedded in an iframe\n- The URL includes authentication tokens and configuration parameters\n- URLs are customer-specific and respect your security settings\n\n### Usage guidelines:\n- Dashboard types: Choose from `invoices`, `usage`, or `commits_and_credits`\n- Customization options:\n    - `dashboard_options`: Configure whether you want invoices to show zero usage line items\n    - `color_overrides`: Match your brand's color palette\n    - `bm_group_key_overrides`: Customize how dimensions are displayed (for the usage embeddable dashboard)\n- Iframe implementation: Embed the returned URL directly in an iframe element\n- Responsive design: Dashboards automatically adapt to container dimensions\n\n\n# Response Schema\n```json\n{\n  $ref: '#/$defs/dashboard_get_embeddable_url_response',\n  $defs: {\n    dashboard_get_embeddable_url_response: {\n      type: 'object',\n      properties: {\n        data: {\n          type: 'object',\n          properties: {\n            url: {\n              type: 'string'\n            }\n          }\n        }\n      },\n      required: [        'data'\n      ]\n    }\n  }\n}\n```",
-  inputSchema: {
-    type: 'object',
-    properties: {
-      customer_id: {
-        type: 'string',
-      },
-      dashboard: {
-        type: 'string',
-        description: 'The type of dashboard to retrieve.',
-        enum: ['invoices', 'usage', 'credits', 'commits_and_credits'],
-      },
-      bm_group_key_overrides: {
-        type: 'array',
-        description: 'Optional list of billable metric group key overrides',
-        items: {
-          type: 'object',
-          properties: {
-            group_key_name: {
-              type: 'string',
-              description: 'The name of the billable metric group key.',
-            },
-            display_name: {
-              type: 'string',
-              description: 'The display name for the billable metric group key',
-            },
-            value_display_names: {
-              type: 'object',
-              description:
-                '<key, value> pairs of the billable metric group key values and their display names. e.g. {"a": "Asia", "b": "Euro"}',
-              additionalProperties: true,
-            },
-          },
-          required: ['group_key_name'],
-        },
-      },
-      color_overrides: {
-        type: 'array',
-        description: 'Optional list of colors to override',
-        items: {
-          type: 'object',
-          properties: {
-            name: {
-              type: 'string',
-              description: 'The color to override',
-              enum: [
-                'Gray_dark',
-                'Gray_medium',
-                'Gray_light',
-                'Gray_extralight',
-                'White',
-                'Primary_medium',
-                'Primary_light',
-                'UsageLine_0',
-                'UsageLine_1',
-                'UsageLine_2',
-                'UsageLine_3',
-                'UsageLine_4',
-                'UsageLine_5',
-                'UsageLine_6',
-                'UsageLine_7',
-                'UsageLine_8',
-                'UsageLine_9',
-                'Primary_green',
-                'Primary_red',
-                'Progress_bar',
-                'Progress_bar_background',
-              ],
-            },
-            value: {
-              type: 'string',
-              description: 'Hex value representation of the color',
-            },
-          },
-        },
-      },
-      dashboard_options: {
-        type: 'array',
-        description: 'Optional dashboard specific options',
-        items: {
-          type: 'object',
-          properties: {
-            key: {
-              type: 'string',
-              description: 'The option key name',
-            },
-            value: {
-              type: 'string',
-              description: 'The option value',
-            },
-          },
-          required: ['key', 'value'],
-        },
-      },
-      jq_filter: {
-        type: 'string',
-        title: 'jq Filter',
-        description:
-          'A jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available.\n\nFor example: to include only the `name` field in every object of a results array, you can provide ".results[].name".\n\nFor more information, see the [jq documentation](https://jqlang.org/manual/).',
-      },
-    },
-    required: ['customer_id', 'dashboard'],
-  },
-  annotations: {},
-};
-
-export const handler = async (client: Metronome, args: Record<string, unknown> | undefined) => {
-  const { jq_filter, ...body } = args as any;
-  return asTextContentResult(await maybeFilter(jq_filter, await client.v1.dashboards.getEmbeddableURL(body)));
-};
-
-export default { metadata, tool, handler };