MCP integrations

The MCP Integrations settings page connects N|Solid Copilot, the AI assistant in the N|Solid Console, to Model Context Protocol (MCP) servers. This page covers the two available integrations: the N|Solid MCP Server, which Copilot requires, and the GitHub MCP Server, which lets Copilot open pull requests with the optimizations it recommends.

To open the page, click Settings in the N|Solid Console, expand Integrations in the left menu, and select MCP Integrations. You need the settings > mcp integrations permission (included in the admin role). See Role-based access control.

info

This page is about MCP servers that the Console's Copilot uses. To connect your own IDE or AI agent to the N|Solid Console's MCP server, see N|Solid Console MCP integration (IDE).

N|Solid MCP Server (required for Copilot)

N|Solid Copilot uses the N|Solid MCP Server integration to read your Console data and use runtime features such as profiling and heap sampling. Until the integration is installed and active, Copilot shows N|Solid MCP Server Required ("To ask Copilot questions, install the N|Solid MCP server in Settings.") instead of answering questions.

To install it:

1. Create a service token in NodeSource Accounts (accounts.nodesource.com > Service Tokens > New Service Token). See Service tokens.
2. Under N|Solid console API, select these permissions:
   • Make custom view
   • Make new action in view
   • View events historic
   • Assets
   • Custom filters
   • Dynamic configuration
   • Generate CPU profile
   • Generate heap snapshot
   • Generate heap sample
   • Generate SBOM
   • AI service complete agent
   • Security vulnerabilities
3. Copy the generated token key.
4. In the Console, go to Settings > Integrations > MCP Integrations and click Install N|Solid MCP Server.
5. On the integration page, click Install, paste the token into the N|Solid Service Token field, and click Save.

If the integration is active but has no stored token, Copilot shows N|Solid MCP Token Missing. Open the integration's Configure tab and save a valid token.

GitHub MCP Server

The GitHub MCP Server lets AI tools work with GitHub repositories, issues, and pull requests. The N|Solid Console uses GitHub's hosted remote GitHub MCP Server to create pull requests from Copilot's AI report workflow: when Copilot finds and benchmarks a faster version of a function, it can open a pull request with the change in your repository.

Prerequisites

Before you set up the GitHub integration, make sure you have:

• Administrative access to your GitHub organization or repository.
• Access to the MCP Integrations settings page in the N|Solid Console.
• A fine-grained GitHub personal access token (PAT), created as described in the next section. The same steps appear on the integration's About tab.

Create a fine-grained personal access token

1. In GitHub, click your profile picture, then click Settings.
2. In the left sidebar, click Developer settings.
3. Under Personal access tokens, click Fine-grained tokens, then click Generate new token.

Configure the token as follows.

Token name and expiration

• Enter a descriptive Token name, for example "N|Solid Console MCP".
• Set an Expiration date. 90 days or less is recommended.
• Optionally, add a Description that explains the token's purpose.

Resource owner

Choose the account or organization that owns the repositories. If you choose an organization, an organization admin may need to approve the token.

Repository access

Select Only select repositories, then choose the repositories where you want Copilot to create pull requests. Limiting access this way follows the principle of least privilege.

Repository permissions

The token needs these repository permissions:

• Contents: Read and write (to create branches and files)
• Pull requests: Read and write (to create and manage pull requests)
• Metadata: Read (included automatically)

Generate and save the token

Click Generate token, then copy the token right away and store it securely. You can't see it again after you leave the page.

Pending approval

If the resource owner is an organization that requires approval for fine-grained tokens, the token stays pending until an organization administrator reviews it. Ask your organization admin to approve the request.

Install the GitHub MCP Server

1. In the N|Solid Console, click Settings.

2. Expand Integrations in the left menu and select MCP Integrations.

3. Click Install GitHub MCP Server.

   

4. On the integration page, click Install. In the dialog that opens, paste your PAT into the GitHub Personal Access Token field and click Save.

   

Verify the installation

After installation, the GitHub entry on the MCP Integrations page shows Installed and the installation date, and the integration page shows an Installed badge.

Create a pull request from an optimization

After the GitHub integration is installed, Copilot can create pull requests for optimizations that pass benchmarking.

1. Start the optimization. Open a CPU profile and click AI Report.

2. Analysis and benchmarking. Copilot analyzes the profile, generates optimized versions of the hot functions, and benchmarks them.

3. Review the report. Copilot shows a detailed report based on the CPU profile, including optimized code for any function that performed better than the original.

   

4. Choose to create a pull request. Copilot lists the functions that are ready for a pull request. Click Create Pull Request to choose where to open it.

5. Select an organization. Choose a suggested organization, or type an organization name.

   

6. Select a repository. Choose a suggested repository, or type a repository name.

   

7. Select a branch. Choose the branch that Copilot should base the new pull request on.

   

8. Review the summary. Copilot shows the organization, repository, and branch you chose. Confirm to create the pull request.

   

When you confirm, Copilot:

1. Creates a new branch in your repository.

2. Commits the optimized code with a descriptive message.

3. Opens a pull request that includes the benchmark results and details about the optimization.

   

4. Shows the pull request URL in the Console.

   

If the GitHub MCP Server isn't installed yet

If you click Create Pull Request before the GitHub MCP Server is installed:

1. Copilot shows GitHub MCP Server Required.
2. Click View MCP Servers Page.
3. Complete the steps in Install the GitHub MCP Server.
4. Return to Copilot and create the pull request again.

Skip pull request creation

To skip the pull request for an optimization, click skip when Copilot offers to create one. The optimization report is kept, and you can apply the changes yourself later.

Manage the GitHub integration

View the integration. Go to Settings > Integrations > MCP Integrations and click the GitHub entry to see its status and the masked PAT on the Configure tab.

Change the token. Open the Configure tab, enter the new PAT, and click Save.

Disable or remove the integration. On the GitHub MCP Server integration page, open the status menu (Enabled) and choose Disabled to turn it off, or Uninstall to remove it. Uninstalling also deletes the stored PAT. To fully revoke access, also delete the token in GitHub.

Permissions and security

The GitHub MCP Server integration needs only the permissions you grant to your PAT:

• Contents: Read and write, to create branches and commit code.
• Pull requests: Read and write, to open pull requests.

Security details:

• Token lifetime: the integration uses your fine-grained PAT directly. It stays valid until the expiration date you set in GitHub or until you revoke it.
• Scoped access: the integration can reach only the repositories your token grants.
• Encrypted storage: on N|Solid SaaS, the stored token is encrypted with AWS KMS, and the Console shows only a masked version.
• Audit trail: all GitHub operations are logged for security review.

Troubleshooting

Repository not listed. If your repository doesn't appear in the list, type the repository and branch names yourself, as described in Create a pull request from an optimization.

Best practices

• Review pull requests promptly. Review and test Copilot-generated pull requests before you merge them.
• Test optimizations. Run your test suite on optimized code before you deploy it to production.

Additional resources

GitHub MCP Server:

• GitHub MCP Server repository
• Remote server documentation
• GitHub MCP Server policies and governance

GitHub personal access tokens:

• Managing your personal access tokens
• Permissions required for fine-grained personal access tokens

N|Solid Copilot:

• N|Solid Copilot
• Optimize performance with CPU profiles