NeuralSeek MCP

Connect to a NeuralSeek MCP server, discover its tools, and invoke tools from your editor.

In editors implementing VS Code's MCP server definition provider API, this extension also registers NeuralSeek for compatible chat agents.

Requirements

• VS Code 1.102 or newer, or a compatible desktop editor.
• A trusted workspace.
• A NeuralSeek MCP Streamable HTTP endpoint over HTTPS.
• An API key accepted with Authorization: Bearer YOUR_API_KEY.
• Network access from the extension host to the endpoint.

This extension is not a browser-only extension.

When using Remote SSH, containers, or similar remote environments, connections originate from the machine running the workspace extension host.

Configure and verify

1. Run NeuralSeek: Configure MCP Connection.
2. Enter the complete MCP endpoint URL provided by NeuralSeek.
3. Enter the API key without the Bearer prefix.
4. Run NeuralSeek: Test MCP Connection.
5. Confirm that initialization succeeds and tools are discovered.

Use the actual MCP endpoint, not a general REST API endpoint. The extension does not append /mcp or guess an endpoint path.

Use tools manually

Run NeuralSeek: List MCP Tools to view tool names, descriptions, and input schemas.

Run NeuralSeek: Call MCP Tool to:

1. Select a tool.
2. View its input schema.
3. Enter arguments as a JSON object.
4. Confirm the call.
5. View the returned MCP result.

Tool arguments are checked for JSON-object syntax; the server validates the tool-specific schema.

Tool calls may read or change data. Calls are not automatically retried. If a call fails after transmission, check the service before retrying.

Results may contain sensitive service data. They are opened in unsaved editor documents; review them before saving or sharing.

The manual client does not provide sampling, roots, or elicitation handlers. Tools requiring those optional client capabilities may not work manually.

Use tools in a chat agent

Run NeuralSeek: Show Integration Status.

If native registration is available:

1. Open the Command Palette.
2. Run MCP: List Servers.
3. Select NeuralSeek and start it.
4. Approve the editor's server trust prompts.
5. Enable NeuralSeek tools in the agent's tool picker.
6. Use an agent/model that supports tool calls.

UI labels may differ between compatible editors.

The editor manages this native MCP session. The manual test commands use separate short-lived sessions.

Restart the native server after replacing credentials or changing endpoints.

Open VSX compatibility

Open VSX is a registry, not an MCP runtime.

An editor may install this extension but lack native MCP provider support. The manual connection and tool commands can still work.

Agents such as Cline, Roo Code, or Continue may maintain separate MCP configuration. This extension does not automatically modify those files or inject tools into those agents.

Configure the same endpoint and bearer authentication in that agent using its documented remote MCP settings.

Commands

Security

• HTTPS is required.
• API keys are stored using the editor's SecretStorage.
• Keys are associated with normalized endpoint URLs.
• Keys are not stored in settings or included in the extension package.
• Endpoint configuration is machine-scoped.
• Raw transport errors and credentials are not logged.
• Manual requests refuse HTTP redirects.
• Native MCP transport behavior is controlled by the editor.
• No network connection is made merely by activating the extension.

Do not put credentials in endpoint URLs.

Changing endpoints leaves the previous endpoint's saved key in SecretStorage. Configure that endpoint again to delete its key.

Deleting a saved key does not revoke it at NeuralSeek or remove credentials already held by a running native connection. Stop that connection and revoke the key at NeuralSeek when necessary.

Troubleshooting

Configuration saves, but connection fails

Check the full MCP endpoint, bearer key, network access, TLS certificates, and Streamable HTTP support.

An endpoint redirect is rejected by the manual client. Use the final, canonical endpoint URL.

Connection works, but tools are missing in chat

Manual tool discovery and agent integration are separate.

Check integration status, start the native MCP server, enable its tools, and confirm that the agent consumes the editor's native MCP providers.

If your agent has separate MCP settings, configure NeuralSeek there.

Zero tools are discovered

The server completed discovery but advertised no tools. Check the NeuralSeek server configuration, permissions, and account access.

Tool result contains isError: true

The MCP request completed, but the tool reported an application-level error. Inspect the returned content.

License

MIT