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:
-
Obtain the client secret for the
atscale-mcpclient:-
In Design Center, in the left-side navigation, click Security. The Identity Broker opens.
-
In the left-side navigation, click Clients.
-
Click the
atscale-mcpclient. -
Go to the Credentials tab and copy the Client Secret.
ImportantDo not regenerate the Client Secret.
-
-
Add the following to your
mcp.jsonfile. Be sure to replace<atscale_url>with the URL for your AtScale instance, and<client_secret>with the secret you copied above.{
"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" # This line is optional and will skip SSL validation
}
}
}
}
(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:
-
In Design Center, generate an API token:
-
Click the profile icon in the top-right corner. The Account panel opens.
-
In the API Token section, click the generate icon. A token is generated.
-
Copy the token.
-
-
Add the following to your
mcp.jsonfile. Be sure to replace<atscale_url>with the URL for your AtScale instance.{
"mcpServers": {
"atscale-mcp": {
"command": "npx",
args": [
"mcp-remote",
"https://<atscale_url>/mcp",
"--header",
"Authorization: Bearer ${AUTH_TOKEN}"
],
"env": {
"NODE_TLS_REJECT_UNAUTHORIZED": "0" # This line is optional and will skip SSL validation
"AUTH_TOKEN": "..."
}
}
}
}