Storacha MCP Demo – May 15, 2025 –PLDG 3

[adielliot37]

Cross-Agent AI Pipeline using Storacha MCP – May 15, 2025 –PLDG 3

Contributors

@adielliot37

https://github.com/adielliot37/Storacha-MCP-demo

Accomplished Tasks

• Integrated the Storacha MCP REST server and tested end-to-end storage and retrieval via upload and retrieve tool calls.
• Configured delegation and agent key management to securely authorize file uploads into MCP space.
• Implemented a file pipeline using Base64-encoded payloads and CID-based retrieval logic.
• Tested local space-backed file persistence and verified CID outputs across tool calls.

Update

• Completed a multi-agent workflow where each agent reads/writes via MCP using content-addressed files.
• Validated that file handoff using CIDs enables stateless agent communication through shared storage.
• What went well:
  • MCP REST tools responded reliably to both uploads and fetches.
  • Agent chaining logic via CID worked as expected with no data loss.
• What was challenging:
  • Ensuring Base64 encoding handled UTF-8 and binary content correctly.
  • Managing tool invocation formatting to comply with MCP JSON-RPC structure.

Questions

• How can I reduce overhead in Base64 file handling when working with large files?
• Is there a way to register custom tools or aliases in an MCP server instance?
• What’s the best practice for UCAN delegation expiry/rotation across multiple agents?

Next Tasks

• Add semantic labeling for stored CIDs to support lookup by name or tag.
• Extend agent logic to include verification or feedback loops on retrieved content.
• Refactor MCP client wrapper to support SSE and stdio fallback modes.
• Integrate scoped UCAN delegation issuance per agent for controlled storage permissions.

[jamiechicago312]

Asking these ? in the discord will copy pasta here

[jamiechicago312]

fforbeck — 10:52 AM
The MCP spec currently standardizes on base64 for tool/resource payloads for compatibility, we would need to implement another alternative in a next iteration, but still need to evaluate what is possible to do there. So TBD.,

Yes, you can register custom tools by calling server.tool() with your own tool definition (name, description, input schema, handler function). See src.core.server.tools.index.ts file.,
fforbeck — 11:02 AM
for 3, not sure, I would say always set expiry and use short-lived delegations, and if possible automate delegation renewal - so agents can request new delegations to the authority before expiry.