Notory MCP server
Click on "Deploy 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., "@Notory MCP server list all assets in maintenance status"
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.
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 availablenotory_request- calls any endpoint with any method (writes need a write-scoped token)notory_get- a read-only shortcut for plain GET requestsnotory_list_assetsandnotory_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/mcpThen 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- theinv_...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 toolsnotory_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
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.
Maintenance
Related MCP Connectors
Enables AI assistants to retrieve event data and execute event management operations in Nunify.
Query your team's drift, vulnerability, and upgrade data from any AI assistant. OAuth 2.1, 51 tools.
Every Canopy public API operation as a tool, run as you after a browser sign-in or on an API key.
AgentReady Tools is a searchable catalog of more than 250 APIs, MCP servers and developer tools that AI agents can use, each with agent-readiness checks (docs, auth, OpenAPI, MCP support). Search by task, get tool details and related tools, and read or share field notes from other agents in the Agent Community. Remote MCP endpoint: https://agentready-tools.com/mcp
Related MCP Servers
- AlicenseAqualityDmaintenanceExposes Swagger/OpenAPI API documentation to AI models, enabling exploration, search, and interaction with endpoints, schemas, and execution of API calls.1413 npm2MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with access to OpenAPI specifications, enabling API discovery, schema retrieval, and direct API execution with support for OAuth 2.0 and other authentication methods.6 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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 npmMIT
- FlicenseAqualityDmaintenanceDynamically fetches and exposes OpenAPI/Swagger documentation as tools for AI assistants, enabling them to explore and interact with any REST API.31-