Skip to main content
Glama
mattcoatsworth

ShipStation API MCP Server

get_store

Retrieve store details by providing a specific store ID using the ShipStation API MCP Server tool, facilitating efficient management of store-related data.

Input Schema

NameRequiredDescriptionDefault
storeIdYesStore ID to retrieve

Input Schema (JSON Schema)

{ "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "storeId": { "description": "Store ID to retrieve", "type": "number" } }, "required": [ "storeId" ], "type": "object" }

Implementation Reference

  • The async handler function that implements the core logic of the 'get_store' tool: fetches store details via shipStationClient.getStore and returns JSON-formatted response or error.
    handler: async ({ storeId }) => { try { const store = await shipStationClient.getStore(storeId); return { content: [{ type: "text", text: JSON.stringify(store, null, 2) }] }; } catch (error) { return { content: [{ type: "text", text: error.message }], isError: true }; } }
  • Zod input schema defining the 'storeId' parameter as a required number.
    schema: { storeId: z.number().describe("Store ID to retrieve") },
  • src/server.js:184-191 (registration)
    Batch registration of all tools, including 'get_store', with the MCP server via server.tool().
    ].forEach(tool => { server.tool( tool.name, tool.schema, tool.handler, { description: tool.description } ); });

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/mattcoatsworth/shipstation-mcp-server'

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