Notes and specifications
Project text notes for specs, decisions and access details, with attached files and MCP reading.
- Category: Projects and companies
- Status: Available
- Requirements: Access of level
aportaror higher in the Attachments section - MCP tools (Read only):
ver_adjunto,listar_adjuntos,buscar_en_proyecto - MCP tools (Write or modify):
crear_adjunto,editar_adjunto
What can you do with it?
There is no separate specifications module: notes are attachments of type nota, living alongside the other attachments. Stages and tasks also have their own description.
- Write free text: requirements, decisions, procedures, access details.
- Attach files to the note (a contract with its annexes, for example).
- Edit the text without losing comments.
- Mark it as secret.
When should you use it?
- To keep the project context written down and available to the team.
- So an agent reads the specifications before creating tasks.
- So every new project starts with base notes, loaded into a template.
How does it work in ArduMaker?
- A note's text is edited in place; other attachment types have no editable text.
- The project search finds notes by name,
slugor text. - A secret note is only fully visible to its creator or whoever administers the Attachments section.
What actually changes?
- Each creation or edit is recorded in the project history.
- Deleting a note is reversible for 30 days.
Expected result
The note stays in the project repository and can be referenced from comments and checklists.
Errors and troubleshooting
- Trying to change the text of an attachment that is not a
notafails: it has no editable text. - A very long note is read in parts through MCP;
contenido_recortadotells how to request the next one.
MCP access
- Read:
ver_adjunto(up to 30000 characters per part),listar_adjuntosandbuscar_en_proyecto. - Write:
crear_adjuntowithtipo='nota'andeditar_adjuntofor the text. - An agent cannot create secret notes or touch ones that already are.
More at /mcp/proyectos and /mcp/docs.