Skip to main content
Glama
dongri

LGTM MCP Server

by dongri
README.md
[![MseeP.ai Security Assessment Badge](https://mseep.net/pr/dongri-mcp-server-lgtm-badge.png)](https://mseep.ai/app/dongri-mcp-server-lgtm)

# mcp-server-lgtm MCP Server

[![smithery badge](https://smithery.ai/badge/@dongri/mcp-server-lgtm)](https://smithery.ai/server/@dongri/mcp-server-lgtm)

A Model Context Protocol server for LGTM images

This is a TypeScript-based MCP server that interacts with the LGTM API. It provides a tool to fetch random LGTM (Looks Good To Me) images that can be used in code reviews and other developer communications.

## Features

### Create server
```
npx @modelcontextprotocol/create-server mcp-server-lgtm
```

### Tools
- `get_lgtm` - Fetch a random LGTM image
  - Returns markdown code for embedding the image
  - Provides the direct image URL for use in various contexts

## Development

Install dependencies:
```bash
npm install
```

Build the server:
```bash
npm run build
```

For development with auto-rebuild:
```bash
npm run watch
```

## Dev Installation

To use with Claude Desktop, add the server config:

On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`

```json
{
  "mcpServers": {
    "mcp-server-lgtm": {
      "command": "/path/to/mcp-server-lgtm/build/index.js"
    }
  }
}
```

### Installing via Smithery

To install mcp-server-lgtm MCP Server for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@dongri/mcp-server-lgtm):

```bash
npx -y @smithery/cli install @dongri/mcp-server-lgtm --client claude
```

### Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:

```bash
npm run inspector
```

The Inspector will provide a URL to access debugging tools in your browser.

## Smithery

https://smithery.ai/server/@dongri/mcp-server-lgtm

TDQS

B3.3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_lgtm' has a clearly defined and distinct purpose, so an agent cannot misselect between non-existent alternatives.

Naming Consistency5/5

The naming follows a consistent verb_noun pattern with 'get_lgtm', and since there is only one tool, there is no inconsistency to evaluate. The naming is clear and predictable for the single tool present.

Tool Count2/5

A single tool is too few for most server purposes, as it limits functionality and suggests a very narrow scope. While it might be appropriate for a trivial utility, it feels thin and underdeveloped for a server named 'LGTM MCP Server', which implies more comprehensive LGTM-related operations.

Completeness2/5

The server is severely incomplete for handling LGTM operations. With only a 'get_lgtm' tool, there are obvious gaps such as creating, updating, deleting, or listing LGTMs, and no coverage of related workflows. This will likely cause agent failures when more complex tasks are required.

Maintenance

ActivityInactive
ResponsivenessNo issues