Skip to main content
Glama
runpod

RunPod MCP Server

Official
by runpod

create-template

Create a new template on RunPod by specifying a Docker image and required name, with optional configuration for ports, environment variables, disk size, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the template
imageNameYesDocker image to use
isServerlessNoIs this a serverless template
portsNoPorts to expose
dockerEntrypointNoDocker entrypoint commands
dockerStartCmdNoDocker start commands
envNoEnvironment variables
containerDiskInGbNoContainer disk size in GB
volumeInGbNoVolume size in GB
volumeMountPathNoPath to mount the volume
readmeNoREADME content in markdown format

Implementation Reference

  • src/index.ts:1129-1169 (registration)
    Registration of the 'create-template' tool via server.tool(). Defines the tool name, Zod schema for parameters (name, imageName, isServerless, ports, dockerEntrypoint, dockerStartCmd, env, containerDiskInGb, volumeInGb, volumeMountPath, readme), and passes the handler.
    // Create Template
    server.tool(
      'create-template',
      {
        name: z.string().describe('Name for the template'),
        imageName: z.string().describe('Docker image to use'),
        isServerless: z
          .boolean()
          .optional()
          .describe('Is this a serverless template'),
        ports: z.array(z.string()).optional().describe('Ports to expose'),
        dockerEntrypoint: z
          .array(z.string())
          .optional()
          .describe('Docker entrypoint commands'),
        dockerStartCmd: z
          .array(z.string())
          .optional()
          .describe('Docker start commands'),
        env: z.record(z.string()).optional().describe('Environment variables'),
        containerDiskInGb: z
          .number()
          .optional()
          .describe('Container disk size in GB'),
        volumeInGb: z.number().optional().describe('Volume size in GB'),
        volumeMountPath: z.string().optional().describe('Path to mount the volume'),
        readme: z.string().optional().describe('README content in markdown format'),
      },
      async (params) => {
        const result = await runpodRequest('/templates', 'POST', params);
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      }
    );
  • Zod schema defining the input parameters for 'create-template': name (string), imageName (string), isServerless (optional boolean), ports (optional string array), dockerEntrypoint (optional string array), dockerStartCmd (optional string array), env (optional record of strings), containerDiskInGb (optional number), volumeInGb (optional number), volumeMountPath (optional string), readme (optional string).
    {
      name: z.string().describe('Name for the template'),
      imageName: z.string().describe('Docker image to use'),
      isServerless: z
        .boolean()
        .optional()
        .describe('Is this a serverless template'),
      ports: z.array(z.string()).optional().describe('Ports to expose'),
      dockerEntrypoint: z
        .array(z.string())
        .optional()
        .describe('Docker entrypoint commands'),
      dockerStartCmd: z
        .array(z.string())
        .optional()
        .describe('Docker start commands'),
      env: z.record(z.string()).optional().describe('Environment variables'),
      containerDiskInGb: z
        .number()
        .optional()
        .describe('Container disk size in GB'),
      volumeInGb: z.number().optional().describe('Volume size in GB'),
      volumeMountPath: z.string().optional().describe('Path to mount the volume'),
      readme: z.string().optional().describe('README content in markdown format'),
    },
  • Handler function for 'create-template'. Calls runpodRequest('/templates', 'POST', params) to create a new template via the RunPod API, then returns the JSON-stringified result as text content.
    async (params) => {
      const result = await runpodRequest('/templates', 'POST', params);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • The runpodRequest helper function used by the create-template handler. Makes authenticated HTTP requests to the RunPod REST API (base URL: https://rest.runpod.io/v1) using the API key from environment variable.
    async function runpodRequest(
      endpoint: string,
      method: string = 'GET',
      body?: Record<string, unknown>
    ) {
      const url = `${API_BASE_URL}${endpoint}`;
      const headers = {
        Authorization: `Bearer ${API_KEY}`,
        'Content-Type': 'application/json',
      };
    
      const options: NodeFetchRequestInit = {
        method,
        headers,
      };
    
      if (body && (method === 'POST' || method === 'PATCH')) {
        options.body = JSON.stringify(body);
      }
    
      try {
        const response = await fetch(url, options);
    
        if (!response.ok) {
          const errorText = await response.text();
          throw new Error(`RunPod API Error: ${response.status} - ${errorText}`);
        }
    
        // Some endpoints might not return JSON
        const contentType = response.headers.get('content-type');
        if (contentType && contentType.includes('application/json')) {
          return await response.json();
        }
    
        return { success: true, status: response.status };
      } catch (error) {
        console.error('Error calling RunPod API:', error);
        throw error;
      }
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/runpod/runpod-mcp-ts'

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