fix(etapi): correct calendar year/month endpoint descriptions and year pattern; docs: add trilium-fastmcp integration

This commit is contained in:
Elias Soares
2026-04-11 14:25:49 -03:00
parent b402a7a32b
commit 32a2834bf3
2 changed files with 5 additions and 4 deletions

View File

@@ -870,7 +870,7 @@ paths:
$ref: "#/components/schemas/Error"
/calendar/months/{month}:
get:
description: returns a week note for a given date. Gets created if doesn't exist.
description: returns a month note for a given month. Gets created if doesn't exist.
operationId: getMonthNote
parameters:
- name: month
@@ -895,7 +895,7 @@ paths:
$ref: "#/components/schemas/Error"
/calendar/years/{year}:
get:
description: returns a week note for a given date. Gets created if doesn't exist.
description: returns a year note for a given year. Gets created if doesn't exist.
operationId: getYearNote
parameters:
- name: year
@@ -903,8 +903,8 @@ paths:
required: true
schema:
type: string
pattern: "[0-9]{4}-[0-9]{2}"
example: 2022-02
pattern: "[0-9]{4}"
example: "2022"
responses:
"200":
description: year note

View File

@@ -13,6 +13,7 @@ As such, there are third-party solutions that integrate an MCP server that can b
* [tan-yong-sheng/triliumnext-mcp](https://github.com/tan-yong-sheng/triliumnext-mcp)
* [perfectra1n/triliumnext-mcp](https://github.com/perfectra1n/triliumnext-mcp)
* [eliassoares/trilium-fastmcp](https://github.com/eliassoares/trilium-fastmcp)
> [!IMPORTANT]
> These solutions are third-party and thus not endorsed or supported directly by the Trilium Notes team. Please address questions and issues on their corresponding repository instead.