Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Shellagent MCP Serverlist all running processes on my system"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
shellagent-mcp MCP Server
A Model Context Protocol (MCP) server for shellagent-mcp
Requirements
Node.js 18 or newer
VS Code, Cursor, Windsurf, Claude Desktop or any other MCP client
Getting started
Local (Stdio)
First, install the Commands MCP server with your client. A typical configuration looks like this:
You can also install the shellagent-mcp MCP server using the VS Code CLI:
After installation, the Commands MCP server will be available for use with your GitHub Copilot agent in VS Code.
Go to Cursor Settings -> MCP -> Add new MCP Server. Name to your liking, npx mcp-server-shellagent-mcp. You can also verify config or add command like arguments via clicking Edit.
Follow Windsuff MCP documentation. Use following configuration:
Follow the MCP install guide, use following configuration:
Remote (SSE / Streamable HTTP)
At the same time, use --port $your_port arg to start the browser mcp can be converted into SSE and Streamable HTTP Server.
You can use one of the two MCP Server remote endpoint:
Streamable HTTP(Recommended):
http://127.0.0.1::8089/mcpSSE:
http://127.0.0.1::8089/sse
And then in MCP client config, set the url to the SSE endpoint:
url to the Streamable HTTP:
In-memory call
If your MCP Client is developed based on JavaScript / TypeScript, you can directly use in-process calls to avoid requiring your users to install the command-line interface to use Commands MCP.
Developement
Access http://127.0.0.1:6274/: