de en es ja ko ru zh

Simple TypeScript MCP Server

Name: Simple TypeScript MCP Server
Author: jasonkneen

by jasonkneen

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Einfacher TypeScript MCP-Server

Eine einfache TypeScript-Vorlage zum Erstellen von Model Context Protocol (MCP)-Servern mit grundlegenden CRUD-Operationen. Diese Vorlage bietet die Grundlage für die Erstellung von MCP-Tools, die JSON-Antworten zurückgeben.

Merkmale

Einfache Notizen-API mit CRUD-Operationen
In-Memory-Datenspeicherung
TypeScript-Implementierung
JSON-Antworten
Bereit zum Testen mit Vitest

Related MCP server: MCP Server Starter

Aufstellen

npm install

Ausführen des Servers

npm run dev

Bauen für die Produktion

npm run build
npm start

Verfügbare Tools

Diese Vorlage enthält die folgenden MCP-Tools:

getNote : Ruft eine Notiz nach ID ab
getAllNotes : Alle Notizen abrufen
createNote : Erstelle eine neue Notiz
updateNote : Aktualisieren Sie eine vorhandene Notiz
deleteNote : Löscht eine Notiz anhand der ID

Testen

Führen Sie die Tests mit folgendem aus:

npm test

Oder im Beobachtungsmodus:

npm run test:watch

Customizing

Sie können diese Vorlage als Ausgangspunkt für Ihren eigenen MCP-Server verwenden, indem Sie die Tools in src/server.ts an Ihre Anforderungen anpassen.

Available Tools

5 tools

createNoteD

ParametersJSON Schema

Name	Required	Description	Default
`title`	Yes	The title of the note
`content`	Yes	The content of the note

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.

deleteNoteD

ParametersJSON Schema

Name	Required	Description	Default
`noteId`	Yes	The ID of the note to delete

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.

getAllNotesD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

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.

getNoteD

ParametersJSON Schema

Name	Required	Description	Default
`noteId`	Yes	The ID of the note to retrieve

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.

updateNoteD

ParametersJSON Schema

Name	Required	Description
`noteId`	Yes	The ID of the note to update
`title`	No	The updated title of the note
`content`	No	The updated content of the note

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.

1 tool updatev1.0.0Jan 3, 2026
- ChangedgetAllNotes1 field changed
  - removedInput schema / additionalProperties
```
Removed value: -false
```
5 tool updatesAug 15, 2025
- First observedcreateNote
- First observeddeleteNote
- First observedgetAllNotes
- First observedgetNote
- First observedupdateNote

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.2/5.0

Scored 2026-04-18 10:05 across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: createNote, deleteNote, getAllNotes, getNote, and updateNote cover different CRUD operations on notes. The action (create, delete, get, update) and scope (all vs. single) make them easily distinguishable.

Naming Consistency5/5

All tools follow a consistent verbNoun pattern in camelCase (e.g., createNote, deleteNote). The naming is uniform across all five tools, with no deviations in style or convention.

Tool Count5/5

With 5 tools, this server is well-scoped for managing notes, covering essential CRUD operations. Each tool serves a clear purpose without redundancy, making the count appropriate for the domain.

Completeness5/5

The tool set provides complete CRUD coverage for notes: create, read (get and getAll), update, and delete. There are no obvious gaps, as all lifecycle operations are included, allowing agents to handle full workflows without dead ends.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

devbrother2024-typescript-mcp-server-boilerplateOAuth
ai.smithery
Kickstart development with a customizable TypeScript template featuring sample tools for greeting,…
Developer Tools Code Execution Coding Agents
22
cortexpad A
com.cortexpad
Google Keep-style notes app with an MCP server for AI agents to read/write notes.
Note Taking Knowledge & Memory
162
smithery-ai-cookbook-ts-smithery-cli
ai.smithery
A simple Typescript MCP server built using the official MCP Typescript SDK and smithery/cli. This…
Developer Tools
213
hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
238

Related MCP Servers

MCP Server
Note Taking Text Summarization Content Management Systems
seonglae
A
license
Not graded
quality
D
maintenance
This TypeScript-based MCP server allows users to manage a simple notes system through creating and summarizing text notes using Model Context Protocol (MCP).
Updated 8 months ago (2026-02-04 18:50 UTC)
1,026 npm
8
MIT
MCP Server Starter
Developer Tools Code Execution Autonomous Agents
StevenStavrakis
A
license
C
quality
D
maintenance
A production-ready template for creating Model Context Protocol servers with TypeScript, providing tools for efficient testing, development, and deployment.
Updated 2 years ago (2025-01-19 15:14 UTC)
1
33 npm
47
MIT
Notes MCP Server
Note Taking Text Summarization
HeatherFlux
F
license
Not graded
quality
D
maintenance
A TypeScript-based MCP server that enables users to manage text notes with features like note creation and summary generation using a Model Context Protocol.
Updated 2 years ago (2025-01-31 04:00 UTC)
1
-
Drupal-Modules-MCP MCP Server
Note Taking Text Summarization Developer Tools
Cleversoft-IT
A
license
B
quality
D
maintenance
This TypeScript-based MCP server allows users to manage and interact with a note system through Model Context Protocol, enabling note creation and summarization with URIs and metadata.
Updated 2 years ago (2025-02-07 18:51 UTC)
1
MIT