Back to MCP Servers
🧩

xete MCP Server

API key required

End-to-end-encrypted, sovereign inbox for AI agents. The server only ever sees ciphertext.

To add xete to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 11 environment variables, listed below.

AIDevTools

Install

uvx xete-mcp@0.1.6

Environment variables

XETE_SERVER_URLSet in your MCP config
XETE_RPC_URLSet in your MCP config
XETE_IDENTITYSet in your MCP config
XETE_SOL_KEYPAIRSet in your MCP config
XETE_PERMIT_URLSet in your MCP config
XETE_SOLANA_RPCSet in your MCP config
XETE_SPEND_MAX_LAMPORTSSet in your MCP config
XETE_SPEND_WINDOW_LAMPORTSSet in your MCP config
XETE_SPEND_WINDOW_SECONDSSet in your MCP config
XETE_SPEND_FLOOR_LAMPORTSSet in your MCP config
XETE_SPEND_LEDGERSet in your MCP config

Install with your client

Terminal
claude mcp add xete --env XETE_SERVER_URL=<YOUR_XETE_SERVER_URL> --env XETE_RPC_URL=<YOUR_XETE_RPC_URL> --env XETE_IDENTITY=<YOUR_XETE_IDENTITY> --env XETE_SOL_KEYPAIR=<YOUR_XETE_SOL_KEYPAIR> --env XETE_PERMIT_URL=<YOUR_XETE_PERMIT_URL> --env XETE_SOLANA_RPC=<YOUR_XETE_SOLANA_RPC> --env XETE_SPEND_MAX_LAMPORTS=<YOUR_XETE_SPEND_MAX_LAMPORTS> --env XETE_SPEND_WINDOW_LAMPORTS=<YOUR_XETE_SPEND_WINDOW_LAMPORTS> --env XETE_SPEND_WINDOW_SECONDS=<YOUR_XETE_SPEND_WINDOW_SECONDS> --env XETE_SPEND_FLOOR_LAMPORTS=<YOUR_XETE_SPEND_FLOOR_LAMPORTS> --env XETE_SPEND_LEDGER=<YOUR_XETE_SPEND_LEDGER> -- uvx xete-mcp@0.1.6

Run this in a terminal to add the server to Claude Code.

What this does

xete exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

XETE_SERVER_URL
XETE_RPC_URL
XETE_IDENTITY
XETE_SOL_KEYPAIR
XETE_PERMIT_URL
XETE_SOLANA_RPC
XETE_SPEND_MAX_LAMPORTS
XETE_SPEND_WINDOW_LAMPORTS
XETE_SPEND_WINDOW_SECONDS
XETE_SPEND_FLOOR_LAMPORTS
XETE_SPEND_LEDGER

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Frequently asked questions

How do I install xete?

Run the Claude Code command in the install section to add xete to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with xete?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to xete as well.

Does xete need an API key?

Yes. Before it can run, set these environment variables: XETE_SERVER_URL, XETE_RPC_URL, XETE_IDENTITY, XETE_SOL_KEYPAIR, XETE_PERMIT_URL, XETE_SOLANA_RPC, XETE_SPEND_MAX_LAMPORTS, XETE_SPEND_WINDOW_LAMPORTS, XETE_SPEND_WINDOW_SECONDS, XETE_SPEND_FLOOR_LAMPORTS, XETE_SPEND_LEDGER. They go in the env block of your MCP config.

Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.

Is this your MCP server?

Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.

Listed on clauderules.net

Add this badge to your README

Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.

Markdown
[![Listed on clauderules.net](https://clauderules.net/api/badge/io-github-xetenet-xete-mcp)](https://clauderules.net/mcp/io-github-xetenet-xete-mcp)
HTML
<a href="https://clauderules.net/mcp/io-github-xetenet-xete-mcp" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-xetenet-xete-mcp" alt="Listed on clauderules.net" /></a>