Skip to main content
Glama
deenesjakoruzh
instructa

MCP Starter

by instructa
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

Стартовый сервер MCP

mcp стартер

Хотите создать свой собственный MCP-сервер?

MCP Server Starter предоставляет вам базовую структуру для запуска локальных инструментов с Cursor, Claude и другими, использующими стандарт MCP.

Функции

  • 📡 Гибкая коммуникация

    • Поддерживает несколько протоколов связи между клиентом и сервером,

    • stdio : Локальное использование

    • Streamable HTTP : удаленное и локальное использование

    • sse : Удаленное и локальное использование (устарело)~~

  • 📦 Минимальная настройка — начните работу быстро с базовой реализации сервера.

  • 🤖 Интеграция Cursor AI — включает пример конфигурации .cursor/mcp.json .

  • ⌨️ TypeScript — добавьте безопасность типов в свой проект.

Related MCP server: MCP Server Starter

Тодо

  • [ ] Добавить возможность публиковать собственные пакеты

  • [ ] Лучшая поддержка CLI для скаффолдинга

  • [ ] Предлагает создавать инструменты «на лету»

Начиная

Предпосылки

  • Node.js (укажите версию при необходимости)

  • MCP-совместимый клиент (например, Cursor )

Использование

Поддерживаемые варианты транспорта

Модель контекстного протокола Поддерживает несколько методов транспортировки.

стдио

mcp стартер

Рекомендуется для локальных установок

Поддержка редактора кода

Добавьте фрагменты кода ниже

  • Курсор: .cursor/mcp.json

Локальная разработка/тестирование

Используйте это, если вы хотите протестировать свой mcp-сервер локально.

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

Опубликованный пакет

Используйте это, когда вы опубликовали свой пакет в реестре npm.

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

Потоковое HTTP

mcp стартер

Важно: потоковый HTTP пока не поддерживается в Cursor

Рекомендовано для использования на удаленном сервере

Важно: в отличие от stdio вам также необходимо запустить сервер с правильным флагом.

Локальная разработка Используйте streamable http -транспорт

  1. Запустите MCP Server. Запустите это в своем терминале.

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

Или с инспектором mcp

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

  1. Добавьте это в свою конфигурацию

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

Опубликованный пакет

Используйте это, когда вы опубликовали свой пакет в реестре npm.

Запустите это в своем терминале

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

Используйте инспектор

Используйте команду inspect для отладки вашего сервера mcp

mcp стартерmcp стартер

Параметры командной строки

Выбор протокола

Протокол

Описание

Флаги

Примечания

stdio

Стандартный ввод/вывод

(Никто)

По умолчанию

http

HTTP-REST-ПРОЦЕССОР

--port <num> (по умолчанию: 3000), --endpoint <path> (по умолчанию: /mcp )

sse

События, отправленные сервером

--port <num> (по умолчанию: 3000)

Устаревший

Лицензия

Данный проект лицензирован по лицензии MIT — подробности см. в файле LICENSE.

Курсы

  • Научитесь создавать программное обеспечение с помощью ИИ: instructa.ai

Available Tools

1 tool
doSomethingD

What is the capital of Austria?

ParametersJSON Schema
NameRequiredDescriptionDefault
param1YesThe name of the track to search for
param2YesThe name of the track to search for

TDQS

D1.4/5.0
Behavior1/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 of behavioral disclosure. The description fails to indicate what the tool does, whether it's a read/write operation, any side effects, or response format. It offers no behavioral context beyond the confusing question, leaving the agent with no understanding of the tool's behavior.

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

Conciseness2/5

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

The description is a single sentence, but it is not appropriately sized for the tool—it is under-specified and misleading rather than concise. It does not front-load useful information about the tool's purpose, wasting the opportunity to clarify functionality.

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?

Given the complexity (2 required parameters, no annotations, no output schema) and the description's complete failure to explain the tool's purpose or behavior, it is inadequate. The description does not compensate for the lack of annotations or output schema, leaving the agent with insufficient information to use the tool correctly.

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?

Schema description coverage is 100%, with both parameters documented as 'The name of the track to search for'. The description adds no parameter information beyond what the schema provides. According to the rules, with high schema coverage (>80%), the baseline is 3 even with no param info in the 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?

The description 'What is the capital of Austria?' is a question about geography, not a description of what the tool does. It provides no verb indicating an action (e.g., search, retrieve, calculate) and no mention of resources or operations. This is misleading as it suggests a trivia answer rather than tool functionality.

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?

No guidance is provided on when to use this tool. The description does not mention any context, prerequisites, or alternatives. Given the mismatch between the description and input schema (which references track searching), there is no usable information for an agent to determine appropriate usage scenarios.

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 updatev1.0.0
    • First observeddoSomething
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 'doSomething' stands alone with a distinct purpose, making disambiguation trivial.

Naming Consistency3/5

There is only one tool, so consistency cannot be assessed across multiple tools. The naming 'doSomething' is clear but does not follow a strong pattern, placing it in the middle range.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and scope. This feels thin and inadequate for typical MCP server applications.

Completeness1/5

The server has a single tool that answers a specific trivia question, which is severely incomplete for any meaningful domain. There are obvious gaps, as it lacks any operational coverage or lifecycle management.

Maintenance

ActivityInactive
ResponsivenessSyncing

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 Server Python Template

    Cris-0k
    -
    license
    Not graded
    quality
    Not graded
    maintenance
    A streamlined foundation for building Model Context Protocol servers in Python, designed to make AI-assisted development of MCP tools easier and more efficient.
    12
    -

  • MCP Server Scaffold

    vjouenne76
    F
    license
    B
    quality
    D
    maintenance
    A basic starter project for building Model Context Protocol (MCP) servers that enables standardized interactions between AI systems and various data sources through secure, controlled tool implementations.
    2
    -

  • MCP Template

    xcollantes
    A
    license
    B
    quality
    D
    maintenance
    A template repository for building Model Context Protocol (MCP) servers that enable LLM clients to interact with custom tools and services through standardized JSON-RPC communication.
    3
    MIT

Appeared in Searches

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/instructa/mcp-starter'

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