Bug: MCP server schema forces ARRAY for note content, resulting in literal JSON array formatting in notes

[Amirmohammadomidi]

Since the 6.29.0 update, creating or updating standard note or markdown notes via the MCP server results in the literal JSON array syntax being saved into the note's body.

The tool description for create_note and update_note states that content accepts (string, or JSON array for task lists). However, the actual JSON schema exposed by the MCP server strictly enforces the content field to be of type ARRAY.

Because MCP clients (like Hermes Agent / Claude) strictly follow the schema, they are forced to wrap string content in an array to pass validation (e.g., ["# My Note Content"]). The backend then receives this array and writes its literal stringified JSON representation into the note, bracket characters and all.

Steps to Reproduce:

1. Use an MCP client to call mcp_poznote_create_note or mcp_poznote_update_note.
2. Attempt to create a standard markdown note. The client wraps the text in an array to pass the schema validator.
3. Check the resulting note in Poznote.
4. The note content literally displays: ["# My Note Content\n\nSome text"] instead of the raw string.

Expected Behavior:
The MCP server should accept a plain STRING for standard notes, or the MCP handler should unpack/join the array elements into a raw string before passing it to the Poznote backend API when the note_type is not tasklist.

Actual Behavior:
The schema enforces an array, and the backend dumps the serialized array literal into the note body.

Environment:

• Deployment: Official Docker Compose.
• Appeared after the 6.29.0 update.

[timothepoznanski]

Hello, Can you tell me which MCP clients do you use? I don't reproduce this issue with Copilot. Do you use Hermes?

[timothepoznanski]

Please try the latest update and let me know if it working now. Thanks.

Tim

[Amirmohammadomidi]

Hello,

My apologies for generalizing. Hermes Agent is very strict about following the JSON schema exactly as defined by the server.

I tested the latest version and can confirm the issue is fully resolved (verified on Hermes). Everything looks great on my end. Thank you for the quick update!

[timothepoznanski]

Thanks for your quick feedback. I supposed it was with Hermes.