Skip to main content
Glama
kukapay

whoami-mcp

by kukapay
README.md
[![MseeP Badge](https://mseep.net/pr/kukapay-whoami-mcp-badge.jpg)](https://mseep.ai/app/kukapay-whoami-mcp)

# WhoAmI MCP Server

[![smithery badge](https://smithery.ai/badge/@kukapay/whoami-mcp)](https://smithery.ai/server/@kukapay/whoami-mcp)
A lightweight MCP server that tells you exactly who you are.

<a href="https://glama.ai/mcp/servers/@kukapay/whoami-mcp">
  <img width="380" height="200" src="https://glama.ai/mcp/servers/@kukapay/whoami-mcp/badge" alt="whoami-mcp MCP server" />
</a>

![GitHub License](https://img.shields.io/github/license/kukapay/whoami-mcp) 
![GitHub Last Commit](https://img.shields.io/github/last-commit/kukapay/whoami-mcp) 
![Python Version](https://img.shields.io/badge/python-3.10%2B-blue)


## Features
- Returns the system username as your name, your identity.
- Fast and synchronous execution, ideal for local LLM integration.

## Installation

### Installing via Smithery

To install WhoAmI for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@kukapay/whoami-mcp):

```bash
npx -y @smithery/cli install @kukapay/whoami-mcp --client claude
```

1. **Clone the Repository**
    ```bash
    git clone https://github.com/kukapay/whoami-mcp.git
    ```

2. **Client Configuration**

    ```json
    {
      "mcpServers": {
        "whoami": {
          "command": "uv",
          "args": ["--directory", "path/to/whoami_mcp", "run", "main.py"]
        }
      }
    }
    ````

## Usage

### MCP Tool
- **Name**: `whoami`
- **Description**: Retrieves the username of the current system user as your name.
- **Output**: your name.

## License
This project is licensed under the MIT License. See the [LICENSE](LICENSE) file for details.

TDQS

A3.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools, making disambiguation perfect. The tool 'whoami' has a single, clear purpose that cannot be mistaken for any other function.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect as there are no other tools to compare against. The tool name 'whoami' is clear and follows a common Unix command pattern, which is appropriate for its purpose.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and can feel thin or incomplete. While it might be appropriate for a minimal utility, it lacks the breadth typically expected in an MCP server, which often requires multiple tools for varied operations.

Completeness3/5

The tool 'whoami' covers its specific function of returning the current system user's identity, but with only one tool, the server's scope is very narrow. There are no obvious gaps for this limited purpose, but it lacks broader coverage that might be expected in a user management or system information domain.

Maintenance

ActivityInactive
ResponsivenessNo issues