Skip to main content
Glama
CoutinhoTTS

MCP Server Starter

by CoutinhoTTS
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

MCP Server Starter

mcp starter

Want to build your own MCP server?

MCP Server Starter gives you a basic structure to run local tools with Cursor, Claude, and others using the MCP standard.

Features

  • 📡 Flexible Communication

    • Supports multiple communication protocols between client and server,

    • stdio: Local usage

    • Streamable HTTP: Remote and local useage

    • sse: Remote and local usage (deprecated)~~

  • 📦 Minimal Setup - Get started quickly with a basic server implementation.

  • 🤖 Cursor AI Integration - Includes example .cursor/mcp.json configuration.

  • ⌨️ TypeScript - Add type safety to your project.

Related MCP server: MCP Starter

Todo

  • Add option to publish your own packages

  • Better CLI support for scaffolding

  • Prompts to build tools on the fly

Getting Started

Prerequisites

  • Node.js (Specify version if necessary)

  • An MCP-compatible client (e.g., Cursor)

Usage

Supported Transport Options

Model Context Protocol Supports multiple Transport methods.

stdio

mcp starter

Recommend for local setups

Code Editor Support

Add the code snippets below

  • Cursor: .cursor/mcp.json

Local development/testing

Use this if you want to test your mcp server locally

{
  "mcpServers": {
    "my-starter-mcp-stdio": {
      "command": "node",
      "args": ["./bin/cli.mjs", "--stdio"]
    }
  }
}

Published Package

Use this when you have published your package in the npm registry

{
  "mcpServers": {
    "my-starter-mcp-stdio": {
      "command": "npx",
      "args": ["my-mcp-server", "--stdio"]
    }
  }
}

Streamable HTTP

mcp starter

Important: Streamable HTTP is not supported in Cursor yet

Recommend for remote server usage

Important: In contrast to stdio you need also to run the server with the correct flag

Local development Use the streamable http transport

  1. Start the MCP Server Run this in your terminal

node ./bin/cli.mjs --http --port 4200

Or with mcp inspector

npm run dev-http
# npm run dev-sse (deprecated)

  1. Add this to your config

{
  "mcpServers": {
    "my-starter-mcp-http": {
      "command": "node",
      "args": ["./bin/cli.mjs", "--http", "--port", "4001"]
      // "args": ["./bin/cli.mjs", "--sse", "--port", "4002"] (or deprecated sse usage)
    }
  }
}

Published Package

Use this when you have published your package in the npm registry

Run this in your terminal

npx my-mcp-server --http --port 4200
# npx my-mcp-server --sse --port 4201 (deprecated)
{
  "mcpServers": {
    "my-starter-mcp-http": {
      "url": "http://localhost:4200/mcp"
      // "url": "http://localhost:4201/sse"
    }
  }
}

Use the Inspector

Use the inspect command to debug your mcp server

mcp starter mcp starter

Command-Line Options

Protocol Selection

Protocol

Description

Flags

Notes

stdio

Standard I/O

(None)

Default

http

HTTP REST

--port <num> (def: 3000), --endpoint <path> (def: /mcp)

sse

Server-Sent Events

--port <num> (def: 3000)

Deprecated

License

This project is licensed under the MIT License - see the LICENSE file for details.

Courses

Available Tools

1 tool
Generation moduleC
 遍历工具返回的数组，将数组中每一项有 writeOptions: object、dir: string,两个属性。
 需要将对象writeOptions的属性进行遍历，找到dir文件中对应的变量名。 匹配规则：变量名和writeOptions的属性名称相等。
 匹配到了之后将dir中的变量值自动重写，使用writeOptions属性值覆盖，一定是自动重写。
 For example: 
 writeOptions示例
 ``` javascript
   writeOptions:{subnaem:'用户管理'}
 ```

 dir文件代码示例：
 ``` javascript
   const subnaem = '';
 ```

 经过规则匹配之后，dir文件重写后应该是：
 ``` javascript
   const subnaem = '用户管理';
 ```
ParametersJSON Schema
NameRequiredDescriptionDefault
addressYes描述文件地址

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It describes the rewriting behavior and matching rules, but lacks critical details: it doesn't specify if this is a read-only or destructive operation, what permissions are needed, how errors are handled, or the output format. The description mentions '自动重写' (automatic rewrite), implying mutation, but without annotations, more behavioral context is needed.

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

Conciseness3/5

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

The description is moderately concise but poorly structured. It mixes technical details with an example, making it somewhat front-loaded but cluttered. Sentences like '需要将对象writeOptions的属性进行遍历' are necessary but could be clearer. The example adds value but the overall flow could be more streamlined for better readability.

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

Completeness2/5

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

Given the complexity (involving array traversal, property matching, and file rewriting), no annotations, and no output schema, the description is incomplete. It explains the matching and rewriting process but omits error handling, side effects, and return values. For a tool with potential destructive behavior and no structured safety hints, more comprehensive context is needed.

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

Parameters3/5

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

The schema description coverage is 100%, with the parameter 'address' clearly documented as '描述文件地址' (describing file address). The description adds no additional meaning about parameters beyond what the schema provides, focusing instead on internal processing. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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

Purpose2/5

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

The description states the tool processes arrays with specific properties to rewrite variable values in files, but it's vague about the core purpose. It describes implementation details ('遍历工具返回的数组', '匹配规则') rather than clearly stating what the tool does at a high level. The purpose is implied but not explicitly defined, making it somewhat tautological with the name 'Generation module'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description focuses on how it works internally, with no mention of prerequisites, typical use cases, or contextual triggers. Since there are no sibling tools, this is less critical, but the absence of any usage context leaves the agent without direction.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.4/5.0
Disambiguation5/5

With only one tool named 'Generation module', there is no possibility of confusion or overlap with other tools. The tool's purpose is clearly defined as a specific file rewriting operation based on matching rules, making it entirely distinct by default.

Naming Consistency3/5

The tool name 'Generation module' uses a noun-based naming style, which is readable but lacks a consistent verb_noun pattern that is typical for action-oriented tools. Since there is only one tool, consistency cannot be assessed across multiple tools, but the naming is clear though not following common conventions.

Tool Count2/5

A single tool for a server named 'MCP Server Starter' feels thin and under-scoped, as it suggests a limited or incomplete surface. Typically, such a server might be expected to offer more foundational or varied tools for starting or managing MCP servers, making one tool insufficient for the implied purpose.

Completeness1/5

The tool set is severely incomplete for the server's purpose. With only one tool focused on a niche file rewriting task, there are significant gaps in coverage for common MCP server operations like configuration, deployment, or management, leading to likely agent failures in broader tasks.

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

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/CoutinhoTTS/funi-mcp'

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