Skip to main content

Setting Up a Development Environment

You can set up a development environment with the AtScale MCP Server using an npm service called mcp-remote. For more information on mcp-remote, refer to the npm documentation.

Add the AtScale MCP Server to your development environment​

To add the MCP Server to your development environment:

  1. Obtain the client secret for the atscale-mcp client:

    1. In Design Center, in the left-side navigation, click Security. The Identity Broker opens.

    2. In the left-side navigation, click Clients.

    3. Click the atscale-mcp client.

    4. Go to the Credentials tab and copy the Client Secret.

      Important

      Do not regenerate the Client Secret.

  2. Add the following to your mcp.json file. Be sure to replace <atscale_url> with the URL for your AtScale instance, and <client_secret> with the secret you copied above.

    Note

    Lines 11–13 (the env block with NODE_TLS_REJECT_UNAUTHORIZED) are optional and skip SSL validation. To keep SSL validation enabled, remove lines 11–13 and the comma at the end of line 10.

    mcp.json
    {
    "mcpServers": {
    "atscale": {
    "command": "npx",
    "args": [
    "mcp-remote",
    "https://<atscale_url>/mcp",
    "--static-oauth-client-info",
    "{ \"client_id\": \"atscale-mcp\", \"client_secret\": \"<client_secret>\" }"
    ],
    "env": {
    "NODE_TLS_REJECT_UNAUTHORIZED": "0"
    }
    }
    }
    }

(Optional) Configure the MCP Server to use token authentication​

You can alternatively configure the MCP Server to use token authentication instead of OAuth.

To configure the MCP Server to use token authentication:

  1. In Design Center, generate an API token:

    1. Click the profile icon in the top-right corner. The Account panel opens.

    2. In the API Token section, click the generate icon. A token is generated.

      The API Token section of the Account panel, with the generate icon highlighted.

    3. Copy the token.

  2. Add the following to your mcp.json file. Be sure to replace <atscale_url> with the URL for your AtScale instance, and ... with the token you copied above.

    Note

    Line 12 (NODE_TLS_REJECT_UNAUTHORIZED) is optional and skips SSL validation; remove it to keep SSL validation enabled.

    mcp.json
    {
    "mcpServers": {
    "atscale-mcp": {
    "command": "npx",
    "args": [
    "mcp-remote",
    "https://<atscale_url>/mcp",
    "--header",
    "Authorization: Bearer ${AUTH_TOKEN}"
    ],
    "env": {
    "NODE_TLS_REJECT_UNAUTHORIZED": "0",
    "AUTH_TOKEN": "..."
    }
    }
    }
    }