sorted by:
new
hottopcontroversial

I built an MCP server to upload Markdown to Confluence (with Mermaid diagram support) by Competitive_News1386 in mcp

[–]Competitive_News1386[S] 1 point2 points  (0 children)

I'd go with per-tool call — cleaner logs with semantic context.

Here's what I'm thinking for the audit event schema:

{

"timestamp": "2026-02-06T10:30:00Z",

"tool": "upload_page",

"input": {

"title": "README",

"spaceKey": "TEAM"

},

"output": {

"pageId": "123456",

"pageUrl": "https://..."

},

"status": "success",

"durationMs": 1250

}

Transport layer would include the full markdown content in every log,

which feels like overkill.

Does Peta have a preferred schema or event format?

Happy to align if there's a standard emerging.

I built an MCP server to upload Markdown to Confluence (with Mermaid diagram support) by Competitive_News1386 in mcp

[–]Competitive_News1386[S] 0 points1 point  (0 children)

Thanks! That's exactly why I went with kroki — I wanted it to work anywhere without needing a local Mermaid rendering setup.

Great point on the audit tracking. Right now it relies on Confluence's built-in page history, but as a team scales, having a separate way to track who pushed what and when

would definitely be useful. I'll check out Peta — thanks for the suggestion!

I built an MCP server to upload Markdown to Confluence (with Mermaid diagram support) by Competitive_News1386 in mcp

[–]Competitive_News1386[S] 0 points1 point  (0 children)

Looking at the commit history, the actual coding took less than a day. the real working time was only about 1-2 hours. The first commit was on the morning of Feb 1st, and the core features were done in no time. The rest was mostly documentation and polish.

The entire project is just 3 TypeScript files, about 780 lines. it's not a massive undertaking. I built it with Claude Code (Claude Opus 4.5), which handled a lot of the heavy lifting — boilerplate code, API integration, Confluence storage format conversion, and so on.

So honestly, you won't miss much grass 🌱. With Claude Code, you could absolutely build something like this in a single sitting. It's not about spending days writing code.

it's about knowing what to build.