Skip to main content
Glama
Yes or No MCP

Yes or No MCP

by a-polishchuk
README.md
# MCP Example: Server over stdio

This repository demonstrates a simple MCP (Model Context Protocol) server implementation that communicates over stdio using TypeScript.

## Features
- Example MCP server using stdio
- Written in TypeScript
- Easily extensible for custom MCP commands

## Prerequisites
- Node.js (v18 or newer recommended)
- npm

## Setup
1. **Install dependencies:**
   ```sh
   npm install
   ```

2. **Go to Cursor Settings -> MCP -> Add new MCP:**
   ```json
   {
       "mcpServers": {
           "Yes or No MCP": {
               "command": "npx",
               "args": [
                   "-y",
                   "tsx",
                   "<absolute_path_to>/stdio-example.ts",
                   "--stdio"
               ]
           }
       }
   }
   ```
   Replace `<absolute_path_to>` with the absolute path to your `stdio-example.ts` file.

3. **Use MCP server:**
   Ask LLM in Cursor some question and add "yes or no" in the end, Cursor will call MCP tool.

## File Overview
- `stdio-example.ts`: Main MCP server implementation.
- `copy-this-to-mcp-json.json`: Example configuration for MCP server setup.

## License
MIT 

TDQS

D1.8/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool 'getYesOrNo' stands alone with a distinct purpose, making disambiguation trivial and perfect.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'getYesOrNo' follows a clear verb_noun pattern, and with no other tools to compare, there is no inconsistency.

Tool Count2/5

A single tool is too few for most practical server purposes, as it severely limits functionality and scope. For a server named 'Yes or No MCP', which suggests a simple decision-making or random response service, one tool might be minimal but still functional, but it feels thin and underdeveloped compared to typical MCP servers.

Completeness3/5

Inferring the domain as providing yes/no responses, the single tool 'getYesOrNo' covers the core functionality. However, there are obvious gaps: no ability to customize responses, set parameters, or handle variations, which limits agent workflows. The surface is basic but not severely incomplete for the stated purpose.

Maintenance

ActivityInactive
ResponsivenessNo recent community issues