Choose the server-everything transport on the command line

[cliffhall]

Description

Update server-everything to allow choosing the transport on the command line.

• In src/everything/index.ts

  • refactor/extracted contents to stdio.ts
  • replaced with code that
    • Gets the single argument from the commandline as scriptName
    • switches on scriptName
    • imports the appropriate server script or outputs usage options
  • scripts run on import

• In src/everything/stdio.ts

  • added console log "Starting default (STDIO) server..."

• In src/everything/sse.ts

  • added console log "Starting SSE server..."

• In src/everything/streamableHttp.ts

  • added console log "Starting Streamable HTTP server..."

• In README.md

  • add details for launching

Server Details

• Server: everything
• Changes to: startup process

Motivation and Context

To allow specifying the transport to start the server with on the command line.

• This fixes Add option to enable either stdio or SSE transports when running server-everything using npx #1594

Valid commands

Run the default (stdio) server

npx @modelcontextprotocol/server-everything

Or specify stdio explicitly

npx @modelcontextprotocol/server-everything stdio

Run the SSE server

npx @modelcontextprotocol/server-everything sse

Run the streamable HTTP server

npx @modelcontextprotocol/server-everything streamableHttp

How Has This Been Tested?

1. Run the startup script that npx will invoke with the args

2. Run npm link in src/everything and then test with npx

Breaking Changes

Nope.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Additional context

[olaservo]

Looks good, I was also able to publish this branch to a personal version of the package in npm and run all variations on my Windows machine:

PS C:\Users[redacted]> npx @olaservo/server-everything
Starting default (STDIO) server...
{"method":"notifications/message","params":{"level":"emergency","data":"Emergency-level message"},"jsonrpc":"2.0"}
PS C:\Users[redacted]> npx @olaservo/server-everything sse
Starting SSE server...
Server is running on port 3001
PS C:\Users[redacted]> npx @olaservo/server-everything streamableHttp
Starting Streamable HTTP server...
MCP Streamable HTTP Server listening on port 3001
Shutting down server...
Server shutdown complete
PS C:\Users[redacted]> npx @olaservo/server-everything stdio
Starting default (STDIO) server...

[olaservo]

Thanks for adding this, left a comment on a logging issue but works for me on the terminal so far.

[olaservo]

Thanks, Claude Desktop over STDIO is happy now:

I'm not able to test SSE in the same app so I'm not certain how console.error is actually being interpreted for that transport, but if it creates noise we can always change it.