Skip to content

feat: add HTTP/SSE transport support and document usage in Quick Start #257

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Rujaxx
Copy link

@Rujaxx Rujaxx commented May 16, 2025

This pull request introduces support for running the MongoDB MCP server with HTTP or SSE transport using the new --transportType and --port command-line arguments. The default port is 5700 if not specified. The Quick Start section in the README has been updated to include Option 5, providing clear instructions and example commands for exposing the server over HTTP or SSE for network-based client integration.

  • Adds support for --transportType (http or sse) and --port arguments in the server startup.
  • Updates the Quick Start documentation in the README to include usage examples for HTTP/SSE transport.
  • Clarifies that all other configuration options (like --connectionString, --apiClientId, etc.) are supported with these transport types.
  • Helps users easily expose the MCP server for integration with clients that require a network endpoint.

Rujaxx added 2 commits May 16, 2025 12:31
…upport

Add support and documentation for running the MCP server with HTTP or SSE transport using --transportType and --port arguments
Provide example commands and clarify default port usage for custom network endpoints
…ions

Document usage of --transportType and --port for running the server with HTTP or SSE endpoints
Add example commands and clarify default port behavior
Help users expose the MCP server for network-based client integration
@Rujaxx Rujaxx requested a review from a team as a code owner May 16, 2025 07:19
Copy link
Collaborator

@nirinchev nirinchev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this contribution. Unfortunately, we can't accept it in its current form, because the server is stateful (we already have a session that tracks connection status) and as such, doesn't lend itself to multiple clients connecting to it - e.g., you could end up executing crud updates against the wrong connection.

We do have plans to rework the design and enable stateless operation, but that's lower priority than some of the features we're working on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants