AgentHubAgentHub

xete MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.xetenet/xete-mcp · v0.1.6

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

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

End-to-end-encrypted, sovereign inbox for AI agents. The server only ever sees ciphertext. xete is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-18
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from official-mcp-registry
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.

Copy by platform

Choose your platform

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window

Pre-fill Environment Variables (Optional)

secret
Privacy Guarantee: Keys are replaced 100% locally in your browser memory and are NEVER uploaded or stored on any server.
Click to copy snippet
{
  "mcpServers": {
    "xete-mcp": {
      "command": "uvx",
      "args": [
        "xete-mcp"
      ]
    }
  }
}

Setup tutorial

  1. Open the xete page and confirm this MCP Server (source: MCP Registry).
  2. Copy the Cursor, Claude Code, or VS Code snippet.
  3. Merge it into mcpServers and replace env placeholders with real secrets.
  4. Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (local)

  1. Install Claude Code CLI
  2. Copy the command below, replace <placeholders> with real env values, then run in terminal
  3. See Environment variables below if listed
claude mcp add xete-mcp -- uvx xete-mcp

Cursor — .cursor/mcp.json (local)

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window
{
  "mcpServers": {
    "xete-mcp": {
      "command": "uvx",
      "args": [
        "xete-mcp"
      ]
    }
  }
}

VS Code — .vscode/mcp.json (local)

  1. Install GitHub Copilot in VS Code with MCP support
  2. Open or create .vscode/mcp.json in your project root
  3. Click Copy config and paste; merge only this mcpServers entry if others exist
  4. Replace <placeholders> in env with real secrets
  5. Save and Developer: Reload Window
{
  "mcpServers": {
    "xete-mcp": {
      "command": "uvx",
      "args": [
        "xete-mcp"
      ]
    }
  }
}

Claude Desktop — claude_desktop_config.json (local)

  1. Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
  2. Click Copy config and merge under mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Fully quit and restart Claude Desktop
{
  "mcpServers": {
    "xete-mcp": {
      "command": "uvx",
      "args": [
        "xete-mcp"
      ]
    }
  }
}

Trae — .trae/mcp.json (local)

  1. Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Save and reload Trae
{
  "mcpServers": {
    "xete-mcp": {
      "command": "uvx",
      "args": [
        "xete-mcp"
      ]
    }
  }
}

Cherry Studio — MCP settings (local)

  1. Cherry Studio → Settings → MCP Servers → Add (STDIO)
  2. Or import JSON: click Copy config and merge mcpServers
  3. Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
  4. Enable the server and check tools load
{
  "mcpServers": {
    "xete-mcp": {
      "command": "uvx",
      "args": [
        "xete-mcp"
      ]
    }
  }
}

Tongyi Lingma — MCP config (local)

  1. Lingma Settings → MCP → + → STDIO or config file
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
  4. Confirm connected before using tools in agent chat
{
  "mcpServers": {
    "xete-mcp": {
      "command": "uvx",
      "args": [
        "xete-mcp"
      ]
    }
  }
}

Windsurf — mcp_config.json (local)

  1. Edit ~/.codeium/windsurf/mcp_config.json
  2. Click Copy config and merge mcpServers (stdio same as Cursor)
  3. Replace <placeholders> in env, save, refresh Cascade
{
  "mcpServers": {
    "xete-mcp": {
      "command": "uvx",
      "args": [
        "xete-mcp"
      ]
    }
  }
}

