Skip to main content
Glama
brainupgrade-in

Notes Manager

by brainupgrade-in
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

MCP Server: Notes Manager (TypeScript Starter)

A simple MCP (Model Context Protocol) server that manages notes. This is the companion repository for the Gheware DevOps AI YouTube tutorial: "Build Your Own MCP Server (TypeScript)".

What You'll Learn

  • How to create an MCP server from scratch

  • Implementing TOOLs (operations AI can perform)

  • Implementing RESOURCEs (data AI can read)

  • Testing with Claude Desktop and MCP Inspector

Related MCP server: API MCP Server

Features

Tools (AI Operations)

Tool

Description

add_note

Create a new note with title, content, and tags

list_notes

List all notes with IDs and titles

search_notes

Search notes by title, content, or tags

delete_note

Delete a note by ID

Resources (AI Data Access)

URI

Description

notes://list

JSON list of all notes

notes://note/{id}

Individual note by ID

Quick Start

Prerequisites

  • Node.js 18+

  • npm or yarn

  • Claude Desktop (for testing)

Installation

# Clone the repository
git clone https://github.com/brainupgrade-in/mcp-server-typescript-starter.git
cd mcp-server-typescript-starter

# Install dependencies
npm install

# Build the project
npm run build

Test with MCP Inspector

npm run inspector

This opens a browser-based inspector to test your tools and resources.

Configure Claude Desktop

Add this to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "notes": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-server-typescript-starter/dist/index.js"]
    }
  }
}

Restart Claude Desktop after saving.

Usage Examples

Once connected to Claude Desktop, try these prompts:

"Add a note about Docker networking with tags devops and docker"

"List all my notes"

"Search for notes about devops"

"Delete the welcome note"

Project Structure

mcp-server-typescript-starter/
├── src/
│   └── index.ts        # Main MCP server code
├── dist/               # Compiled JavaScript (after build)
├── package.json        # Dependencies and scripts
├── tsconfig.json       # TypeScript configuration
└── README.md           # This file

Code Walkthrough

1. Server Setup

const server = new Server(
  { name: "notes-manager", version: "1.0.0" },
  { capabilities: { tools: {}, resources: {} } }
);

2. Defining a Tool

server.setRequestHandler(ListToolsRequestSchema, async () => ({
  tools: [{
    name: "add_note",
    description: "Create a new note",
    inputSchema: {
      type: "object",
      properties: {
        title: { type: "string", description: "Note title" },
        content: { type: "string", description: "Note content" }
      },
      required: ["title", "content"]
    }
  }]
}));

3. Handling Tool Calls

server.setRequestHandler(CallToolRequestSchema, async (request) => {
  const { name, arguments: args } = request.params;
  
  if (name === "add_note") {
    // Create the note...
    return { content: [{ type: "text", text: "Note created!" }] };
  }
});

4. Exposing Resources

server.setRequestHandler(ListResourcesRequestSchema, async () => ({
  resources: [{
    uri: "notes://list",
    name: "All Notes",
    mimeType: "application/json"
  }]
}));

Next Steps

  • Add persistence (save notes to a file or database)

  • Implement Prompts (pre-defined instruction templates)

  • Add authentication for multi-user support

  • Deploy as a standalone service

Resources

Video Tutorial

Watch the full tutorial on Gheware DevOps AI:

License

MIT License - Feel free to use this as a starting point for your own MCP servers!

Made with ❤️ by Gheware DevOps AI

Available Tools

1 tool
create_greetingC

Create a personalized greeting message

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the person to greet
styleNoThe style of greeting (formal, casual, or excited)

TDQS

C2.9/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 of behavioral disclosure. It states 'Create' which implies a write operation, but fails to describe any behavioral traits such as side effects, permissions needed, or what the output looks like (e.g., format, success indicators). This is a significant gap for a mutation tool with zero annotation coverage.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly.

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 tool's purpose (creating a greeting, which implies a write operation), the lack of annotations, and no output schema, the description is incomplete. It does not address what the tool returns, potential errors, or behavioral context needed for safe and effective use, leaving critical gaps for the agent.

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 input schema has 100% description coverage, with clear documentation for both parameters (name and style with enum values). The description does not add any additional meaning beyond what the schema provides, such as examples or constraints. Given the high schema coverage, the baseline score of 3 is appropriate.

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

Purpose4/5

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

The description clearly states the tool's purpose with a specific verb ('Create') and resource ('personalized greeting message'), making it easy to understand what the tool does. However, since there are no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, which prevents a perfect score of 5.

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?

The description provides no guidance on when to use this tool versus other methods or tools. It lacks any context about prerequisites, alternatives, or specific scenarios where this tool is appropriate, leaving the agent without usage 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

B3/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly distinct by default.

Naming Consistency5/5

The single tool name follows a verb_noun pattern (create_greeting), which is consistent within this minimal set. There are no other tools to compare against, so no inconsistency exists.

Tool Count2/5

A single tool for a 'Notes Manager' server is too few for the apparent scope, as it suggests incomplete functionality. The tool count of 1 feels thin and inadequate for managing notes, indicating a mismatch with the server's purpose.

Completeness1/5

The tool surface is severely incomplete for a notes management domain. There are obvious gaps, such as missing operations to read, update, delete, or list notes, which will cause agent failures in typical workflows.

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-low-level-server

    0GiS0
    F
    license
    Not graded
    quality
    D
    maintenance
    A TypeScript-based MCP server that implements a simple note-taking system using low-level server components and streamable HTTP. It enables users to create, store, and summarize text notes through a set of tools, resources, and specialized prompts.
    3

  • perplexity-server

    dkmaker
    F
    license
    Not graded
    quality
    D
    maintenance
    A TypeScript-based MCP server that implements a simple notes system with resources, tools for creating notes, and prompts for summarization.

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/brainupgrade-in/mcp-server-typescript-starter'

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