Schema | Notory MCP server

Notory MCP server

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

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": true }

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). `path` is rooted at the host, e.g. '/api/v1/assets' or '/api/v1/assets/{id}'. Pass query parameters via `query`.
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}).

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ruffymk3/notory_mcp'

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