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
Enhance MCP server context management and documentation
- Added support for pre-configured context in MCP server commands, allowing users to specify `--pulsar-instance` and `--pulsar-cluster` flags.
- Updated `RegisterContextTools` function to conditionally skip context tool registration based on provided CLI flags, improving usability.
- Enhanced README.md with new command examples and notes regarding context management behavior when using specific flags.
- Added comments in the code for better clarity on the context management logic.
@@ -235,6 +243,8 @@ The StreamNative MCP Server allows you to enable or disable specific groups of f
235
243
|`streamnative-cloud`| Manage StreamNative Cloud context and check resource logs |[streamnative_cloud.md](docs/tools/streamnative_cloud.md)|
236
244
|`functions-as-tools`| Dynamically exposes deployed Pulsar Functions as invokable MCP tools, with automatic input/output schema handling. |[functions_as_tools.md](docs/tools/functions_as_tools.md)|
237
245
246
+
> **Note:** When using `--pulsar-instance` and `--pulsar-cluster` flags together, context management tools (`sncloud_context_use_cluster`) are automatically disabled since the context is pre-configured.
247
+
238
248
You can combine these features as needed using the `--features` flag. For example, to enable only Pulsar client features:
0 commit comments