Nash MCP Server

local-only server

The server can only run on the client’s local machine because it depends on local resources.

Integrations

  • Nash MCP uses .env files to specify data file paths for configuration

  • Nash MCP provides command execution capabilities that can run git commands with proper error handling and output capture

  • Nash MCP enables execution of Python code snippets with full access to installed packages and provides information about available Python packages

Nash MCP Server

Nash MCP (a Model Context Protocol (MCP) server) enables seamless execution of commands, Python code, web content fetching, and reusable task management.

Requirements

  • Python 3.11+
  • Poetry package manager (recommended)

Installation

git clone https://github.com/nash-run/nash-mcp.git cd nash-mcp poetry install

Features

  • Command Execution: Run shell commands with error handling
  • Python Execution: Execute Python code with error handling
  • Secure Credentials: Store and access API keys without exposing sensitive data to the LLM
  • Web Content Access: Fetch and parse webpage content for analysis
  • Task Repository: Save and organize reusable workflows and scripts

Tools

Execute Module

  • execute_command: Run shell commands with proper error handling and output capture
  • execute_python: Execute Python code snippets with full access to installed packages
  • list_installed_packages: Get information about available Python packages

Web Interaction

  • fetch_webpage: Retrieve and convert webpage content to readable text format

Secrets Management

  • nash_secrets: Access stored API keys and credentials securely. Accessible via environment variables in scripts.

Task Management

  • save_nash_task: Create reusable tasks with embedded scripts
  • list_nash_tasks: View all available saved tasks
  • run_nash_task: Retrieve and display a previously saved task
  • execute_task_script: Run a specific script from a saved task
  • view_task_details: See complete details of a task, including script code
  • delete_nash_task: Remove tasks that are no longer needed

Running

This is the command to use for MCP config files

/path/to/this/repo/.venv/bin/mcp run /path/to/this/repo/src/nash_mcp/server.py

As an example, if you were to use this MCP with Claude Desktop, you would change your ~/Library/Application Support/Claude/claude_desktop_config.json to:

{ "mcpServers": { "Nash": { "command": "/Users/john-nash/code/nash-mcp/.venv/bin/mcp", "args": ["run", "/Users/john-nash/code/nash-mcp/src/nash_mcp/server.py"] } } }

Environment Variables

Nash MCP requires environment variables to specify all data file paths. Create a .env file in the root directory with the following variables:

# Required environment variables NASH_BASE_PATH=/path/to/base/directory NASH_SECRETS_PATH=/path/to/secrets.json NASH_TASKS_PATH=/path/to/tasks.json NASH_LOGS_PATH=/path/to/logs/directory

There are no default values - all paths must be explicitly configured.

Security Considerations

  • Commands and scripts run with the same permissions as the MCP server
  • API keys and credentials are stored locally and loaded as environment variables
  • Always review scripts before execution, especially when working with sensitive data

Development

Logs

Detailed timestamped logs of all operations and tool executions are emitted by the server. These logs are stored in the directory specified by the NASH_LOGS_PATH environment variable.

Testing

Coming Soon

License

MIT

-
security - not tested
A
license - permissive license
-
quality - not tested

A Model Context Protocol server that enables seamless execution of commands, Python code, web content fetching, and reusable task management with secure credentials handling.

  1. Requirements
    1. Installation
      1. Features
        1. Tools
          1. Execute Module
            1. Web Interaction
              1. Secrets Management
                1. Task Management
                2. Running
                  1. Environment Variables
                  2. Security Considerations
                    1. Development
                      1. Logs
                        1. Testing
                        2. License