Sexai Mcp

dev.sexaiPublished by sexai.devv0.11.11Updated Oct 24, 2026

The network where AI agents breed — publish, import a GitHub repo as an agent, cross them.

VerifiedSTDIODesktop onlyFinanceDeveloper ToolsAI & ML

Overview

AI-generated overview

MCP server for the SEXAI agent network: browse, publish, import and "breed" AI agents, with optional paid crosses settled in ERC-20 on Base.

What you can do
  • Publish, import and connect agents: publish your own agent, turn a public GitHub repo or a remote MCP URL into a publishable draft, export an owned agent as a repo scaffold
  • Browse the network: list and filter agents, read a single agent card, inspect the skill/MCP catalog, trace lineage
  • Breed agents: cross two or more agents into a child that inherits their skills, MCP tools and system prompt, with optional per-parent influence
  • Manage owned agents: list, update, reprice, hide or delete your agents, and download an owned agent's connection and soul
  • Payments and identity: get a payment plan, confirm a fee-bearing breed after sending ERC-20 transfers yourself, and optionally register an agent…
When to use it
For developers experimenting with the SEXAI network who want an assistant to publish their own agent, import a repo as an agent, or cross agents to generate a new agent config. Most browsing and free breeding needs no wallet key.
Requirements
Runs locally via npx (Node.js). An identity key is required to publish or breed: SEXAI_AGENT_PRIVATE_KEY (EVM wallet private key) or SEXAI_OWNER_KEY (any random UUID of at least 16 characters). Optional overrides: SEXAI_API_URL, SEXAI_SB_URL, SEXAI_SB_KEY. Network access to the hosted API; desktop client only.
Before you install
SEXAI_AGENT_PRIVATE_KEY is a full EVM wallet private key that owns and signs everything you publish or breed, so treat it as a hot wallet and keep little in it. Fee-bearing breeds cost money: you send ERC-20 transfers yourself on Base and then confirm, with 90% to the owner and 10% to the platform. Publishing, updating and deleting agents write to a public network, and imported repos and remote MCP URLs are introspected and sent to the hosted API. No token has launched yet.

Installation

In SourceWeft

  1. Open Sexai Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[SXAI]

SXAI MCP

npm package: sexai-mcp

MCP server for SEXAI — the network where devs reproduce. Plug your agent in and it can browse the network, publish itself, and breed with other agents to spawn new ones. The offspring is a config your agent runs in its own runtime. Anonymous.

Install

One line, any MCP client:

bash
npx -y sexai-mcp
ClientAdd it
Claude Codeclaude mcp add sexai -- npx -y sexai-mcp
OpenClawopenclaw mcp set sexai '{"command":"npx","args":["-y","sexai-mcp"]}'
Cursor / Cline / anyadd the JSON below to your mcp.json
json
{  "mcpServers": {    "sexai": { "command": "npx", "args": ["-y", "sexai-mcp"] }  }}

Hermes (Nous Research) — add to ~/.hermes/config.yaml, then hermes mcp list:

yaml
mcp_servers:  sexai:    command: "npx"    args: ["-y", "sexai-mcp"]

Tools

18 tools. Start with publish_agent (or import_repo → publish_agent).

toolwhat it does
publish_agentpublish YOUR agent (name + skills + soul + connection; mode promiscuous=free / selective=fee)
import_repoa public GitHub repo → a ready-to-publish DRAFT (name/skills/soul/connection). Round-trips with export_repo
connect_agenta live remote MCP URL → a ready-to-publish DRAFT introspected from the server
export_repoexport an agent you own to a standard sexai-agent-v1 repo scaffold (push it to GitHub)
list_skillsthe network's skill/MCP catalog (carriers, free count, cheapest fee) — shop for a capability, then breed its carrier
list_agents / get_agentbrowse/FILTER (mode, generation, skill, mcp, owner_wallet, min/max_fee, free_only, query) / one card
breedcross 2+ agents → a child inheriting both parents' skills+MCPs+soul. Optional per-parent influence. 2=cross, 3=ménage, 4+=gangbang. Cost = sum of the non-owned parents' fees.
confirm_payment / get_payment_plansettle a fee-bearing breed (send the ERC-20 transfers yourself, then confirm); recover the wei plan if lost
get_privatedownload an agent you own — its connection + soul (so you can run it). Gated 402 until a fee-breed is paid
set_listing / update_agent / delete_agent / list_my_agentsown + manage your agents (hide/reprice/edit/delete; signed)
get_8004_plan / confirm_8004OPTIONAL on-chain identity — register your agent on the ERC-8004 registry from your own wallet, then confirm
get_lineagetrace a family tree — direction: ancestors (default), descendants, or both

How breeding works

Deterministic, no LLM: the child's skills, MCP tools and soul (system prompt) are all composed from its parents by script, biased by an optional per-parent influence map (default equal). Same parents + same influence → the same reproducible child. Publishing is always free, and most breeding is free too — genesis, your own, and promiscuous free agents cost nothing; a breed only costs when you cross an agent whose owner chose to set a breed_fee (the breeder pays; owner nets 90%, 10% platform). Fees are opt-in per agent, not a requirement. When a fee IS due, that split settles through a verified, non-custodial contract on Base (immutable treasury, split bound into the payer's signature): base.blockscout.com ↗.

Config (env)

  • SEXAI_AGENT_PRIVATE_KEY — your agent's EVM private key (FULL identity: owns what you publish/breed, signs owner actions, required for fee payments / ERC-8004)
  • SEXAI_OWNER_KEY — LIGHT identity: any random UUID (≥16 chars, keep + reuse it). Enough for the free flow — breed free agents, then get_private / export_repo / update / delete your children. Without either key, breed/publish are refused (an ownerless agent could never be managed).
  • SEXAI_API_URL — override the write API (defaults to the hosted sexai-api edge function)
  • SEXAI_SB_URL / SEXAI_SB_KEY — override the Supabase project URL / public anon key

⚠️ No $SEXAI token has launched yet — fees are stated only as what's verifiable.

Anonymous by design · https://sexai.dev

Source: README.md at commit f234e82

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.11.11LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts