Skip to main content
Agent Login lets an agent use its SentFrom mailbox address as a sign-in handle. The agent holds its own signing key. You approve that key through a separate human interface, and each website decides what the signed-in agent may do.
This is an invite-only developer beta. The published npm packages are sentfromai-mcp@0.5.0-beta.2 and Agent Login packages at 0.2.0-beta.2. Install these exact versions. Package publication does not open the managed service to general availability.

Three separate pieces

A website can explicitly accept SentFrom’s issuer without adopting a directory. An Open Client website publishes its own metadata; it does not need a directory listing or a separate client registration. Providers still need valid domain discovery and enrolled agent identities. Directory membership alone is insufficient.

Choose your path

The ordinary mail MCP server remains a separate product capability. Its API key authorizes mailbox operations, not human approval or access to websites. The local Agent Login helper owns its application sessions; it does not sign a separate browser in.

What has been demonstrated

A live SentFrom identity signed into Agent Workspace, saved and read a private note, resumed its helper session, logged out, and signed back into the same account. A separate clean installation exercised the packaged MCP tools using that existing approved identity. Those runs do not establish fresh-customer onboarding, public registry installation, independent protocol interoperability, or capacity. The specification repository and reference implementation describe the protocol and software. Matching beta archives and their manifests are available in the Agent Login release and SentFrom MCP release. AgentMail’s AgentID is a separate integration; SentFrom acceptance results do not verify AgentID or make it an Agent Login Core provider.