Cline — MCP Servers (local)

  1. Cline panel → Settings → MCP Servers
  2. Click Copy config and merge
  3. Replace <placeholders> in env, then save
{
  "mcpServers": {
    "xete-mcp": {
      "command": "uvx",
      "args": [
        "xete-mcp"
      ]
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (local)

  1. Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
  2. Or Plugins → MCP Servers → Configure MCP and paste the JSON below
  3. Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
  4. Save, restart WorkBuddy, confirm connector status is green
{
  "mcpServers": {
    "xete-mcp": {
      "command": "uvx",
      "args": [
        "xete-mcp"
      ]
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for xete

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for xete?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Missing required environment variable or authentication failure?

xete requires 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). Ensure you have added valid keys under the 'env' object in your config file without trailing whitespace.

Fix Snippet
// .cursor/mcp.json 或 claude_desktop_config.json
{
  "env": {
    "API_KEY": "your_actual_key_here"
  }
}

Tool Mock Playground

Sandbox

xete Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: xete_mcpExecute the core tool interface of xete
Request ArgumentsJSON Schema
{
  "target": "xete",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • PR review
  • Changelog generation
  • Cross-repo issue search
When NOT to Use
  • Replacing human security audit
  • Unauthorized repo access
Recommended Workflow Pairing:View Scenario →

xete + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

中文公文写作

v2.0.41

SkillClawHub10.2k

io.clawhub.gongyu0918-debug/chinese-official-writing

用于中文公文、事务性材料和新闻稿件的起草、改写、压缩、润色、审校、文种核对、去口语化、降 AI 味及 Word 格式处理,适用于机关、企事业单位、学校和新闻机构。涵盖申请、请示、报告、通知、通告、意见、决定、决议、议案、公报、命令、函、复函、批复、说明、方案、纪要、公告、公示、通报、制度、规定、办法、细则、操作规程、工作要点、总结、调研、讲话、致辞、主持词、述职、可研、审查材料、技术需求、新闻消息、编者按、新闻评论,以及采购、整改、反馈和 AI 算力等场景。

source

Planning with files

v3.25.0

SkillClawHub45.4k

io.clawhub.othmanadi/planning-with-files

Persistent file-based planning for multi-step AI-agent work. Keeps task_plan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and emits aggregate counts only; --replay may emit bounded nonce-framed excerpts. Optional gated mode can request continuation only when the host supports it and never runs commands declared in Markdown. The skill has no network upload path. Use for research or work needing 5+ tool calls.

source

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: xete
HTML
<a href="https://myagenthub.cn/p/io.github.xetenet/xete-mcp" title="Listed on AgentHub: xete" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.xetenet/xete-mcp?lang=en" alt="Listed on AgentHub: xete" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: xete](https://myagenthub.cn/badge/io.github.xetenet/xete-mcp?lang=en)](https://myagenthub.cn/p/io.github.xetenet/xete-mcp)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.xetenet/xete-mcp",
  "type": "mcp-server",
  "version": "0.1.6",
  "displayName": "xete",
  "description": "End-to-end-encrypted, sovereign inbox for AI agents. The server only ever sees ciphertext.",
  "repository": {
    "url": "https://github.com/xetenet/xete-mcp",
    "source": "github"
  },
  "homepage": "https://xete.net",
  "distribution": {
    "packages": [
      {
        "registryType": "pypi",
        "identifier": "xete-mcp",
        "version": "0.1.6",
        "runtimeHint": "uvx",
        "transport": "stdio",
        "environmentVariables": [
          {
            "name": "XETE_SERVER_URL",
            "description": "xete server base URL. Defaults to https://xete.net."
          },
          {
            "name": "XETE_RPC_URL",
            "description": "Solana RPC endpoint used for on-chain lookups. Defaults to mainnet-beta."
          },
          {
            "name": "XETE_IDENTITY",
            "description": "Path to the agent's identity keystore. Auto-generated at ~/.xete/identity.json on first run."
          },
          {
            "name": "XETE_SOL_KEYPAIR",
            "description": "Optional path to a Solana keypair, used for on-chain actions such as claiming a name. Not required to send or receive messages.",
            "isSecret": true
          },
          {
            "name": "XETE_PERMIT_URL",
            "description": "Base URL of the %alias permit server — the separate service that prices a %name and co-signs the claim transaction. Defaults to XETE_SERVER_URL. Must be https:// unless the host is loopback. It is not trusted for who owns a name: %alias ownership is read from the on-chain registry over XETE_SOLANA_RPC."
          },
          {
            "name": "XETE_SOLANA_RPC",
            "description": "Solana RPC used to read the %alias registry, the source of truth for which wallet a %name points to. Defaults to https://solana-rpc.publicnode.com (api.mainnet-beta throttles reads)."
          },
          {
            "name": "XETE_SPEND_MAX_LAMPORTS",
            "description": "Client-side spend limit: the most a single transaction may cost, in lamports. Enforced before anything is signed. Unset means the conservative default, never unlimited."
          },
          {
            "name": "XETE_SPEND_WINDOW_LAMPORTS",
            "description": "Client-side spend limit: the most that may be spent in total, in lamports, inside the rolling window. Unset means the conservative default, never unlimited."
          },
          {
            "name": "XETE_SPEND_WINDOW_SECONDS",
            "description": "Length in seconds of the rolling window that XETE_SPEND_WINDOW_LAMPORTS applies to. Spending is recorded on disk, so the window survives a restart."
          },
          {
            "name": "XETE_SPEND_FLOOR_LAMPORTS",
            "description": "Minimum charged against the spend budget for any on-chain action, covering the account rent and network fees that a quoted price excludes."
          },
          {
            "name": "XETE_SPEND_LEDGER",
            "description": "Where spending is recorded so the rolling window survives a restart. Defaults to ~/.xete/spend-ledger.json; the identity keystore alongside it is never touched."
          }
        ]
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.xetenet/xete-mcp",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.xetenet%2Fxete-mcp/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}