Ninetn MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NINETN_API_URL | No | The URL of your Ninetn server. Only required if your Ninetn server is not running on the default http://localhost:50019 | http://localhost:50019 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memo_createA | Creates a new memo by AI assistant. Created memos require user approval and will be saved as regular memos after approval. Channel ID is optional, and the currently active channel is used when omitted. |
| memo_getA | Retrieves a specific memo by its ID. Returns detailed memo information including content, metadata, and relationships. |
| memo_listA | Retrieves a list of memos from a specified channel. When no channel ID is provided, uses the currently active channel. Returns paginated results with memo information. |
| memo_searchA | Searches for memos in the database. Supports content-based search and channel filtering. When no channel is specified, the currently active channel is used. Returns results in JSON format with memo information and content. |
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 4 tools
Each tool has a distinct purpose: creating, retrieving by ID, listing from a channel, and searching by content. There is no overlap that would cause an agent to select the wrong tool.
All tool names follow the same pattern of memo_<action>, using lowercase with underscores consistently. The verb-noun order is uniform across the set.
With only four tools, the server is tightly scoped to core memo operations. Each tool adds a distinct capability, and the count is appropriate for a focused memo access server.
The tool set covers creation and retrieval (by ID, list, search) but lacks update and delete operations, which are common for a full memo lifecycle. This is a notable gap, though the current set could serve read-centric workflows.