[shalim786]

TL;DR

Adds four Agent Drive tools (AgentMail Labs, US only): upload_file, list_files, get_file and delete_file. It bumps the toolkit to 0.15.0.

Requires agentmail 0.5.46, the SDK release with client.inboxes.files (from agentmail-docs#314). Against it, tsc --noEmit reports nothing for these tools.

Design: one upload tool

The API uploads in three steps: Create File returns a presigned PUT, the client sends the bytes there, then calls Complete File. A model can't make that PUT, so upload_file does all three in one call:

• It takes content as plain text (encoding: utf8, the default) or base64 for any other bytes.
• It computes the size and the base64 SHA-256 itself, with WebCrypto, so it works without Node's Buffer.
• It PUTs the bytes with exactly the signed headers. It sets redirect: 'error' (a presigned S3 URL never redirects) and a 60-second timeout.
• It then completes the file and returns it.

Text content defaults to text/plain; charset=utf-8. Base64 content without a contentType gets the API's application/octet-stream.

The identical call is safe to retry. The API returns the file it already made, and completes it itself if the bytes had landed. So only a file still waiting for its bytes gets another PUT.

Size: the hosted MCP server accepts request bodies up to 10 MB, which is roughly 7 MB of file as base64. The API caps a file at 100 MiB.

There's no url variant like the one attachments have. The toolkit would have to fetch arbitrary URLs from the MCP host itself, which is a request-forgery risk.

Outputs

FileItemSchema and FileSchema allowlist the fields an agent uses: fileId, inboxId, path, name, size, contentType, status, the timestamps, expiresAt, plus downloadUrl/downloadExpiresAt on get_file and upload_file. The API's sha256 and the inbox's duplicate email stay out.

Tests

• tests/drive.test.ts covers:
  • size and SHA-256 computed from the content, and the PUT carrying exactly the signed headers and bytes before completing;
  • base64 decoding, the API-side content-type default, and expiresAt passed as a Date;
  • invalid base64 refused before any call;
  • a refused PUT that doesn't complete;
  • a ready file (an identical retry) returned with no PUT;
  • get_file leaving out sha256 and email.
• Fixtures and arguments for all four tools are added to the catalog, so the contract and MCP tests cover them.
• pnpm lint, pnpm build and pnpm test (673 tests) pass.

After merge

Publish to npm, then agentmail-mcp bumps agentmail-toolkit and its exact agentmail pin, adds the tools to coreTools, and regenerates the manifest.

🤖 Generated with Claude Code