Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@notepm-mcp-server search for meeting notes about project alpha"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An unofficial Model Context Protocol (MCP) server for NotePM - a knowledge management and documentation platform.
This server enables AI assistants like Claude to search, read, create, and update pages in your NotePM workspace.
Node.js >= 24
Related MCP server: mcp-multi-note
No installation required. Configure your MCP client to run the server directly with npx.
npm install -g @nonz250/notepm-mcp-serverAdd the following to your Claude Desktop configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"notepm": {
"command": "npx",
"args": ["-y", "@nonz250/notepm-mcp-server"],
"env": {
"NOTEPM_TEAM_DOMAIN": "your-team-domain",
"NOTEPM_ACCESS_TOKEN": "your-access-token"
}
}
}
}claude mcp add notepm \
--env NOTEPM_TEAM_DOMAIN=your-team-domain \
--env NOTEPM_ACCESS_TOKEN=your-access-token \
-- npx -y @nonz250/notepm-mcp-serverAdd the following to your Claude Code settings file (.claude/settings.json or .claude/settings.local.json):
{
"mcpServers": {
"notepm": {
"command": "npx",
"args": ["-y", "@nonz250/notepm-mcp-server"],
"env": {
"NOTEPM_TEAM_DOMAIN": "your-team-domain",
"NOTEPM_ACCESS_TOKEN": "your-access-token"
}
}
}
}codex mcp add notepm \
--env NOTEPM_TEAM_DOMAIN=your-team-domain \
--env NOTEPM_ACCESS_TOKEN=your-access-token \
-- npx -y @nonz250/notepm-mcp-serverIf you installed globally, replace npx with the direct command:
{
"mcpServers": {
"notepm": {
"command": "notepm-mcp-server",
"env": {
"NOTEPM_TEAM_DOMAIN": "your-team-domain",
"NOTEPM_ACCESS_TOKEN": "your-access-token"
}
}
}
}Tool | Description |
| List folders in a note with hierarchy |
| List all notes in your workspace |
| Search pages by keyword, note, or tag |
| Get a page's full content including title, body, and tags |
| Create a new page in a specified note |
| Update an existing page's content |
| List all tags in your workspace |
| Create a new tag |
Variable | Required | Description |
| Yes | Your NotePM team domain (e.g., |
| Yes | API access token from NotePM |
Log in to your NotePM workspace
Go to Personal Settings > Access Token
Generate a new access token
Copy the token and use it in your configuration
When developing this package, npx @nonz250/notepm-mcp-server won't work from within the project directory. Use the local build instead:
claude mcp add notepm \
--env NOTEPM_TEAM_DOMAIN=your-team-domain \
--env NOTEPM_ACCESS_TOKEN=your-access-token \
-- npm run start --prefix /path/to/notepm-mcp-servercodex mcp add notepm \
--env NOTEPM_TEAM_DOMAIN=your-team-domain \
--env NOTEPM_ACCESS_TOKEN=your-access-token \
-- npm run start --prefix /path/to/notepm-mcp-servergit clone https://github.com/nonz250/notepm-mcp-server.git
cd notepm-mcp-server
npm install
npm run buildNOTEPM_TEAM_DOMAIN=your-team NOTEPM_ACCESS_TOKEN=your-token npm run startnpm testnpm run lint
npm run formatContributions are welcome! Please see CONTRIBUTING.md for guidelines.
MIT
Create a new page in NotePM. Note code and title are required. Optionally specify folder_id to create the page in a specific folder.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | Page body (Markdown format) | |
| memo | No | Memo (max 255 characters) | |
| tags | No | Array of tags | |
| title | Yes | Page title (1-100 characters) | |
| folder_id | No | Folder ID to create page in (if omitted, created at note root) | |
| note_code | Yes | Note code to create page in |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full behavioral disclosure burden. It identifies the action as creating a new page but does not mention permissions, side effects, return values, error behavior, or whether creating could overwrite an existing note_code. This is minimal for a write operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences convey the action, the resource, and the key constraints without wasted words. The required parameters are stated up front, and the optional folder_id behavior follows naturally.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the essential action and required parameters, and the schema fully documents all six parameters. However, with no output schema and no annotations, it omits the expected result of the creation, how errors are surfaced, and any permission requirements, leaving the tool partially underspecified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3 even without additional parameter detail. The description restates that note_code and title are required and adds that folder_id is optional, but these facts are already present in the schema, adding little net value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Create a new page in NotePM.' It also clarifies the required fields, making the tool's purpose immediately clear and distinguishing it from update_page and create_tag.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool by saying 'Create a new page', but it does not explicitly mention alternatives or when not to use it. There is no guidance about preferring update_page for existing pages or search_pages for retrieval.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Create a new tag in NotePM.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Tag name (1-100 characters) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose behavioral traits like whether duplicate names are allowed, if the creation is irreversible, or what the response looks like. The minimal description leaves important behavioral aspects unknown.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, direct sentence. It is concise and to the point, earning a high score for structure.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the tool, the description still lacks essential context such as behavior on duplicate names, whether tags are scoped to a workspace, or if there are limits. For a complete understanding, more information is needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema fully describes the name parameter with constraints (1-100 characters). The description adds no extra meaning beyond what is already in the schema. With 100% schema coverage, score 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Create' and the resource 'a new tag in NotePM.' It is specific and distinct from sibling tools like list_tags. However, it lacks additional context about what a tag represents.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 vs alternatives, such as list_tags or create_page. No prerequisites or exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get a NotePM page. Retrieve title, body, tags and other details by page code.
| Name | Required | Description | Default |
|---|---|---|---|
| page_code | Yes | Page code |
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 describes a read operation without side effects, which is appropriate. However, it does not disclose potential behavioral traits like authentication needs or rate limits, but for a simple get, this is adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with two sentences, front-loading the action and resource. Every sentence adds value with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one required parameter, no output schema), the description covers the basic purpose and what is retrieved. It could mention that page_code is a unique identifier, but overall it is complete enough for effective usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single parameter 'page_code', so baseline is 3. The description adds 'by page code' but does not provide additional meaning beyond the schema's description. No format or examples are given.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action 'Get' and the resource 'NotePM page', and mentions retrieving title, body, tags, and other details by page code. It distinguishes from sibling tools like create_page and update_page.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when needing page details by page code, but lacks explicit guidance on when to use this tool instead of siblings like search_pages or list_notes. No exclusions or alternatives are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List folders in a NotePM note. Returns folder hierarchy with IDs and names.
| Name | Required | Description | Default |
|---|---|---|---|
| note_code | Yes | Note code to list folders from |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden for behavioral disclosure. It does not explicitly state that this is a read-only operation, nor does it mention authentication requirements, rate limits, or potential side effects. The description merely indicates the return format, leaving important behavioral context unaddressed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise at two sentences. The first sentence immediately states the purpose, and the second sentence adds return value details. No unnecessary words or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the tool (one parameter, no output schema, no annotations), the description covers the basic purpose and return format. However, it lacks details about the structure of the folder hierarchy (e.g., nested vs flat) and any ordering or pagination. The description is minimally complete but could be more informative.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage for the single parameter (note_code). The tool description does not add any additional semantic information about the parameter beyond what the schema provides. Thus, the description adds no extra value, meeting the baseline of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb (list), resource (folders), and scope (in a NotePM note). It also specifies the return value (folder hierarchy with IDs and names). This distinguishes it from sibling tools which deal with pages, tags, etc.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool (when you need to list folders in a note), but does not provide explicit guidance on when not to use it or mention alternatives. No exclusions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List all NotePM notes. Returns note codes, names, and descriptions.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (default: 1) | |
| per_page | Yes | Number of results (1-100, default: 20) | |
| include_archived | No | Include archived notes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description must carry the full burden. It describes a read operation but omits details like whether results are paginated beyond schema defaults, sort order, or rate limits. The description is functionally adequate but minimally informative.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is concise and front-loaded with purpose. However, it could be slightly expanded to include a brief note on pagination or scope without losing conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a list tool with 3 parameters and no output schema or annotations, the description is minimal. It does not clarify default behavior (e.g., whether archived are excluded by default), pagination limits, or sort order. It covers the basics but leaves gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so each parameter is already explained in the schema. The description does not add additional meaning or constraints beyond the schema, thus 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.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'List all NotePM notes' with a specific verb and resource, and specifies the returned fields (note codes, names, descriptions). It serves as a distinct listing operation among siblings like get_page (single retrieval) and search_pages (filtered retrieval).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 versus siblings such as search_pages or list_folders. There is no mention of context (e.g., 'Use for broad retrieval; for filtered results use search_pages').
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List all tags in NotePM. Can filter by note code.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number for pagination | |
| per_page | Yes | Number of results (1-100, default: 50) | |
| note_code | No | Note code (list tags within specific note) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must convey all behavioral traits. It states 'List all tags' but pagination parameters (page, per_page) imply it may not return all at once; this contradiction is not addressed. No mention of ordering, rate limits, or other behaviors.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise at two sentences, no wasted words. However, it could be structured slightly better to include key behavioral info without harming brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema is provided, and the description omits any details about the response format (e.g., fields, structure, pagination metadata). For a list tool, this is a significant gap, making the agent rely on assumptions.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the description does not add meaningful insight beyond what the schema already provides (e.g., note_code filtering is already described). With high schema coverage, baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('List all tags') and resource ('NotePM'), with an optional filter by note_code. It distinguishes itself from sibling tools like create_tag (different verb) and list_folders (different resource), but lacks explicit differentiation from potential search_tags tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description mentions a basic usage scenario ('Can filter by note code') but provides no guidance on when to use this tool versus alternatives (e.g., search_pages) or when not to use it. No exclusions or context for pagination are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search NotePM pages. Can filter by keyword, note, or tag.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (default: 1) | |
| query | No | Search keyword | |
| per_page | Yes | Number of results (1-100, default: 20) | |
| tag_name | No | Filter by tag name | |
| note_code | No | Note code (search within specific note) | |
| only_title | No | Search only in page titles (default: false) | |
| include_archived | No | Include archived pages (default: false) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are absent, so the description must carry the full burden. It does not disclose side effects, authentication needs, rate limits, or behavior for edge cases (e.g., empty query). As a search tool, it is likely read-only, but this is not explicitly stated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise: two short sentences with no redundant information. It front-loads the core purpose ('Search NotePM pages') and quickly summarizes filtering capabilities.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 7 parameters and no output schema, the description is insufficient. It fails to explain pagination behavior, default results, or how filters interact. For a search tool, details about result format or edge cases (e.g., no results) are missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the description adds minimal value. It mentions filtering by 'keyword, note, or tag' (mapping to query, note_code, tag_name), but omits other parameters like only_title and include_archived. This provides some context but not beyond what the schema already conveys.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Search NotePM pages' with filtering options (keyword, note, tag), distinguishing it from sibling tools like create_page, get_page, and list_notes. However, it lacks explicit differentiation from list-based tools and could be more specific about scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 versus alternatives (e.g., get_page for a single page, list_folders for navigation). The description does not mention prerequisites or exclusions, leaving the agent without context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Update an existing NotePM page. Page code is required. To move the page to a different folder, specify both folder_id and note_code.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | Page body (Markdown format) | |
| memo | No | Memo (max 255 characters) | |
| tags | No | Array of tags | |
| title | No | Page title (max 100 characters) | |
| folder_id | No | Folder ID to move page to (requires note_code) | |
| note_code | No | Note code (required when specifying folder_id) | |
| page_code | Yes | Page code to update |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It only states requirements (page_code required) and moving rule, but fails to disclose what happens if page doesn't exist, update semantics (merge vs replace), auth needs, or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with main purpose. Every sentence is necessary and no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple update tool with no output schema, but does not clarify that only provided fields are updated or the behavior when only page_code is given. Could be more complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
All 7 parameters have schema descriptions (100% coverage), baseline 3. The extra context about moving requiring both folder_id and note_code adds value beyond schema, justifying a 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Update an existing NotePM page' with a specific verb and resource. The mention of 'page code is required' and the moving rule distinguishes from sibling tools like create_page (create vs update) and get_page (read).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides a usage guideline: 'To move the page to a different folder, specify both folder_id and note_code.' However, it does not explicitly contrast with alternatives like create_page or when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.1.6create_pagev1.1.5create_pagev1.1.3create_pagecreate_tagget_pagelist_folderslist_noteslist_tagssearch_pagesupdate_pageEach tool targets a distinct resource and action (e.g., create_page vs. create_tag, get_page vs. search_pages, list_folders vs. list_notes vs. list_tags). There is no ambiguity between tools.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_page, list_folders, search_pages). No mixed conventions or inconsistent verb choices.
8 tools is well-scoped for a note/wiki management server. Each tool serves a clear purpose without unnecessary duplication or insufficiency.
The tool set covers core operations for pages (create, get, update, search) and tags (create, list), plus folder listing. However, crucial missing operations like delete_page, delete_tag, update_tag, and folder create/delete may force agents into dead ends.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Markdown-based note-taking with a hosted MCP server. Your notes serve you and your AI.
Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.
Search your AI chat history (ChatGPT, Claude, Codex) from any MCP client. Remote, private, read-only
An MCP server that integrates with Discord to provide AI-powered features.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nonz250/notepm-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
