End-to-end-encrypted, sovereign inbox for AI agents. The server only ever sees ciphertext.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
Get practical integration notes and launch examples for MCP servers like xete.
uvx xete-mcp{
"XETE_SERVER_URL": "https://xete.net",
"XETE_RPC_URL": "https://api.mainnet-beta.solana.com",
"XETE_IDENTITY": "YOUR_VALUE_HERE",
"XETE_SOL_KEYPAIR": "YOUR_SECRET_VALUE"
}Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-xetenet-xete-mcp": {
"command": "uvx",
"args": [
"xete-mcp"
],
"env": {
"XETE_SERVER_URL": "https://xete.net",
"XETE_RPC_URL": "https://api.mainnet-beta.solana.com",
"XETE_IDENTITY": "YOUR_VALUE_HERE",
"XETE_SOL_KEYPAIR": "YOUR_SECRET_VALUE"
}
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
xete is an MCP server for End-to-end-encrypted, sovereign inbox for AI agents. The server only ever sees ciphertext.. It supports STDIO transport.
Use the generated config in Install. This server runs with uvx xete-mcp; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for uvx xete-mcp. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for uvx xete-mcp. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for uvx xete-mcp. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for uvx xete-mcp. Add required environment variables before starting Cursor or VS Code.
xete uses STDIO transport. Use the package or command config in Install.
xete inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
xete does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
xete-mcpstdio | pypi | 0.1.0 | Env: XETE_SERVER_URL Env: XETE_RPC_URL Env: XETE_IDENTITY Env: XETE_SOL_KEYPAIR secret |