Skip to main content
Glama
saurabh-sde3

common_mcp

by saurabh-sde3
README.md
# common_mcp

Simple MCP service that exposes one tool: `get_basic_details`.

## What it does

- Runs as an MCP server over stdio
- Provides a single tool: `get_basic_details`
- Returns platform, Node version, architecture, current time, and uptime
- Optionally returns hostname if `includeHostname: true`

## Setup

```bash
npm install
```

## Run

```bash
npm start
```

## MCP client config

Use `node` directly so the client can launch the stdio server.

### Cursor

Add this under MCP settings (or your MCP config file):

```json
{
  "mcpServers": {
    "common_mcp": {
      "command": "node",
      "args": [
        "/Users/saurabhverma/Desktop/vibecoding/projects/common_mcp/server.js"
      ]
    }
  }
}
```

### Claude Desktop

Put this in `~/Library/Application Support/Claude/claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "common_mcp": {
      "command": "node",
      "args": [
        "/Users/saurabhverma/Desktop/vibecoding/projects/common_mcp/server.js"
      ]
    }
  }
}
```

## Example MCP tool call

Tool name: `get_basic_details`

Input:

```json
{
  "includeHostname": true
}
```

## Signature

Saurabh Kumar

TDQS

C2.8/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap. The single tool has a clear and distinct purpose.

Naming Consistency5/5

There is only one tool, so naming consistency is not an issue. The name 'get_basic_details' follows a clear verb_noun pattern.

Tool Count3/5

Having only one tool feels thin for a server labeled 'common_mcp'. While a single tool can be appropriate for very narrow scopes, this server's name suggests a broader utility, making the count borderline.

Completeness2/5

The server only provides basic system and runtime details. For a 'common' server, one would expect additional tools for other common operations, leaving significant gaps.

Maintenance

ActivityInactive
ResponsivenessUnresponsive