Permissioned MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_ACTOR | No | Identifier for the actor performing actions, used in audit logs. | |
| MCP_SCOPES | No | Comma-separated list of scopes (e.g., notes:read,notes:write). Controls which tools are available. | |
| MCP_DATA_FILE | No | Absolute path to the JSON file for persistent note storage. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notes.listA | List note metadata without returning note bodies. |
| notes.getA | Read one note by its opaque identifier. |
| notes.createA | Create a local note. Requires the notes:write scope. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: list returns metadata, get returns a full note, and create adds a new note. No overlap in functionality.
All tools follow the consistent pattern 'notes.<verb>', using simple, descriptive verbs (list, get, create). No naming style deviations.
Three tools is a reasonable scope for a basic note management server. It covers core operations without being too sparse or excessive.
The set supports listing, reading, and creating notes but lacks update and delete operations. While a minimal viable set, these missing operations are notable gaps for typical CRUD coverage.