MCP.so
ログイン

MCP TypeScript Server Starter

@ralf-boltshauser

基本情報

カテゴリ

開発者ツール

ライセンス

MIT

トランスポート

stdio

作者

ralf-boltshauser

MCP TypeScript Server Starter について

概要はまだありません

MCP TypeScript Server Starter の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "mcp-typescript-server-starter": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://subdomain.yourdomain.com/sse"
      ]
    }
  }
}

MCP TypeScript Server Starter のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is MCP TypeScript Server Starter?

A starter project for building Model Context Protocol (MCP) servers in TypeScript. It includes a simple echo server that demonstrates tools, resources, and prompts, and supports both STDIO and SSE communication modes.

How to use MCP TypeScript Server Starter?

Clone the repository, install dependencies with pnpm install, and run pnpm dev to start the development server with an inspector at http://localhost:6274. To switch between STDIO and SSE modes, comment/uncomment the corresponding code blocks in src/index.ts. Deploy with Docker or Coolify, and connect via npx -y mcp-remote https://your-domain.com/sse.

Key features of MCP TypeScript Server Starter

  • Simple echo server with tool, resource, and prompt implementations
  • Supports STDIO (local) and SSE (remote) communication
  • Built-in web inspector for testing and debugging
  • Hot-reloading development server
  • TypeScript type safety and modern tooling
  • Easy deployment to Coolify and other platforms

Use cases of MCP TypeScript Server Starter

  • Quickly prototype and test an MCP server locally
  • Integrate an echo server with Cursor or Claude Desktop
  • Deploy a production‑ready MCP server via SSE for remote access
  • Use as a reference for building custom tools, resources, or prompts
  • Experiment with MCP debugging and environment variable handling

よくある質問

1

What is the difference between STDIO and SSE modes?

STDIO mode uses direct process communication and is ideal for local development with tools like Cursor or Claude Desktop. SSE mode uses HTTP/SSE and is better for production deployments and remote access.

2

What are the prerequisites?

Node.js v16 or later and pnpm (or npm) are required.

3

How do I test the server locally?

Run `pnpm dev`, open the inspector at `http://localhost:6274`, click “Connect”, go to “Tools”, “List Tools”, select “echo”, write a message, and submit.

4

How do I deploy to Coolify?

Disable GZIP compression, ensure port 3001 is exposed, and set the domain with `:3001` suffix (e.g. `https://subdomain.yourdomain.com:3001`). Then connect clients with `npx -y mcp-remote https://subdomain.yourdomain.com/sse`.

5

How do I add custom tools, resources, or prompts?

Edit `src/index.ts` — the file contains commented examples for adding tools (functions your AI can call), resources (data your AI can access), and prompts (templates for AI interactions).

コメント

「開発者ツール」の他のコンテンツ