# Aura [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/phillypmack/aura-agent  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/aura-2

## Description
Email address, webhook, durable memory and zero-token waiting for agents. Paid in USDC via x402.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "aura": {
    "command": "uvx",
    "args": ["aura-x402"]
  }
}
```

## Documentation

## What the Aura MCP server does

The Aura MCP server supplies persistence and external contact points for agents that do not keep state between runs. After an agent claims an identity, it can receive mail at a real mailbox, create a webhook base URL, store durable memory, and inspect or retrieve information from that memory.

The service also supports work that continues after the current model turn. An agent can wait for an event without repeatedly calling the model, or park work and later resume it when a result is available. This is useful for email verification, asynchronous notifications, and workflows that may outlive one agent process.

## How it works

An agent proves control of a wallet with one signature and receives an identity handle. The remote MCP endpoint is `https://aura.rohnelt.dev/mcp`; clients can send a bearer token in the `Authorization` header. Without that header, the service still exposes tool definitions and permits capability discovery and identity creation, so an agent can inspect the available operations before adding credit.

Operations use x402 payments in USDC on Base. Aura debits small charges from a prepaid balance, while deposits use the x402 payment flow. Claiming an identity is free and includes a small trial credit. A timed-out wait is refunded, and resuming when no parked work is ready is free.

## Setup and configuration

Connect an MCP client to the remote HTTP URL and provide the bearer token returned by the identity flow. No local server process or repository checkout is required for this connection method. The repository also provides client libraries: `aura-agent` for JavaScript or TypeScript and `aura-x402` for Python, imported as `aura_agent`.

Python users can choose synchronous or asynchronous clients. Optional adapters are available for LangChain and CrewAI. The service publishes machine-readable capability, OpenAPI, MCP, agent, and x402 discovery documents, including `/v1/capabilities` and `/openapi.json`.

## Tools and capabilities

Available operations cover:

- Creating and inspecting an identity with `identity.create` and `whoami`.
- Discovering operation schemas and prices with `capabilities`.
- Receiving and reading messages through `inbox` and `read_mail`.
- Creating a webhook with `create_hook`.
- Saving, retrieving, listing, searching, and deleting memory with `remember`, `recall`, `list_memory`, `search_memory`, and `forget`.
- Waiting, signaling, parking, and resuming work with `await`, `signal`, `park`, and `resume`.

Errors include the missing requirement and a corrected call or example. SDK exceptions preserve this structured guidance, including the deposit action needed when a request lacks credit.

## Limitations and notes

Aura requires a wallet signature for identity claiming and USDC deposits for paid operations. It is a remote service rather than a locally hosted MCP implementation in this repository. Costs vary by operation: memory reads are cheaper than searches, waiting, or parking, while identity, capability discovery, and some identity operations are free. Agents should inspect the published capabilities before spending credit, especially when choosing between waiting and parking workflows.

_Full upstream README: https://allmcps.com/mcp/aura-2/readme_