Skip to main content
Glama
runpod

RunPod MCP Server

Official
by runpod

delete-endpoint

Remove a specific endpoint from the RunPod MCP Server by providing its ID to manage server resources effectively.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endpointIdYesID of the endpoint to delete

Implementation Reference

  • src/index.ts:468-489 (registration)
    Registration of the 'delete-endpoint' tool using server.tool, including inline schema and handler function.
    // Delete Endpoint
    server.tool(
      'delete-endpoint',
      {
        endpointId: z.string().describe('ID of the endpoint to delete'),
      },
      async (params) => {
        const result = await runpodRequest(
          `/endpoints/${params.endpointId}`,
          'DELETE'
        );
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      }
    );
  • Handler function that performs the DELETE request to RunPod API endpoint /endpoints/{endpointId} and returns the JSON result as text content.
    async (params) => {
      const result = await runpodRequest(
        `/endpoints/${params.endpointId}`,
        'DELETE'
      );
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Input schema validating the endpointId parameter using Zod.
    {
      endpointId: z.string().describe('ID of the endpoint to delete'),
    },
  • Reusable helper function for making authenticated HTTP requests to the RunPod API, used by all tools including delete-endpoint.
    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;
      }
    }

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