Skip to main content
Glama
fadlee

PocketBase MCP Server

by fadlee

generate_typescript_interfaces

Generate TypeScript interfaces from PocketBase collections to enable type-safe database interactions in your applications.

Instructions

Generate TypeScript interfaces from PocketBase collections

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionsNoCollection names to generate interfaces for (empty for all)
optionsNoGeneration options

Implementation Reference

  • Handler factory function that creates the tool handler for generating TypeScript interfaces from PocketBase collections. The core logic fetches collections, maps fields to TS types, handles relations, and generates interface code.
    /**
     * Generate TypeScript interfaces from PocketBase collections
     */
    export function createGenerateTypescriptInterfacesHandler(pb: PocketBase): ToolHandler {
      return async (args: GenerateTypescriptInterfacesArgs = {}) => {
        try {
          const { collections: targetCollections = [], options = {} } = args;
          const includeRelations = options.includeRelations ?? true;
          
          // Get all collections or specific ones
          const allCollections = await pb.collections.getFullList();
          const collectionsToProcess = targetCollections.length > 0
            ? allCollections.filter(c => targetCollections.includes(c.name))
            : allCollections;
          
          const interfaces: string[] = [];
          
          // Generate base record interface
          interfaces.push("// Base record interface");
          interfaces.push("export interface BaseRecord {");
          interfaces.push("  id: string;");
          interfaces.push("  created: string;");
          interfaces.push("  updated: string;");
          interfaces.push("}");
          interfaces.push("");
          
          // Generate interfaces for each collection
          for (const collection of collectionsToProcess) {
            const interfaceName = toPascalCase(collection.name);
            const fields = collection.fields || [];
            
            interfaces.push(`// ${collection.name} collection`);
            interfaces.push(`export interface ${interfaceName} extends BaseRecord {`);
            
            for (const field of fields) {
              if (field.system) continue; // Skip system fields
              
              const fieldType = mapPocketBaseTypeToTypeScript(field.type, field);
              const optional = !field.required ? "?" : "";
              
              if (includeRelations && field.type === "relation") {
                const relatedCollection = field.options?.collectionId;
                if (relatedCollection) {
                  const relatedCollectionName = allCollections.find(
                    c => c.id === relatedCollection
                  )?.name;
                  
                  if (relatedCollectionName) {
                    const relatedInterface = toPascalCase(relatedCollectionName);
                    const isMultiple = field.options?.maxSelect !== 1;
                    
                    interfaces.push(
                      `  ${field.name}${optional}: ${isMultiple ? `${relatedInterface}[]` : relatedInterface};`
                    );
                    continue;
                  }
                }
              }
              
              interfaces.push(`  ${field.name}${optional}: ${fieldType};`);
            }
            
            interfaces.push("}");
            interfaces.push("");
          }
          
          // Add utility types
          interfaces.push("// Utility types");
          interfaces.push("export type RecordId = string;");
          interfaces.push("export type RecordTimestamp = string;");
          interfaces.push("");
          
          // Add collection names type
          const collectionNames = collectionsToProcess.map(c => `"${c.name}"`).join(" | ");
          interfaces.push(`export type CollectionName = ${collectionNames};`);
          
          const result = interfaces.join("\n");
          return createTextResponse(result);
        } catch (error: unknown) {
          throw handlePocketBaseError("generate TypeScript interfaces", error);
        }
      };
    }
  • Input schema validation for the generate_typescript_interfaces tool, defining expected arguments like collections and options.
    export const generateTypescriptInterfacesSchema = {
      type: "object",
      properties: {
        collections: {
          type: "array",
          description: "Collection names to generate interfaces for (empty for all)",
          items: {
            type: "string",
          },
        },
        options: {
          type: "object",
          description: "Generation options",
          properties: {
            includeRelations: {
              type: "boolean",
              description: "Whether to include relation types",
            },
          },
        },
      },
    };
  • src/server.ts:212-216 (registration)
    Tool registration in the main server, specifying name, description, input schema, and handler.
      name: "generate_typescript_interfaces",
      description: "Generate TypeScript interfaces from PocketBase collections",
      inputSchema: generateTypescriptInterfacesSchema,
      handler: createGenerateTypescriptInterfacesHandler(pb),
    },
  • TypeScript interface defining the argument shape for the tool handler, matching the schema.
    export interface GenerateTypescriptInterfacesArgs {
      collections?: string[];
      options?: {
        includeRelations?: boolean;
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It states what the tool does but doesn't describe output format (e.g., whether it returns code as a string or file), side effects (e.g., if it modifies the database), error conditions, or performance considerations (e.g., rate limits). This leaves critical behavioral traits unspecified for a code-generation tool.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action ('Generate TypeScript interfaces') and avoids redundancy, making it easy for an agent to parse quickly. Every part of the sentence contributes essential information.

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

Completeness2/5

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

Given the tool's complexity (generating code interfaces) and lack of annotations or output schema, the description is insufficient. It doesn't explain what the output looks like (e.g., TypeScript code string), how errors are handled, or dependencies on other tools (e.g., requiring collection schemas first). For a tool with no structured output documentation, more descriptive context is needed to guide effective use.

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

Parameters3/5

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

The schema description coverage is 100%, with clear documentation for both parameters ('collections' and 'options'). The description adds no additional parameter semantics beyond what's in the schema, such as examples of collection names or details on relation types. However, since the schema fully describes the parameters, the baseline score of 3 is appropriate as the description doesn't detract from the schema's clarity.

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

Purpose5/5

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

The description clearly states the specific action ('Generate TypeScript interfaces') and the resource ('from PocketBase collections'), using precise technical terminology. It distinguishes itself from sibling tools like 'generate_pb_schema' (which likely generates schema definitions) and 'get_collection_schema' (which retrieves schema data), making the purpose unambiguous.

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 (e.g., whether authentication is required), compare it to similar tools like 'generate_pb_schema', or specify scenarios where it's appropriate (e.g., for frontend development). The agent must infer usage from the tool name alone.

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

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/fadlee/dynamic-pocketbase-mcp'

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