N|Solid Console MCP Integration (IDE)
The N|Solid Console MCP server lets an AI assistant connect to the N|Solid Console through a standard MCP interface.
This guide shows how to add the N|Solid Console MCP server to your IDE/agent workflow (with Windsurf/VSCode as the example).
N|Solid MCP endpoint
By default, the N|Solid Console MCP server is exposed at:
https://{consoleID}.saas.nodesource.io.mcp
Authentication
The N|Solid Console MCP server authenticates using an N|Solid Accounts service token.
Create a dedicated service token for your IDE agent and only grant the permissions you want the agent to have.
You can do so by following this guide:
Configure the N|Solid MCP server in VSCode
The exact UI labels can change between VSCode versions, but the flow is generally:
- Open Settings in VSCode.
- Locate the MCP / MCP Servers section.
- Select Add Server.
- Choose a Remote / URL-based MCP server.
- Set the server URL to
https://{consoleID}.mcp.saas.nodesource.io. - Add your N|Solid Accounts service token to the server configuration (as a secret / environment variable, depending on what Windsurf supports).
You can also directly add the server to your IDE's mcp configuration file with the following format:
{
"mcpServers": {
"nsolid-console": {
"serverUrl": "https://{consoleID}.mcp.saas.nodesource.io",
"headers": {
"Authorization": "Bearer {YOUR_SERVICE_TOKEN}"
}
}
}
}
Keep the service token out of your repository. Store it in your IDE’s secret storage or environment-variable configuration.
Verifying the integration
After you add the server:
- Log into the N|Solid console that matches the org of your service token.
- Confirm the MCP server is listed as installed/enabled in your IDE.
- Run a safe, read-only tool first, such as asking the agent for a list of connected applications.
Tools
You can check the available tools by asking the agent to list them, or by checking the N|Solid Console API documentation by visiting the Settings page of your N|Solid Console instance. Navigate to the About section and click the API Reference link. Then scroll down to the MCP Tools section to see the available tools.
Troubleshooting
If tools are missing, re-check:
- The MCP server is running / reachable.
- The MCP server URL is correct (
https://{consoleID}.mcp.saas.nodesource.ioby default). - The service token is present in the MCP server configuration.
- The token has the permissions required for the tool you’re trying to use.