mcp -bash-sdk

This MCP server is implemented in Bash and communicates using the MCP protocol over standard input and output. It exposes business logic as tool functions that are discovered automatically based on the tool naming convention (tool_<name>). You can interact with the server by piping a JSON-RPC request to the server script (for example, ./moviemcpserver.sh) and reading the JSON-RPC response back on stdout. A sample request demonstrates calling a tool by name (e.g., get_movies) via the tools namespace: {"jsonrpc": "2.0", "method": "tools/call", "params": {"name": "get_movies"}, "id": 1}. The server will route this to the corresponding tool_<name> function defined in the business logic (e.g., tool_get_movies) and return the result. You can customize or extend the server by adding new tool_ functions and updating assets as needed. For VS Code or Copilot integration, configure the stdio server to point to moviemcpserver.sh and set any necessary environment variables (for example, API keys) in the env block.

Prerequisites:

• Bash shell
• jq (for JSON processing)

Installation steps:

1. Clone the repository: git clone https://github.com/muthuishere/mcp-server-bash-sdk cd mcp-server-bash-sdk

2. Ensure executable permissions on the server script and related files: chmod +x mcpserver_core.sh moviemcpserver.sh

3. Install dependencies:

   • Install jq (e.g., on macOS: brew install jq; on Debian/Ubuntu: sudo apt-get install jq)

4. Run the server (example): ./moviemcpserver.sh // Alternatively, run via the MCP config: // Use the mcp_config entry with command: bash and args: ["./moviemcpserver.sh"]

5. Test with a sample request: echo '{"jsonrpc": "2.0", "method": "tools/call", "params": {"name": "get_movies"}, "id": 1}' | ./moviemcpserver.sh

Tips and notes:

• The server discovers tools automatically from functions named tool_<name>, so to add a new capability implement a new function tool_<name> that accepts a single JSON argument in $1 and returns 0 on success and 1 on error.
• Tool metadata and external configuration can be stored under assets/ (e.g., assets/yourserver_tools.json and assets/yourserver_config.json) to enable dynamic behavior.
• Ensure jq is available in your environment since the Bash implementation relies on it for JSON parsing.
• If you modify tool implementations, make sure to make the script executable and reload/restart the MCP server as needed.
• This Bash-based MCP server emphasizes lightweight operation and zero-overhead protocol handling, but it may not scale for high-throughput scenarios.