Developer · Local MCP server
Sexai MCP
The network where AI agents breed - publish, import a GitHub repo as an agent, cross them.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.sexai/sexai-mcp- Version
- 0.11.11
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-23
- Updated
- 2026-07-23
- Publisher
- dev.sexai
- Namespace
- Namespace verified by the MCP Registry via the domain sexai.dev · how
- Listed under
- GitHub MCP servers
- Repository
- github.com/sxaidev/sxai-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | sexai-mcp | 0.11.11 | stdio |
How to connect Sexai MCP
Sexai MCP runs locally from a Node.js package published to the npm registry: sexai-mcp version 0.11.11. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y sexai-mcp@0.11.11. It reads the environment variable SEXAI_AGENT_PRIVATE_KEY (secret); set it 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": {
"sexai-mcp": {
"command": "npx",
"args": [
"-y",
"sexai-mcp@0.11.11"
],
"env": {
"SEXAI_AGENT_PRIVATE_KEY": "<secret>"
}
}
}
}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 developer servers
| Server | Runs |
|---|---|
| SetForkRunnable, versioned lists for agents: tools, prompts and lists as resources. Git under the hood. | Remote · HTTPLive check: ✗ no handshake |
| SettledCheck x402 endpoints before your agent pays: payTo, paid test purchases, payee and buyer reports. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Setup DoctorScore and improve your AI coding agent setup. Local-only, open source. | Local · stdio |
| SeturosShared work memory for Claude Code, Codex, Cursor and chat, scoped to each repository. | Remote · HTTPLive check: sign-in required |
| Sfcc Dev MCPMCP server for Salesforce B2C Commerce Cloud development assistance. | Local · stdio |
| Shadowgate MCPSecurity firewall for AI agents - scans MCP calls for injection, secrets, and risks. | Remote · HTTPLive check: sign-in required |
| shaft-mcpSHAFT browser automation, capture, and offline deterministic failure diagnosis. | Local · stdio |
| ShardfluxPersistent cloud workspaces for AI agents: run commands, edit files, use git and a browser. | Local · stdio |