You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once enabled, the MCP server automatically starts when the extension loads, listening on a local HTTP endpoint. Each workspace gets a unique auto-allocated port, which is displayed in a status bar item as `MCP:<port>`.
46
+
3. The status bar will update to show `MCP:<port>` with the assigned port number.
51
47
52
-
#### Documentation Queries
48
+

53
49
54
-
The extension provides a separate MCP server for querying Deephaven documentation, which is enabled by default when the main MCP server is enabled.
50
+
This automatically sets `"deephaven.mcp.enabled": true` in your workspace settings (`.vscode/settings.json`). The MCP server starts immediately, listening on a local HTTP endpoint. Each workspace gets a unique port.
This setting controls whether documentation queries are available to AI assistants. When `deephaven.mcp.enabled`is `true`, the documentation server is automatically enabled unless `deephaven.mcp.docsEnabled` is set to `false`.
54
+
The Deephaven Documentation Searching skill connects to the [Deephaven Docs MCP server](https://deephaven.io/enterprise/docs/clients/mcp/#docs-server). The server is automatically configured for Github Copilot or can be manually configured for other agents as described in [Manual MCP Server Configuration](#manual-mcp-server-configuration). The extension skill makes AI assistants aware of the documentation capabilities. For more information about the Deephaven Docs MCP server itself, see the [official documentation](https://deephaven.io/enterprise/docs/clients/mcp/#docs-server).
59
55
60
-
To disable documentation queries while keeping the extension's MCP tools available:
56
+
The documentation server can be independently enabled/disabled via the `deephaven.mcp.docsEnabled` setting:
When `deephaven.mcp.enabled` is `true`, documentation queries are enabled by default. Set `deephaven.mcp.docsEnabled` to `false` to disable documentation queries while keeping the extension's MCP tools available.
70
61
71
-
When using GitHub Copilot in VS Code, the extension's MCP server is automatically configured and available once enabled. No additional configuration is required.
62
+
#### IDE-Specific Configuration
72
63
73
-
#### Windsurf
64
+
Different IDEs require different MCP server configuration:
74
65
75
-
Windsurf automatically detects and connects to the MCP server when the Deephaven extension is active. No additional configuration is required.
66
+
| IDE | Auto-Configured | MCP Configuration File |
|**Windsurf**| ✅ Yes (after user approval) |`~/.codeium/windsurf/mcp_config.json`|
70
+
|**Claude in VS Code-based IDE**| ❌ No |`<wksp-folder>/.mcp.json`|
71
+
|**Cursor**| ❌ No |`<wksp-folder>/.cursor/mcp.json`|
72
+
|**Other VS Code-based IDEs**| ❌ No | Varies by IDE |
76
73
77
-
> **Note:** Since each workspace uses a unique port and Windsurf only supports user-level MCP configuration, the extension will automatically update the MCP configuration when a Windsurf window becomes active to match the current workspace's port. This has not been thoroughly tested and may require manual steps, such as restarting IDE/agent sessions.
74
+
#### Manual MCP Server Configuration
78
75
79
-
#### Other VS Code-based IDEs
76
+
For IDEs that require manual configuration (Cursor and other VS Code-based IDEs) or Claude running in VS Code-based IDEs, you'll need to configure the MCP server endpoint. The MCP server port is displayed in the status bar as `MCP:<port>` when running. You can click the status bar item to copy the full endpoint URL to your clipboard. The endpoint URL follows the format: `http://localhost:<port>/mcp`.
80
77
81
-
For other VS Code-based IDEs that support MCP, you may need to configure the MCP server endpoint in your IDE's settings.
78
+
**Cursor:**
82
79
83
-
The MCP server uses an auto-allocated port that varies per session. When the MCP server starts, a status bar item will display `MCP:<port>` showing the actual port being used. The endpoint URL follows the format:
80
+
Create a `.cursor/mcp.json` file in your workspace root:
> **Note:** The port is unique per workspace. If you switch workspaces, you may need to update your MCP configuration with the new port shown in the status bar. Most IDEs don't yet seem to support workspace-level MCP configs, so settings may have to be updated at the user level. This may also require restarting agent sessions, MCP tool caches, etc.
Replace `45678` with the actual port shown in the `MCP:<port>` status bar item.
114
+
> **Note:** This configuration should work for Claude running in any VS Code-based IDE that supports the Deephaven extension (VS Code, Cursor, Windsurf, etc.).
115
+
116
+
**Other IDEs:**
117
+
118
+
Configuration format varies by IDE but should be similar to the examples above. Consult your IDE's MCP documentation for the specific configuration file location and format.
119
+
120
+
> **Note:** After configuration changes, you may need to restart agent sessions or clear MCP tool caches.
104
121
105
122
## Available Tools
106
123
107
124
The MCP server provides tools for:
108
125
109
126
-**Server Management** - Connect to and list configured Deephaven servers.
110
-
111
127
-`connectToServer` - Create a connection to a server.
112
128
-`listServers` - List all configured servers.
113
129
114
130
-**Connection Management** - Query active connections.
115
-
116
131
-`listConnections` - List active connections, optionally filtered by URL.
117
132
118
133
-**Code Execution** - Run Python and Groovy code.
119
-
120
134
-`runCode` - Execute arbitrary code text.
121
135
-`runCodeFromUri` - Execute code from workspace files.
122
136
123
137
-**Variables** - Query and interact with Deephaven variables.
124
-
125
138
-`listVariables` - List all variables on a connection.
126
139
-`openVariablePanels` - Open variable panels for specific variables.
127
140
128
141
-**Table Data & Statistics** - Fetch and analyze table data.
129
-
130
142
-`getTableData` - Fetch paginated data from a table.
131
143
-`getTableStats` - Get schema information and basic statistics.
132
144
-`getColumnStats` - Get statistical information for a column.
133
145
134
146
-**Remote File Sources** - Manage server file source paths.
135
-
136
147
-`addRemoteFileSources` - Add folders as remote file sources.
137
148
-`listRemoteFileSources` - List current remote file sources.
@@ -143,14 +154,13 @@ The MCP server provides tools for:
143
154
144
155
For detailed documentation on each tool including parameters, return types, and examples, see [MCP Tool Reference](mcp-tools.md).
145
156
146
-
## Chat Skills
157
+
## Agent Skills
147
158
148
-
In addition to MCP tools, the extension provides Chat Skills that can be registered with supported AI assistants (e.g., GitHub Copilot, Windsurf) to provide domain-specific knowledge and capabilities.
159
+
In addition to MCP tools, the extension provides agent skills that can be registered with supported AI assistants to provide domain-specific knowledge and capabilities. For GitHub Copilot users, the skills are automatically registered when the extension loads. Other agents require manual installation.
149
160
150
-
### Available Chat Skills
161
+
### Provided Skills
151
162
152
163
1.**Deephaven VS Code Usage** (`deephaven-vscode-using`)
153
-
154
164
- Manages Deephaven server connections and code execution through VS Code MCP tools.
155
165
- Handles connecting to DHC/DHE servers, executing Python/Groovy code.
156
166
- Provides workflows for opening variable panels and troubleshooting connection issues.
@@ -162,17 +172,23 @@ In addition to MCP tools, the extension provides Chat Skills that can be registe
162
172
- Supports both Python and Groovy.
163
173
- Does NOT require a running server or connection - purely documentation queries.
164
174
165
-
### Chat Skills Configuration
166
-
167
-
Chat Skills are automatically registered when the extension loads. They are available in supported AI assistants like GitHub Copilot and Windsurf.
175
+
### Installation Options
168
176
169
-
The Deephaven Documentation Searching skill connects to the [Deephaven Docs MCP server](https://deephaven.io/enterprise/docs/clients/mcp/#docs-server), which is automatically configured by the extension when enabled. The extension provides the auto-configuration and the chat skill to make AI assistants aware of the documentation capabilities. For more information about the Deephaven Docs MCP server itself, see the [official documentation](https://deephaven.io/enterprise/docs/clients/mcp/#docs-server).
177
+
> Note: GitHub Copilot users should have access to the skills automatically and don't need to install anything.
170
178
171
-
The documentation server can be independently enabled/disabled via the `deephaven.mcp.docsEnabled` setting:
179
+
1.**Using `npx skills` (recommended if you have Node.js installed):**
When `deephaven.mcp.enabled` is `true`, documentation queries are enabled by default. Set `deephaven.mcp.docsEnabled` to `false` to disable documentation queries while keeping the extension's MCP tools available.
186
+
1.**Manual installation:**
187
+
- Navigate to the [skills folder](https://github.com/deephaven/vscode-deephaven/tree/main/skills) in the vscode-deephaven repository.
188
+
- Download the `SKILL.md` file from each skill you want to use:
189
+
-[deephaven-vscode-using/SKILL.md](https://github.com/deephaven/vscode-deephaven/tree/main/skills/deephaven-vscode-using/SKILL.md) - For interacting with Deephaven through the VS Code extension's MCP tools
190
+
-[deephaven-docs-searching/SKILL.md](https://github.com/deephaven/vscode-deephaven/tree/main/skills/deephaven-docs-searching/SKILL.md) - For querying Deephaven documentation
191
+
- Install the skill(s) according to your AI assistant's documentation.
176
192
177
193
## Tool Response Format
178
194
@@ -207,14 +223,15 @@ All MCP tools follow a consistent response structure:
207
223
208
224
## Supported IDEs
209
225
210
-
The MCP server provided by this extension is designed specifically for VS Code and IDEs built on top of VS Code:
226
+
The MCP server is designed specifically for VS Code and IDEs built on top of VS Code. See the [IDE-Specific Configuration](#ide-specific-configuration) table above for details on which IDEs require manual configuration.
227
+
228
+
**Tested and Fully Supported:**
211
229
212
-
-**VS Code with GitHub Copilot** - Fully supported and tested.
213
-
-**Windsurf** - Fully supported and tested.
214
-
-**Other VS Code-based IDEs** (e.g., Cursor) - May work but untested; requires manual MCP server configuration.
-**Other AI assistants** (e.g., VS Code-based IDEs, AI extensions like Cline) - Automatic configuration not implemented; requires manual MCP server configuration (untested).
235
+
-Claude in VS Code-based IDEs (VS Code, Cursor, Windsurf, etc.)
236
+
-Cursor
237
+
- Other VS Code-based IDEs (untested, configuration format may vary)
0 commit comments