scalekit

The Scalekit MCP Server provides a secure, OAuth-protected interface to Scalekit's identity and access management platform. It exposes a rich set of tools for environment, organization, workspace, and connection management, enabling AI agents to perform tasks such as listing environments, creating and managing organizations and users, configuring OIDC connections, and generating admin portal links. Clients can connect to the MCP server via the standard MCP tooling (for example through VS Code, Claude Desktop, Cursor, Windsurf, or other MCP clients) and invoke the available environment, workspace, organization, and connection operations through the provided command surface.

To use the server, point your MCP client to the Scalekit endpoint and configure the mcp-remote proxy with the server URL. The recommended integration uses npx mcp-remote with the Scalekit MCP server URL, allowing you to access all supported tools within your preferred client. The available tool groups include Environment Management (list/environments, get details, manage roles and scopes), Workspace Management (list members, invite), Organization Management (list, create, admin portal links, users), and Connection Management (list and configure OIDC connections).

When operating in OAuth mode, the server authenticates API calls via Scalekit's identity platform, ensuring secure access to sensitive actions like creating users or configuring environments. When used with the mcp-remote proxy, you gain a consistent, cross-client experience across VS Code, Claude Desktop, Cursor, Windsurf, and other MCP clients.

Prerequisites:

• Node.js and npm installed on your machine (required to run with npx mcp-remote).
• Internet access to fetch the mcp-remote package via npm.
• Access to the Scalekit MCP endpoint (https://mcp.scalekit.com/).

Installation steps:

1. Verify Node.js and npm are installed: node -v npm -v

2. Use npx to set up the Scalekit MCP server proxy configuration in your MCP client The recommended approach is to reference the Scalekit MCP server via npx mcp-remote with the target URL:

   npx -y mcp-remote https://mcp.scalekit.com/

3. For VS Code, Claude Desktop, Cursor, Windsurf, or other MCP clients, add the Scalekit server configuration to your client config as shown in the README examples. The configuration typically looks like:

   { "mcpServers": { "scalekit": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.scalekit.com/"] } } }

4. If you prefer running a local proxy setup, you can install mcp-remote globally and run it with the Scalekit URL, then point your MCP client to the local proxy. Consult your MCP client documentation for any client-specific steps.

5. Ensure your environment variables and OAuth credentials (if applicable) are configured in the MCP client or the proxy by following Scalekit documentation.

Tips and notes:

• The server uses OAuth for secure access; ensure your client is configured with the appropriate authentication flow and tokens.
• The mcp-remote proxy configuration is the recommended way to connect from various MCP clients; keep the proxy URL up to date if Scalekit changes endpoints.
• If you encounter connection issues, verify network access to https://mcp.scalekit.com/ and check that your MCP client is using the same version of the mcp-remote proxy compatible with Scalekit.
• Access controls: use the environment, organization, and project scopes to limit actions according to your security requirements.
• Review the official MCP guide for Scalekit for any client-specific integration nuances or newly introduced tools.