Skip to main content
Glama
Notory MCP server

Notory MCP server

by ruffymk3

Notory MCP server

A small MCP server that lets an AI assistant work with your Notory inventory through the normal REST API.

Notory is a flexible, GDPR-compliant IT inventory and asset management (ITAM) tool - self-hosted or as EU-hosted SaaS. Product: https://notory.io/ · Docs: https://support.notory.io/

You hand it a Notory API token, point it at your instance, and the assistant can look things up ("which laptops are in maintenance?") or, if the token allows it, make changes. It never gets to do anything the token's owner couldn't do anyway - the same roles, scopes and tenant boundaries still apply.

What you get

Five tools. The first two are generic and between them cover the whole API:

  • notory_list_endpoints - lists the endpoints your instance exposes, so the assistant can find out what's actually available

  • notory_request - calls any endpoint with any method (writes need a write-scoped token)

  • notory_get - a read-only shortcut for plain GET requests

  • notory_list_assets and notory_get_asset - convenience wrappers for the thing people ask about most

Because the discovery and request tools read the live OpenAPI spec of your instance, the assistant can reach all 200-odd endpoints, not just assets.

Related MCP server: Open API MCP Server

Getting started

You need Node 18 or newer and an API token. Create the token in Notory under Settings, API tokens. It's shown once and starts with inv_. Give it the read scope if you only want look-ups, or write if the assistant should be able to change things.

Run it straight from npm with npx - no clone, no build step:

npx -y @notory/mcp

Then tell your MCP client where it lives. Most clients read a JSON config that looks like this:

{
  "mcpServers": {
    "notory": {
      "command": "npx",
      "args": ["-y", "@notory/mcp"],
      "env": {
        "NOTORY_BASE_URL": "https://demo.notory.io",
        "NOTORY_API_TOKEN": "inv_your_token_here"
      }
    }
  }
}

Restart the client and you're set. Try asking it to list the assets in maintenance, or to show a specific asset by its serial number.

Prefer to run from source (for development)? Clone the repo, then npm install and npm run build, and point the client at node with the absolute path to dist/index.js.

Configuration

Two environment variables, both required:

  • NOTORY_BASE_URL - your instance, e.g. https://demo.notory.io (no trailing /api)

  • NOTORY_API_TOKEN - the inv_... token; its scope decides read-only vs read/write

A word on safety

Stick to a read token unless you genuinely need writes. The server keeps no state of its own - it just forwards your requests over HTTPS and hands the response back. The token grants exactly the owner's permissions in exactly their tenant, nothing more.

Development

npm run dev   # tsc --watch
npm start     # run the built server (needs the two env vars set)

License

Proprietary. Copyright TougeTech - Raphael Ernst.

Available Tools

5 tools
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.

Inputs: path (required), query.

notory_get_assetA

Fetch a single asset by its id (GET /api/v1/assets/{asset_id}).

Inputs: asset_id (required).

notory_list_assetsB

List assets with optional filters and pagination. Thin wrapper over GET /api/v1/assets.

Inputs: page, query, status, page_size, +1 more.

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.

Inputs: search.

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.

Inputs: path (required), method (required), body, query.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation2/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Exposes Swagger/OpenAPI API documentation to AI models, enabling exploration, search, and interaction with endpoints, schemas, and execution of API calls.
      14
      13 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to discover, search, and call any REST API described by an OpenAPI or Swagger document. Supports multiple API endpoints with authentication and parameter handling.
      14 npm
      MIT