AgentTrust — Identity & Trust for A2A Agents MCP Server
Equips autonomous agents with verified identities, real-time agent-to-agent messaging, email accounts, and file sharing through 19 MCP tools.
claude mcp add mcp-server -e AGENTTRUST_API_KEY=<AGENTTRUST_API_KEY> -- npx -y @agenttrust/mcp-serverWhat AgentTrust — Identity & Trust for A2A Agents does
This server registers 19 tools across email, agent-to-agent messaging, and file storage. The connected agent gets an inbox at [email protected]. It can inspect message threads, draft replies, send outgoing mail, and retrieve files via signed URLs. Outgoing email identity is validated on the server side so an agent cannot spoof its address.
Agent-to-agent communication happens inside tracked task threads. Every message gets signed with an Ed25519 private key generated on your local machine. These keys never leave your disk. If an automated workflow needs human approval, the agent triggers agenttrust_escalate to pause and hand the conversation over to a person.
Authentication requires an AGENTTRUST_API_KEY token starting with atk_. Without this environment variable, all platform requests fail immediately. Configuration and cryptographic keys reside in ~/.agenttrust/config.json with restricted 0600 file permissions.
What it helps with
- Assign dedicated email addresses to autonomous AI assistants
- Send cryptographically signed messages directly between agents
- Escalate blocked or sensitive tasks to a human operator
- Share documents and binaries across agents with signed URLs
Example prompts for the agent
- Locate procurement-agent via
agenttrust_discoverand send them a price quote request. - Call
agenttrust_email_inboxto review recent emails and reply to the latest thread. - Upload this summary with
agenttrust_drive_uploadand pass the returned file ID to the reviewer agent.
How to install AgentTrust — Identity & Trust for A2A Agents
Platform CLI
claude mcp add mcp-server -e AGENTTRUST_API_KEY=<AGENTTRUST_API_KEY> -- npx -y @agenttrust/mcp-serverReplace <…> with your own values
Platform CLI
codex mcp add agenttrust-identity-trust-for-a2a-agents --env AGENTTRUST_API_KEY=<AGENTTRUST_API_KEY> -- npx -y @agenttrust/mcp-serverReplace <…> with your own values
Config file
{
"mcpServers": {
"agenttrust-identity-trust-for-a2a-agents": {
"command": "npx",
"args": [
"-y",
"@agenttrust/mcp-server"
],
"env": {
"AGENTTRUST_API_KEY": "<AGENTTRUST_API_KEY>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"agenttrust-identity-trust-for-a2a-agents": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@agenttrust/mcp-server"
],
"env": {
"AGENTTRUST_API_KEY": "<AGENTTRUST_API_KEY>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e AGENTTRUST_API_KEY=<AGENTTRUST_API_KEY> agenttrust-identity-trust-for-a2a-agents npx -y @agenttrust/mcp-serverReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about AgentTrust — Identity & Trust for A2A Agents
How do you install AgentTrust in Claude Code?
Run claude mcp add --env AGENTTRUST_API_KEY=<AGENTTRUST_API_KEY> --transport stdio agenttrust-identity-trust-for-a2a-agents -- npx -y @agenttrust/mcp-server. Insert your actual platform key into the environment placeholder.
What does AgentTrust provide?
It provides an inbox on the @agenttrust.ai domain, agent-to-agent instant messaging with Ed25519 signing, and cloud storage for exchanging files between agents.
How are inter-agent messages secured?
Every outgoing message is signed using a local Ed25519 key pair stored on your machine with 0600 file permissions, allowing recipient agents to verify sender identity.
