Productivity · Local MCP server
xete
End-to-end-encrypted, sovereign inbox for AI agents. The server only ever sees ciphertext.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.xetenet/xete-mcp- Version
- 0.1.6
- Status
- Active
- Category
- productivity
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-08-02
- Updated
- 2026-08-02
- Publisher
- xetenet (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/xetenet) · how
- Website
- xete.net
- Repository
- github.com/xetenet/xete-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | xete-mcp | 0.1.6 | stdio |
How to connect xete
xete runs locally from a Python package published to PyPI: xete-mcp version 0.1.6. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx xete-mcp. It reads these environment variables: XETE_SERVER_URL, XETE_RPC_URL, XETE_IDENTITY, XETE_SOL_KEYPAIR (secret), XETE_PERMIT_URL, XETE_SOLANA_RPC, XETE_SPEND_MAX_LAMPORTS, XETE_SPEND_WINDOW_LAMPORTS, XETE_SPEND_WINDOW_SECONDS, XETE_SPEND_FLOOR_LAMPORTS and XETE_SPEND_LEDGER; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"xete-mcp": {
"command": "uvx",
"args": [
"xete-mcp"
],
"env": {
"XETE_SERVER_URL": "<value>",
"XETE_RPC_URL": "<value>",
"XETE_IDENTITY": "<value>",
"XETE_SOL_KEYPAIR": "<secret>",
"XETE_PERMIT_URL": "<value>",
"XETE_SOLANA_RPC": "<value>",
"XETE_SPEND_MAX_LAMPORTS": "<value>",
"XETE_SPEND_WINDOW_LAMPORTS": "<value>",
"XETE_SPEND_WINDOW_SECONDS": "<value>",
"XETE_SPEND_FLOOR_LAMPORTS": "<value>",
"XETE_SPEND_LEDGER": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| x402 Web ToolsPay-per-call tools for agents: web page to Markdown, tech stack, email domain check (x402 USDC) | Remote · HTTPLive check: ✓ handshake |
| X402tools10 pay-per-call tools for AI agents: QR, screenshots, DNS, OCR, PDF, email & more. USDC on Base. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| xaffinity MCPMCP server for Affinity CRM - entity search, relationship intelligence, and workflow management. | Local · stdio |
| XcodeBuildMCPXcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities. | Local · stdio |
| XFMS - Model SourcePick the right LLM for any task. Ranked shortlist with rationale across 8 evaluators. | Remote · HTTPLive check: ✓ handshake |
| XFuelSubmit AI inference to XFuel, pay per task (USDC via x402 or TFUEL), fetch/verify ZK proofs. | Local · stdio |
| XLIDERead, write, analyze, test and diff the VBA in Office files, and the document around it. | Local · stdio |
| Xlsx For Ai50 spreadsheet tools for.xlsx: recalc formulas, repair broken refs, read/write, diff, audit. | Local · stdio |