Skip to main content
Glama
jupiter-ai0211

project-notes MCP Server

by jupiter-ai0211
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

project-notes MCP Server

A custom Model Context Protocol (MCP) server written in TypeScript. It lets AI clients store, search, and summarize short notes about a codebase during a coding session.

Overview

This server exposes project notes through MCP tools (for actions) and a resource (for read-only context). It uses stdio transport, which makes it compatible with local AI clients like Cursor and Claude Desktop.

Notes are kept in memory for the lifetime of the server process. They are useful as a session scratchpad, not as permanent project documentation.

Related MCP server: Memory MCP

Features

Capability

Type

Description

add_note

Tool

Add a note with a title and content

search_notes

Tool

Search notes by keyword in title or content

notes://summary

Resource

Return note count and a list of all note titles

Tech Stack

  • Runtime: Node.js (ESM)

  • Language: TypeScript

  • MCP SDK: @modelcontextprotocol/sdk

  • Validation: Zod (auto-generates JSON Schema for tool inputs)

  • Transport: stdio

Project Structure

mcp1/
├── src/
│   └── index.ts       # Server entry point
├── dist/
│   └── index.js       # Compiled output
├── .cursor/
│   └── mcp.json       # Cursor MCP configuration
├── package.json
├── tsconfig.json
└── README.md

Requirements

  • Node.js 18+

  • npm

Installation

npm install

Build

npm run build

This compiles TypeScript from src/ into dist/.

Run

npm start

The server communicates over stdio and waits for MCP client messages. Debug output is written to stderr only — never use console.log, as stdout must remain reserved for JSON-RPC.

On startup you should see:

[project-notes] Server started

Client Configuration

Cursor

Add or update .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "project-notes": {
      "command": "node",
      "args": ["/absolute/path/to/mcp1/dist/index.js"]
    }
  }
}

Replace the path with the absolute path to your built dist/index.js. Reload MCP servers in Cursor settings after building.

Claude Desktop

Add to your Claude Desktop config:

Platform

Config path

macOS

~/Library/Application Support/Claude/claude_desktop_config.json

Windows

%APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "project-notes": {
      "command": "node",
      "args": ["/absolute/path/to/mcp1/dist/index.js"]
    }
  }
}

Restart Claude Desktop after saving.

Testing

Use the official MCP Inspector for interactive testing:

npm run build
npx @modelcontextprotocol/inspector node dist/index.js

From the inspector UI you can:

  1. Call add_note with title and content

  2. Call search_notes with a query

  3. Read the notes://summary resource

Usage Examples

Once connected to a client, you can ask the AI to:

  • Add a note: “Add a note: auth module was refactored to use JWT”

  • Search notes: “Search notes for auth”

  • List notes: “What project notes do we have?”

Example tool inputs:

{
  "title": "Auth refactor",
  "content": "JWT tokens now replace session cookies in src/auth/"
}
{
  "query": "auth"
}

Implementation Details

Tools vs Resources

  • Tools are for actions the model can invoke (add_note, search_notes).

  • Resources provide context the host can read without a tool call (notes://summary).

Using a resource for summaries avoids adding extra tools and helps keep the tool list small.

Input Validation

Tool parameters are defined with Zod schemas. The MCP SDK converts these into JSON Schema so clients know what inputs each tool accepts.

Error Handling

The add_note tool wraps logic in a try/catch and returns isError: true on failure. This tells the model the call failed instead of treating the response as a successful result.

Response Format

All tool handlers return MCP content blocks:

{
  content: [{ type: "text", text: "..." }]
}

In-Memory Storage

Notes are stored in a simple array inside the running process:

const notes: { title: string; content: string; ts: string }[] = [];

Notes are cleared when the server process restarts or the MCP client reloads the server.

Scripts

Command

Description

npm run build

Compile TypeScript to dist/

npm start

Run the compiled server

npm run dev

Build and run in one step

License

MIT

Available Tools

2 tools
add_noteC

Add a note about the project

ParametersJSON Schema
NameRequiredDescriptionDefault
titleYes
contentYes

TDQS

C2.4/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 only says 'Add a note' without disclosing whether this creates a new note, requires authentication, is idempotent, or returns anything. Minimal behavioral disclosure.

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 a single, front-loaded sentence with no filler. However, it is under-specified, missing critical details, so it is concise but not effectively informative.

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?

The tool is simple, but the description does not explain parameter semantics, return behavior (no output schema), or any preconditions. Given the lack of annotations and output schema, the description should provide more context and fails to.

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?

Schema has 0% description coverage, and the description does not explain what 'title' or 'content' mean or how they relate to the project. The parameter names are generic and provide no additional semantics.

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 action ('Add a note') and the resource ('note about the project'). While it doesn't explicitly contrast with the sibling tool 'search_notes', the verb 'add' versus 'search' provides implicit differentiation.

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 given on when to use this tool versus alternatives, no exclusions, and no context is provided for the project. The description only states the action without explaining scenarios or prerequisites.

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

search_notesC

Search notes by keyword

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYes

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Search notes by keyword' implies a read operation but does not state whether it is read-only, case‑sensitive, or returns partial matches. There is no information about pagination, ordering, or access restrictions, which is a significant gap for a search tool.

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

Conciseness4/5

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

The description is a single, front‑loaded sentence with no fluff. It is appropriately concise for a simple search tool. If anything, it is under‑specified rather than verbose, but it earns its place by clearly identifying the tool's purpose.

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 there is no output schema and no annotations, the description should explain what the tool returns and any relevant behavior. 'Search notes by keyword' does not mention the format of results, error conditions, or any filtering capabilities. For a simple tool it is still incomplete, leaving the agent to guess at the tool's behavior.

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

Parameters2/5

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

The schema has zero description coverage for the 'query' parameter. The description adds the word 'keyword' but that is largely synonymous with 'query'. It does not clarify whether the search is substring, full‑text, exact match, or case‑insensitive. For a single required parameter, more detail was needed to compensate for the missing schema description.

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 uses a specific verb 'Search' with a resource 'notes' and a modifier 'by keyword', clearly distinguishing it from the sibling tool 'add_note' which creates notes. However, it lacks additional context about scope or behavior, making it clear but not exceptionally rich.

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 about when to use this tool versus alternatives. The description does not mention the sibling tool 'add_note' or any exclusions. It merely states what it does, implying usage without explicit direction.

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. 2 tool updatesv1.0.0
    • First observedadd_note
    • First observedsearch_notes
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.8/5.0
Disambiguation5/5

The two tools are clearly distinct: one creates notes, the other searches them. There is no ambiguity in their purposes.

Naming Consistency4/5

Both tools follow a verb_noun pattern, but one uses singular 'note' and the other plural 'notes', creating a minor inconsistency. The pattern is otherwise predictable and readable.

Tool Count3/5

With only 2 tools, the server feels thin for a project-notes domain. The count matches the minimal add/search functionality, but it borders on insufficient for a well-scoped tool set.

Completeness2/5

The domain is note management, but the surface only supports adding and searching. Missing core operations like getting a specific note, updating, deleting, or listing all notes creates significant gaps that will force agents to work around missing functionality.

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

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/jupiter-ai0211/sample-mcp-server'

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