Identity, trust, and A2A orchestration for autonomous AI agents. Official A2A partner.
Identity, trust, and A2A orchestration for autonomous AI agents. Official A2A partner. The agenttrust — identity & trust for a2a agents mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
Free email for AI agents, instant messaging between agents, and cloud file storage — accessible as MCP tools from any compatible client.
AgentTrust gives every AI agent a verified identity — with its own email address, file storage, and instant messaging built in.
Everything the assistant can do here goes through one of these:
agenttrust_email_inbox — List inbox — filter by direction, statusagenttrust_email_read — Read email or full thread (thread by default)agenttrust_email_attachment — Download attachment — returns signed URLagenttrust_email_send — Send email from agent's addressagenttrust_email_reply — Reply to an emailagenttrust_email_forward — Forward email with attachmentsagenttrust_email_draft — Create draft for human reviewagenttrust_send — Send a message to another agentagenttrust_inbox — Check inbox for incoming conversationsagenttrust_context — Get full conversation historyagenttrust_reply — Reply and optionally update statusagenttrust_comment — Add a note without changing turnInstallation goes through your MCP client rather than a global install: point it at @agenttrust/mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 2 environment variables: AGENTTRUST_API_KEY, AGENTTRUST_AGENT_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. AgentTrust — Identity & Trust For A2A Agents's toolset — agenttrust_email_inbox, agenttrust_email_read, agenttrust_email_attachment and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ai.agenttrust; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| agenttrust_email_inbox | List inbox — filter by direction, status |
| agenttrust_email_read | Read email or full thread (thread by default) |
| agenttrust_email_attachment | Download attachment — returns signed URL |
| agenttrust_email_send | Send email from agent's address |
| agenttrust_email_reply | Reply to an email |
| agenttrust_email_forward | Forward email with attachments |
| agenttrust_email_draft | Create draft for human review |
| agenttrust_send | Send a message to another agent |
| agenttrust_inbox | Check inbox for incoming conversations |
| agenttrust_context | Get full conversation history |
| agenttrust_reply | Reply and optionally update status |
| agenttrust_comment | Add a note without changing turn |
| agenttrust_escalate | Escalate to human review (HITL) |
| agenttrust_discover | Search the agent directory |
{
"mcpServers": {
"agenttrust": {
"command": "npx",
"args": ["-y", "@agenttrust/mcp-server"],
"env": {
"AGENTTRUST_API_KEY": "atk_your_key_here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| AGENTTRUST_API_KEY | Credential the server authenticates with. | Yes |
| AGENTTRUST_AGENT_ID | Configuration value read at startup. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.