MCP Tools

Postgram’s MCP endpoint mirrors REST capabilities in tool form.

What this page covers

Tool names, practical usage, and when to request compact vs full transport output.

Reference

• store: create an entity.
• recall: fetch entity by ID.
• search: query entities with optional filters.
• update: patch content and metadata.
• delete: soft-delete entity.
• task_create, task_list, task_update, task_complete.
• sync_push, sync_status.
• link, unlink.
• expand: graph neighborhood expansion.

Behavior notes:

• full_response: true returns REST-like payloads.
• toon: true on list-like tools (search, task_list, expand) for compact text.
• Compact search output may include edges.count and edges.relations. These are traversal hints only; neighbor content is returned by expand_graph or expand.

Notes

• MCP is served over Streamable HTTP at /mcp.
• Tool behavior remains aligned to REST; no separate permission model.
• Prefer plain search first. Set expand_graph: true when the user asks about causes, provenance, decisions, dependencies, blockers, ownership, involvement, related discussions, connected context, or ambiguous results.