Skip to content

[MCP] Emit progress notifications for long-running tools #554

Description

@manoahLinks

Summary

mindvault_buy and mindvault_register_onchain can take many seconds across sponsored-account funding, x402 payment, and Soroban submission, with no feedback until they finish.

Scope

  • Keep the implementation aligned with the existing MindVault architecture.
  • Add or update automated tests.
  • Update docs when the change affects contributors, deployers, or agent users.

Acceptance criteria

  • When the client supplies a progress token, both tools emit progress notifications at each phase boundary.
  • Behaviour is unchanged when no progress token is supplied, and tests cover both paths.
  • Failure cases are deterministic and safe to show in issue-driven contributor work.
  • Relevant local tests pass.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: mcpMCP server for AI agents (mcp/)difficulty: mediumModerate effort; touches a couple of areas or needs some contexttype: featureNew functionality or capability

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions