Skip to main content
Glama

post

Send POST HTTP requests to APIs with JSON or form data, including file uploads and authentication support.

Instructions

Make a pOST HTTP request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to make the POST request to
headersNoOptional headers to include in the request
bodyNoThe request body (JSON object, string, etc.)
requestTypeNoRequest type: 'json' for JSON data, 'form-data' for form data with file uploads
fieldFilesNoArray of field names that should be treated as files. Values can be URLs (http/https) for remote files or local file paths for local files. The system will automatically download remote files or read local files and include them as file attachments in the form data.
authNoOptional auth configuration to load a stored bearer token

Implementation Reference

  • Handler for the 'post' tool: extracts parameters, applies authentication headers if provided, validates URL, calls makeHttpRequest with POST method, and returns formatted response including status and data.
    case "post": { const url = String(args?.url || ''); const auth = args?.auth as AuthConfig | undefined; const headers = applyAuthHeader(args?.headers as Record<string, string> || {}, auth); const body = args?.body; const requestType = args?.requestType as 'json' | 'form-data' || 'json'; const fieldFiles = args?.fieldFiles as string[] || []; if (!url) { throw new Error("URL is required for POST request"); } const result = await makeHttpRequest('POST', { url, headers, body, requestType, fieldFiles }); return { content: [{ type: "text", text: `POST ${url}\nRequest Type: ${requestType}\nStatus: ${result.status} ${result.statusText}\nResponse: ${JSON.stringify(result.data, null, 2)}` }] }; }
  • src/index.ts:100-149 (registration)
    Registration of the 'post' tool in the ListTools response, defining its name, description, and input schema including parameters for URL, headers, body, requestType, fieldFiles, and auth.
    { name: "post", description: "Make a pOST HTTP request", inputSchema: { type: "object", properties: { url: { type: "string", description: "The URL to make the POST request to" }, headers: { type: "object", description: "Optional headers to include in the request", additionalProperties: { type: "string" } }, body: { description: "The request body (JSON object, string, etc.)" }, requestType: { type: "string", enum: ["json", "form-data"], description: "Request type: 'json' for JSON data, 'form-data' for form data with file uploads" }, fieldFiles: { type: "array", items: { type: "string" }, description: "Array of field names that should be treated as files. Values can be URLs (http/https) for remote files or local file paths for local files. The system will automatically download remote files or read local files and include them as file attachments in the form data." }, auth: { type: "object", description: "Optional auth configuration to load a stored bearer token", properties: { folder: { type: "string", description: "Folder where tokens are stored (tokens.json)" }, user_title: { type: "string", description: "User title to pick the token from storage (default: 'default')" } } } }, required: ["url"] } },
  • Input schema definition for the 'post' tool, specifying properties like url (required), headers, body, requestType (json|form-data), fieldFiles for file uploads, and auth configuration.
    inputSchema: { type: "object", properties: { url: { type: "string", description: "The URL to make the POST request to" }, headers: { type: "object", description: "Optional headers to include in the request", additionalProperties: { type: "string" } }, body: { description: "The request body (JSON object, string, etc.)" }, requestType: { type: "string", enum: ["json", "form-data"], description: "Request type: 'json' for JSON data, 'form-data' for form data with file uploads" }, fieldFiles: { type: "array", items: { type: "string" }, description: "Array of field names that should be treated as files. Values can be URLs (http/https) for remote files or local file paths for local files. The system will automatically download remote files or read local files and include them as file attachments in the form data." }, auth: { type: "object", description: "Optional auth configuration to load a stored bearer token", properties: { folder: { type: "string", description: "Folder where tokens are stored (tokens.json)" }, user_title: { type: "string", description: "User title to pick the token from storage (default: 'default')" } } } }, required: ["url"] }
  • Core helper function makeHttpRequest that executes the HTTP POST request, handling different body types (JSON or form-data with file uploads), logging, auth headers, and response parsing.
    async function makeHttpRequest(method: string, config: HttpRequestConfig) { try { server.sendLoggingMessage({ level: "info", data: `Starting ${method.toUpperCase()} request to: ${config.url}`, }); const options: NodeRequestInit = { method: method.toUpperCase(), headers: { ...config.headers, }, }; if (config.body && (method === 'POST' || method === 'PUT')) { if (config.requestType === 'form-data') { server.sendLoggingMessage({ level: "info", data: `Using form-data request type with fieldFiles: ${JSON.stringify(config.fieldFiles)}`, }); // Use FormData for form-data requests const formData = await createFormData(config.body, config.fieldFiles); options.body = formData as any; // Cast to any to handle type incompatibility server.sendLoggingMessage({ level: "info", data: `FormData prepared, not setting Content-Type header (will be auto-set with boundary)`, }); // Don't set Content-Type header for FormData, let the system set it with boundary } else { server.sendLoggingMessage({ level: "info", data: `Using JSON request type`, }); // Use JSON for regular requests options.headers = { 'Content-Type': 'application/json', ...options.headers, }; options.body = typeof config.body === 'string' ? config.body : JSON.stringify(config.body); server.sendLoggingMessage({ level: "info", data: `JSON body prepared: ${options.body}`, }); } } else if (!config.body && method !== 'GET' && method !== 'DELETE') { // Set default Content-Type for POST/PUT without body options.headers = { 'Content-Type': 'application/json', ...options.headers, }; } server.sendLoggingMessage({ level: "info", data: `Request headers: ${JSON.stringify(options.headers)}`, }); server.sendLoggingMessage({ level: "info", data: `Making HTTP request...`, }); const response = await fetch(config.url, options); server.sendLoggingMessage({ level: "info", data: `Response received: ${response.status} ${response.statusText}`, }); const responseText = await response.text(); server.sendLoggingMessage({ level: "info", data: `Response body: ${responseText}`, }); // Try to parse as JSON, fallback to text let responseData; try { responseData = JSON.parse(responseText); } catch { responseData = responseText; } // Store in history requestHistory.push({ method: method.toUpperCase(), config, timestamp: new Date() }); return { status: response.status, statusText: response.statusText, headers: Object.fromEntries(response.headers.entries()), data: responseData }; } catch (error) { server.sendLoggingMessage({ level: "error", data: `HTTP ${method.toUpperCase()} request failed: ${error instanceof Error ? error.message : String(error)}`, }); throw new Error(`HTTP ${method.toUpperCase()} request failed: ${error instanceof Error ? error.message : String(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/vilasone455/api-mcp'

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