Notory MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTORY_BASE_URL | Yes | Your Notory instance URL, e.g. https://demo.notory.io (no trailing /api) | |
| NOTORY_API_TOKEN | Yes | The inv_... token; its scope decides read-only vs read/write |
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 |
|---|---|
| notory_list_endpointsA | List the available Notory API endpoints (method, path, summary) from the live OpenAPI spec of the configured instance. Use this to discover what you can call before using notory_request. Optionally filter by substring. |
| notory_getA | GET any Notory endpoint (read-only). |
| notory_requestA | Call any Notory endpoint with any HTTP method (GET/POST/PUT/PATCH/DELETE). Writes require a token with the 'write' scope. Use notory_list_endpoints first to find the right path and payload shape. |
| notory_list_assetsB | List assets with optional filters and pagination. Thin wrapper over GET /api/v1/assets. |
| notory_get_assetA | Fetch a single asset by its id (GET /api/v1/assets/{asset_id}). |
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 5 tools
The generic tools notory_get and notory_request overlap for GET operations, and the specific asset tools (notory_list_assets, notory_get_asset) are thin wrappers over the same endpoints, creating functional redundancy. An agent could easily select the wrong tool for simple read tasks.
All tools use the notory_ prefix with underscore-separated snake_case, and specific tools follow a verb_noun pattern (list_endpoints, list_assets, get_asset). The generic notory_get and notory_request deviate slightly from the noun-bearing structure but maintain a consistent style, making the naming mostly predictable.
Five tools is an appropriate number for an API wrapper server, providing both generic access methods and convenient specific wrappers without excessive bloat or thinness.
The generic notory_request tool supports any HTTP method, enabling full CRUD operations on any endpoint, while notory_list_endpoints facilitates API discovery. The specific asset tools are redundant but do not create gaps in the surface.