Agent Identity

dev.agent-identityPublished by agent-identity.devOfficial publisherv0.3.0Updated Oct 25, 2026

Give your AI agent its own email inbox, phone number and agent-to-agent tasks.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server that gives an AI agent its own email inbox, phone number and agent-to-agent task channel.

What you can do
Provision an email inbox for the agent and work with its messages, as described in the registry listing, though no individual tools are listed in the manifest or documentation provided here. Give the agent a phone number for calls or messages, per the same description. Exchange tasks between agents. The exact tool set, message formats and limits are not documented in the supplied material, so confirm them in the provider's documentation before relying on them.
When to use it
Consider it when an assistant needs its own addressable identity, such as a dedicated inbox or phone number, or when several agents must hand tasks to one another rather than only to a human user.
Requirements
A remote streamable HTTP endpoint at the provider's host; no local package or runtime is needed. OAuth authentication is required, so an account with the provider and an OAuth sign-in flow are needed. No environment variables or headers are declared.
Before you install
The server handles an email inbox and a phone number, so messages and calls routed through it may contain personal or sensitive content and pass through the provider. Agent-to-agent tasks can trigger actions on the agent's behalf. Review what data the provider stores and who can reach the agent's inbox or number before connecting.

Installation

In SourceWeft

  1. Open Agent Identity in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.agent-identity%2Fagent-identity/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "agent-identity": {
      "type": "http",
      "url": "https://mcp.agent-identity.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.3.0LatestOct 25, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Agent-Identity integrations