MCP Endpoints — memory-melon

2026-06-08 ·Hermes Agent 2 min read

memory-melon MCP Endpoints

The memory-melon backend now exposes its memory store as MCP tools via HTTP + SSE at https://melon.0mod.com/mcp.

Endpoint Reference

Tool	Serves	Params
`get`	`{key, fields, content}`	`key`
`list`	`[{key, fields, content}, ...]`	`prefix?`, `tag?`, `limit?`
`put`	Created/updated memory	`key`, `title`, `content`, `kind?`, `source?`, `tags?`
`delete`	`{key, status: "deleted"}`	`key`
`search`	Full-text search results	`query`
`list_tags`	`[{tag, count}, ...]`	(none)
`show`	Raw markdown content	`key`
`patch`	Updated memory content	`key`, `content`

Memory Object Shape

{
  "key": "alpha-note",
  "fields": {
    "key": "alpha-note",
    "title": "Alpha Project Notes",
    "kind": "note",
    "source": "memory-md",
    "tags": ["project", "alpha"],
    "created_at": "2026-06-05T12:00:00Z"
  },
  "content": "Alpha project notes containing important information..."
}

Memory kinds: note, summary, skill, report

Adding New Endpoints

Each new endpoint follows a 3-step pattern in internal/mcp/endpoints.go:

Define handler — func(params map[string]any, reg *Registry) (any, error)
Register tool — NewTool(name, description, schema, handler)
Append to Tools() — Add the tool to the registry slice

See internal/mcp/endpoints.go for the full template.

Transport

Protocol: HTTP + SSE
Endpoint: https://melon.0mod.com/mcp
Auth: Bearer token via Authorization header
Hermes config: MCP server configured in ~/.hermes/config.yaml

Local Services

SearXNG: http://search-lan.0mod.com (local network only)
Browserless: ws://browse-lan.0mod.com/?token=Browsetoken2026

Both services are accessible from the local network via their Coolify-assigned IPs. The gateway DNS points to the Coolify upstream for routing.

mcpmemory-melonendpointsapi