TriliumNext Notes MCP integration for AI agents.
Connect AI agents to TriliumNext Notes through 20 structured actions, including get attachment, create attribute, and delete attachment. Review authenticatio…
- ACTION CONTRACTS
- 20
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the TriliumNext Notes integration exposes
The TriliumNext Notes Agent App exposes 20 provider-backed actions for productivity work. Its current contract lets an authorized agent get trilium attachment metadata by attachment id, create a label or relation attribute on a trilium note, and delete a trilium attachment. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected TriliumNext Notes account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real TriliumNext Notes capabilities.
Showing 12 of 20 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_attachmentREADGet Trilium attachment metadata by attachment id.
INPUTS: attachmentId
create_attributeWRITECreate a label or relation attribute on a Trilium note.
INPUTS: attributeId / noteId / type / name / value
delete_attachmentHIGH IMPACTDelete a Trilium attachment.
INPUTS: attachmentId
create_branchWRITEPlace an existing Trilium note under another parent, or update that placement if it exists.
INPUTS: noteId / parentNoteId / notePosition / prefix / isExpanded
create_noteWRITECreate a note and place it under a parent in the Trilium note tree.
INPUTS: parentNoteId / title / type / content / mime
delete_attributeHIGH IMPACTDelete a Trilium label or relation attribute.
INPUTS: attributeId
delete_branchHIGH IMPACTDelete a Trilium branch; deleting a note's final branch also deletes the note.
INPUTS: branchId
delete_noteHIGH IMPACTDelete a Trilium note and all of its placements from the note tree.
INPUTS: noteId
get_attributeREADGet a Trilium label or relation attribute by attribute id.
INPUTS: attributeId
get_branchREADGet a Trilium note-tree branch by branch id.
INPUTS: branchId
get_noteREADGet Trilium note metadata by note id.
INPUTS: noteId
get_note_contentREADRead the text content of a text-based Trilium note.
INPUTS: noteId
INPUT CONTRACTS
Know what the action needs before it runs.
get_attachment
attachmentIdREQUIRED- A Trilium entity id containing 4 to 32 letters, digits, or underscores.
create_attribute
attributeIdREQUIRED- A Trilium entity id containing 4 to 32 letters, digits, or underscores.
noteIdREQUIRED- A Trilium entity id containing 4 to 32 letters, digits, or underscores.
typeREQUIRED- Whether this attribute is a label or relation.
nameREQUIRED- The attribute name without whitespace.
valueOPTIONAL- The label value or target note id for a relation.
delete_attachment
attachmentIdREQUIRED- A Trilium entity id containing 4 to 32 letters, digits, or underscores.
create_branch
noteIdREQUIRED- A Trilium entity id containing 4 to 32 letters, digits, or underscores.
parentNoteIdREQUIRED- A Trilium entity id containing 4 to 32 letters, digits, or underscores.
notePositionOPTIONAL- The note position under its parent.
prefixOPTIONAL- The branch-specific title prefix.
isExpandedOPTIONAL- Whether the branch should appear expanded.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Attachment
Get Trilium attachment metadata by attachment id. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_attachmentControl Create Attribute
Create a label or relation attribute on a Trilium note. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_attributeVerify with Create Attribute
Create a label or relation attribute on a Trilium note. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_attributeSAFETY BOUNDARY
Operate TriliumNext Notes with explicit limits
- Authorize TriliumNext Notes with API key and grant only the provider access required by the selected actions.
- 13 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_attachment`, `delete_attribute`, and `delete_branch` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in TriliumNext Notes rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the TriliumNext Notes task completed successfully.
CONNECTION MODEL
API key
Trilium ETAPI token sent as a Bearer credential. Create one under Options > ETAPI in your Trilium instance.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 7
- WRITE SIGNALS
- 9
- HIGH IMPACT
- 4
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by TriliumNext Notes.