Skip to main content
Glama
DynamicEndpoints

pocketbase-mcp-server

create_stripe_customer

Generate a new customer profile in Stripe using this tool from pocketbase-mcp-server, enabling streamlined integration with Stripe for payment management and customer tracking.

Instructions

Create a new customer in Stripe

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core helper method implementing Stripe customer creation: checks for duplicates in PocketBase, creates in Stripe API, saves to PocketBase.
    async createCustomer(data: {
      email: string;
      name?: string;
      userId?: string;
      metadata?: Record<string, any>;
    }): Promise<StripeCustomer> {
      try {      // Check if customer already exists
        const existingCustomer = await this.pb.collection('stripe_customers')
          .getFirstListItem(`email="${data.email}"`)
          .catch(() => null);
    
        if (existingCustomer) {
          return existingCustomer as StripeCustomer;
        }
    
        // Create customer in Stripe
        const stripeCustomer = await this.stripe.customers.create({
          email: data.email,
          name: data.name,
          metadata: {
            userId: data.userId || '',
            ...data.metadata,
          },
        });
    
        // Save to PocketBase
        const customerRecord = await this.pb.collection('stripe_customers').create({
          email: data.email,
          name: data.name,
          stripeCustomerId: stripeCustomer.id,
          userId: data.userId,
          metadata: data.metadata || {},
        });
    
        return customerRecord as unknown as StripeCustomer;
      } catch (error: any) {
        throw new Error(`Failed to create customer: ${error.message}`);
      }
    }
  • Registers the create_stripe_customer MCP tool on the server, provides input schema, and defines handler that uses StripeService.createCustomer
    export function registerTools(server: any, pb: any): void {
      server.tool('create_stripe_customer', 'Create a Stripe customer', { type: 'object', properties: { email: { type: 'string' }, name: { type: 'string' } } }, async (args: any) => {
        const stripeService = new StripeService(pb);
        const customer = await stripeService.createCustomer({ email: args.email, name: args.name });
        return { success: true, customer };
      });
    }
  • Direct registration and detailed handler for create_stripe_customer in agent-simple.ts, with error handling and lazy service loading.
    'create_stripe_customer',
    'Create a new customer in Stripe',
    {
      type: 'object',
      properties: {
        email: { type: 'string', format: 'email', description: 'Customer email' },
        name: { type: 'string', description: 'Customer name' }
      },
      required: ['email']
    },
    async ({ email, name }) => {
      // Lazy load Stripe service
      await this.ensureStripeService();
      
      if (!this.stripeService) {
        return {
          content: [{
            type: 'text',
            text: JSON.stringify({
              error: 'Stripe service not available. Please set STRIPE_SECRET_KEY environment variable.'
            })
          }]
        };
      }
    
      try {
        const customer = await this.stripeService.createCustomer({ email, name });
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(customer, null, 2)
          }]
        };
      } catch (error: any) {
        return {
          content: [{
            type: 'text',
            text: JSON.stringify({
              error: `Failed to create Stripe customer: ${error.message}`
            })
          }]
        };
      }
    }
  • Tool schema definition in the static tools list returned by tools/list in Cloudflare Worker mode.
      name: 'create_stripe_customer',
      description: 'Create a new customer in Stripe',
      inputSchema: {
        type: 'object',
        properties: {
          email: { type: 'string', format: 'email', description: 'Customer email' },
          name: { type: 'string', description: 'Customer name' }
        },
        required: ['email']
      }
    },
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. 'Create' implies a write/mutation operation, but it doesn't disclose behavioral traits like required permissions, rate limits, error handling, or what happens on success/failure. It minimally meets baseline by stating the action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with zero waste. It's front-loaded with the essential action and resource, making it highly efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 0 parameters and no output schema, the description is minimally complete—it states what the tool does. However, as a mutation tool with no annotations, it lacks context about behavior, errors, or output, leaving gaps that could hinder effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters, so no parameter documentation is needed. The description doesn't add parameter details, but with no parameters to explain, it appropriately avoids redundancy, earning a high baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create') and resource ('new customer in Stripe'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create_stripe_product' or 'create_stripe_payment_intent' beyond the resource type, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when-not-to-use scenarios, or comparisons to siblings like 'create_record' or 'send_custom_email', leaving the agent to infer context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DynamicEndpoints/pocketbase-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server