Add memory tools to agent-mcp

[haasonsaas]

Summary

• add evalops_recall and evalops_store_memory MCP tools backed by the memory service
• require a registered agent session for memory access, default to agent scope, and pass org/auth headers through to memory
• add focused tests plus README/protocol updates for the new memory workflow

Testing

• go test ./... -count=1

Closes #34

[cursor]

PR Summary

Medium Risk
Introduces new downstream calls to the Memory service and new session/organization header handling; failures are designed to degrade gracefully but could affect agent workflows if misconfigured.

Overview
Adds Memory-backed MCP tools evalops_recall and evalops_store_memory, wired into the server and documented in the agent protocol so agents can fetch prior context before acting and persist durable facts afterward.

Both tools require a registered (non-anonymous) agent session, default to agent scope/filtering, forward Authorization and X-Organization-ID to the Memory service, publish memory events, and gracefully degrade with informative outputs when Memory is not configured or unavailable. Includes focused unit tests validating defaults, header propagation, registration requirements, and failure behavior, plus README updates listing the new tools and MEMORY_BASE_URL semantics.

^{Reviewed by Cursor Bugbot for commit abf8f92. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is ON, but it could not run because the branch was deleted or merged before autofix could start.}

^{Reviewed by Cursor Bugbot for commit abf8f92. Configure here.}

[cursor]

Misleading error when session lacks organization ID

Medium Severity

When sessionOrganizationID returns empty, both toolRecall and toolStoreMemory return registrationRequiredResult, which tells the user "Call evalops_register first." However, the user may already have a valid registered session — the actual problem is a missing workspace_id. Since workspace_id is optional in evalops_register, a user who registered without one enters a confusing loop: register → recall → "register first" → register again → same error. The error message doesn't indicate that a workspace/organization ID is the missing piece.

Additional Locations (1)

• internal/agentmcp/tools_memory.go#L205-L209

 

^{Reviewed by Cursor Bugbot for commit abf8f92. Configure here.}