MCP ExplorerExplorer

Nah

@linmx0130on 10 months ago
3 MIT
FreeCommunity
AI Systems
A user agent for exploring Model Context Protocol.

Overview

What is Nah

nah is a user agent designed for exploring the Model Context Protocol (MCP). It allows users to interact with various MCP servers through a shell-like interface.

Use cases

Use cases for nah include testing and debugging MCP servers, exploring model capabilities, and automating interactions with various tools and resources provided by MCP servers.

How to use

To use nah, launch it with a MCP config file using the command nah ~/mcp/config.json. After starting, you can select an MCP server, list available tools, and perform actions using commands like use, list_tools, and call_tool.

Key features

Key features of nah include support for MCP config files, a shell-like user interface, command history storage, and customizable text editor for tool call arguments.

Where to use

nah can be used in software development environments, particularly for applications that require interaction with multiple MCP servers for data processing or model exploration.

Content

nah: Not A Human

A user agent for exploring Model Context Protocol.

WARNING: Still in active development, use at your own risk!

Quick intro

nah supports a MCP config file in the Claude desktop app config format.

$ nah ~/mcp/config.json

After launching nah, it will active all MCP servers declared in the config file and provide a shell-like user interface. Here are some useful commands supported by nah.

  • use: Select a MCP server to interactive with.
  • list_tools: List all tools on the current server.
  • call_tool: Call a tool on the current server.
  • list_resources: List all resources on the current server.
  • get_resources: Read resources through a URI.

The help command will print out the list of available commands.

All commuications (JSON-RPC messages) will be stored in a directory in the current working directory. A .jsonl file will be create for each server. Use --history-path argument to set the path to store all these records:

$ nah ~/mcp/config.json --history-path trial_1_history
# History will be stored as trial_1_history/[server name].jsonl

Configuration

By deault, users are asked to provide arguments for tool calls through editing a file in vi. Environment variable $EDITOR controls the editor to use:

$ EDITOR=nano nah ~/mcp/config.json
# nano will be used as the editor

Copyright

Copyright © 2025 Mengxiao Lin. Released under MIT License. Check LICENSE file for more details.

Tools

No tools

Comments

Recommend MCP Servers

View All MCP Servers