Skip to main content
Glama
a-polishchuk

Yes or No MCP

by a-polishchuk
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

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

Related MCP server: TypeScript MCP Server

Prerequisites

  • Node.js (v18 or newer recommended)

  • npm

Setup

  1. Install dependencies:

    npm install

  2. Go to Cursor Settings -> MCP -> Add new MCP:

    {
    "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

Available Tools

1 tool
getYesOrNoD
ParametersJSON Schema
NameRequiredDescriptionDefault
questionYes

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool update
    • First observedgetYesOrNo
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.8/5.0
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 issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • MCP Montano Server

    lucasmontano
    F
    license
    Not graded
    quality
    D
    maintenance
    A TypeScript-based server project that can be integrated with Cursor IDE as an MCP (Model Control Protocol) server, enabling enhanced development capabilities.
    134
    -

  • TypeScript MCP Server

    KyleAnthonyMcAdam
    -
    license
    B
    quality
    Not graded
    maintenance
    A simple Model Context Protocol server implemented in TypeScript that enables communication with client applications (like Cursor) over standard input/output and includes a basic calculator tool as an example.
    4
    1
    -

  • MCP Server TypeScript Template

    HarshitRatan
    F
    license
    Not graded
    quality
    D
    maintenance
    A demonstration MCP server built in TypeScript that shows how to implement stdio-based communication for integration with MCP clients. Serves as a template for building custom MCP servers with strong typing and maintainability.
    -

  • Basic MCP Server

    Merlin21x
    F
    license
    B
    quality
    D
    maintenance
    A basic TypeScript implementation of the Model Context Protocol (MCP) server designed as a starting point for MCP development. Provides a minimal foundation for building custom MCP servers with stdio configuration for local integration with VS Code and GitHub Copilot.
    1
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/a-polishchuk/mcp-example-stdio'

If you have feedback or need assistance with the MCP directory API, please join our Discord server