mcp

IcePanel MCP Server acts as the bridge between IcePanel and your MCP clients such as Claude Desktop, Cursor, or Windsurf. It reads your IcePanel API credentials and organization context to enable secure, authenticated access to organization resources and tools via MCP clients. Once configured in your MCP client, the server will handle provisioning, authentication, and routing of requests to the appropriate IcePanel endpoints, allowing you to manage organization-specific tools from within your MCP-enabled workflow. The example configuration demonstrates how to inject your API key and organization identifier so the MCP client can initialize the connection to IcePanel. After setup, you can use your MCP client as usual to request tools, manage prompts, or access organization resources that IcePanel exposes through the MCP server.

Prerequisites:\n- Node.js v18+ (LTS recommended)\n- An MCP client that supports MCP servers (e.g., Claude Desktop, Cursor, Windsurf)\n- An IcePanel account with an Organization and API key.\n\nStep-by-step installation:\n1) Gather required environment details:\n - API_KEY: Your IcePanel API key (from IcePanel -> Organization Settings -> API keys)\n - ORGANIZATION_ID: Your IcePanel organization identifier\n - ICEPANEL_API_BASE_URL: Optional override for the API base URL if using a non-default environment.\n\n2) Configure the MCP client to use IcePanel MCP Server:\njson\n{\n "mcpServers": {\n "@icepanel/icepanel": {\n "command": "npx",\n "args": ["-y", "@icepanel/mcp-server@latest", "API_KEY=\"your-api-key\"", "ORGANIZATION_ID=\"your-org-id\""]\n }\n }\n}\n\n\n3) Run or install the MCP server via your MCP client workflow. The example uses npx to fetch and run the latest IcePanel MCP Server package.\n\n4) If you prefer a direct install/run approach outside the MCP client, you can run the server with:\nbash\n# Install and run via npx (as shown in the config)\nnpx -y @icepanel/mcp-server@latest API_KEY="your-api-key" ORGANIZATION_ID="your-org-id"\n\n\n5) Ensure required environment variables are set when running the server in your environment.\n

Tips and notes:\n- Keep your API key and organization ID confidential; do not commit them to public repositories.\n- If you are using a different IcePanel environment, set ICEPANEL_API_BASE_URL to point to the correct base URL.\n- The MCP server configuration is designed to be placed in your MCP client's config. Ensure the client supports loading MCP server configurations from the provided JSON structure.\n- If you encounter authentication issues, verify that the API key has the necessary permissions for the organization and that ORGANIZATION_ID matches your IcePanel organization.\n- The beta status means features may change; watch for updates and adjust the configuration accordingly.\n