All documents via mcp are {} empty

[macasas]

I'm running bmad, when it creates any document I get

manage_document (archon-3 MCP Server) {"action":"create","project_id":"8d7f95c6-6d27-4596-9e3…  │
 │                                                                                                    │
 │    params/content must be object, params/content must be null, params/content                      │
 │    must match a schema in anyOf
✦ Let me try creating a document with a minimal content structure:

 │ ✓  manage_document (archon-3 MCP Server) {"action":"create","project_id":"8d7f95c6-6d27-4596-9e3…  │
 │                                                                                                    │
 │    {"success": true, "document": {"id": "c874e2a5-59d5-4964-b53c-673011c20daf",                    │
 │    "project_id": "8d7f95c6-6d27-4596-9e31-b85183be73af", "document_type": "spec",                  │
 │    "title": "Architecture and Implementation Guide",                       │
 │    "status": "draft", "version": "1.0"}, "document_id":                                            │
 │    "c874e2a5-59d5-4964-b53c-673011c20daf", "message": "Document created                            │
 │    successfully"}                                                                                  │


 │ x  manage_document (archon-3 MCP Server) {"action":"update","document_id":"c874e2a5-59d5-4964-b5…  │
 │                                                                                                    │
 │    params/content must be object, params/content must be null, params/content                      │
 │    must match a schema in anyOf

and then the document is created with a title but only {} as the content. It then continues to make task after task continuing the project as if the documents contain prd, architecture and tech stack, ending in a completely pointless project and empty set of documents.

How can I get it to actually put the content into the documents it creates?

[macasas]

Based on the /mcp desc, and the fact I cannot get the manage_document to accept any json format, what should I be trying to pass into the value for "content". Seems unlikely that AGENT.md example has no information on manage_document, or anything on documents, so how is the agent supposed to know its a feature, or how to use it? AGENT.md doesn't explain how to call /mcp desc, so where does this info come from, I feel I am missing a piece of the archon puzzle. Archon no longer updates documents.

• manage_document
  Manage documents (consolidated: create/update/delete).

      Args:
          action: "create" | "update" | "delete"
          project_id: Project UUID (required)
          document_id: Document UUID for update/delete
          title: Document title
          document_type: spec/design/note/prp/api/guide
          content: Structured JSON content
          tags: List of tags (e.g. ["backend", "auth"])
          author: Document author name
  
      Examples:
          manage_document("create", project_id="p-1", title="API Spec", document_type="spec")
          manage_document("update", project_id="p-1", document_id="d-1", content={...})
          manage_document("delete", project_id="p-1", document_id="d-1")
  

[macasas]

Here is a workflow example of manage_document update failing.

│ ✓ health_check (archon MCP Server) {}
│
│ {"success": true, "health": {"status": "healthy", "api_service": true, "agents_service": false, "last_health_check":
│ "2026-01-02T07:49:09.822214"}, "uptime_seconds": 46156.23867225647, "timestamp": "2026-01-02T07:49:09.822367"}

✦ The Archon MCP server is healthy and connected. Here's the status:

• Overall status: healthy
• API service: available
• Agents service: not available
• Uptime: ~12.8 hours
• Last health check: Just now (2026-01-02 07:49:09)

The server is ready for use, though the agents service is currently unavailable.

> show me the raw content of document id 6d27706a-7b9a-4a66-8dd6-8582c9390add from project id 8d7f95c6-6d27-4596-9e31-b85183be73af

Here is a document where I added content in the UI, because that works. I wanted to see the correct format.

│ ✓ find_documents (archon MCP Server) {"document_id":"6d27706a-7b9a-4a66-8dd6-8582c9390add","project_id":"8d7f95c6-6d27-4596-9e31-b85… │
│
│ {"success": true, "document": {"id": "6d27706a-7b9a-4a66-8dd6-8582c9390add", "tags": [], "title": "ONNX TTS Project -
│ Final Documentation", "author": "User", "status": "draft", "content": {"markdown": "# Title\n\n## Header 1\nHere is some
│ text\n\n- here is a list item 1\n- here is a list item 2"}, "version": "1.0", "updated_at": "2026-01-02T07:47:51.338449",
│ "document_type": "spec"}}

✦ Here's the raw content of the document:

1 # Title
2
3 ## Header 1
4 Here is some text
5
6 - here is a list item 1
7 - here is a list item 2

Document Details:

• ID: 6d27706a-7b9a-4a66-8dd6-8582c9390add
• Title: ONNX TTS Project - Final Documentation
• Type: spec
• Status: draft
• Author: User
• Version: 1.0
• Last updated: 2026-01-02T07:47:51.338449

> update the content of document 90b0455a-d0f6-42fb-ad50-21e44bc2d8fa to have a title # Edited Title

✦ I'll update the document with the new title. Let me do that for you.

│ ✓ manage_document (archon MCP Server) {"action":"update","document_id":"90b0455a-d0f6-42fb-ad50-21e44bc2d8fa","project_id":"8d7f95c6… │
│ │
│ {"success": true, "document": {"id": "90b0455a-d0f6-42fb-ad50-21e44bc2d8fa", "tags": [], "title": "# Edited Title", │
│ "author": "User", "status": "draft", "content": {"markdown": ""}, "version": "1.0", "updated_at": │
│ "2026-01-02T07:52:28.110230", "document_type": "note"}, "message": "Document updated successfully"} │

✦ I've successfully updated the document with ID 90b0455a-d0f6-42fb-ad50-21e44bc2d8fa. The title has been changed to "# Edited Title". The
document is now updated with this new title, while maintaining its draft status and note type.

> you edited the title of the document, not edited the content of the document to have a markdown title, the docment content is still empty.
Add "# This should be my content title \n ## Description \n I will write a descriptin here" to the content

Even though the agent misunderstood which title, it shows manage_document can update the document title.
But not the document content.

│ x manage_document (archon MCP Server) {"action":"update","document_id":"90b0455a-d0f6-42fb-ad50-21e44bc2d8fa","project_id":"8d7f95c6… │
│ │
│ params/content must be object, params/content must be null, params/content must match a schema in anyOf

✦ I apologize for the misunderstanding. I'll update the document content to include the markdown title and description you specified.

│ x manage_document (archon MCP Server) {"action":"update","content":"{"markdown": "# This should be my content title\n## Descript… │
│ │
│ params/content must be object, params/content must be null, params/content must match a schema in anyOf │

✦ I apologize for the error. Let me try updating the content in a different format:

manage_document update fails, all documents are created but contain {} as content.

[macasas]

Similar issue
https://github.com/coleam00/Archon/issues/887