KURA Notes MCP Client
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your KURA Notes API authentication key (required) | |
| KURA_API_URL | No | The KURA API base URL (optional) | https://kura.tillmaessen.de |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kura_searchC | Perform semantic search across KURA Notes. Returns relevant notes based on the query with metadata. |
| kura_createB | Create a new text note in KURA Notes. Use this to capture ideas, information, or any text content. |
| kura_getA | Retrieve a specific note by its ID. Returns the full content and metadata. |
| kura_list_recentB | List the 20 most recent notes with their metadata (without full content). Use this to get an overview of recent activity. |
| kura_deleteA | Delete a note by its ID. This action is permanent and cannot be undone. |
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
Each tool has a clearly distinct purpose with no ambiguity: create, delete, get, list recent, and search are all unique operations on notes. The descriptions reinforce this by specifying different actions (e.g., 'create a new text note' vs. 'retrieve a specific note'), making it easy for an agent to select the correct tool.
All tool names follow a consistent 'kura_verb' pattern (e.g., kura_create, kura_delete), with verbs that clearly indicate the action. There are no deviations in style or convention, making the naming predictable and easy to understand across the set.
With 5 tools, this server is well-scoped for a notes management system. Each tool serves a distinct and necessary function (create, delete, get, list, search), covering core operations without being overly complex or too sparse, which is ideal for this domain.
The tool set provides strong coverage for basic CRUD and search operations on notes, including create, delete, get, list, and semantic search. A minor gap exists in the lack of an update or edit tool, which could be a common need in note-taking workflows, but agents can work around this by deleting and recreating notes if necessary.