Skip to content

Latest commit

 

History

History
103 lines (76 loc) · 3.69 KB

integrations.md

File metadata and controls

103 lines (76 loc) · 3.69 KB

MCP client integrations

eggsearch integrate prints the exact registration for CodeGG and common MCP-capable agents and IDEs. It defaults to stdio, so the client owns the eggsearch process and no service is required.

eggsearch integrate list
eggsearch integrate codegg
eggsearch integrate codex --executable /usr/local/bin/eggsearch

Apply is explicit. Native CLI clients are changed through their supported commands. Strict JSON clients use an atomic write and create a timestamped .bak.* backup before changing only the eggsearch entry. A malformed file is rejected before any backup or write. No provider credentials are copied into client configuration.

CodeGG

CodeGG is the first-class integration. Stdio needs only the backend selector; CodeGG keeps its existing default command and arguments:

eggsearch integrate codegg --transport stdio --apply

For a previously installed persistent service, use the explicit remote MCP path:

eggsearch startup install
eggsearch integrate codegg --transport http --apply

The HTTP form selects the eggsearch search backend and adds CodeGG's normal remote mcp.eggsearch entry at http://127.0.0.1:11320/mcp. CodeGG still requires web_search and web_fetch; its provider diagnostic is best effort.

Native CLI clients

Codex, Claude Code, and VS Code use their current native registration commands:

eggsearch integrate codex --transport stdio --apply
eggsearch integrate claude --transport http --apply
eggsearch integrate vscode --transport stdio --apply

The adapters use codex mcp add, claude mcp add --scope user, and code --add-mcp respectively. Existing entries named eggsearch are updated by the client command; unrelated servers are not selected. The CLI checks the native command is available before applying.

Current references: Codex MCP CLI, Claude Code MCP, and VS Code MCP servers.

Settings-file clients

For direct local inference with LM Studio, see LM Studio.

Zed renders the current context_servers shape for its Settings Editor. Its settings are JSONC-capable and there is no stable registration CLI, so --apply intentionally remains print-only:

eggsearch integrate zed --transport stdio
eggsearch integrate zed --transport http

Cursor renders and can safely update the global ~/.cursor/mcp.json entry:

eggsearch integrate cursor --transport stdio --apply

OpenCode renders the current mcp.servers shape. A strict JSON ~/.config/opencode/opencode.json can be updated with --apply; an existing opencode.jsonc remains print-only so comments and trailing syntax are not destroyed:

eggsearch integrate opencode --transport http --apply

Current references: Zed MCP, Cursor MCP, and OpenCode MCP servers.

Verification and executable paths

An applied registration is verified with MCP initialize and tools/list. The minimum required tools are web_search and web_fetch; missing recommended tools are reported as a warning. HTTP verification first checks /healthz and rejects an unhealthy or non-eggsearch service.

When invoked from a development checkout, stdio apply requires an installed binary or an explicit --executable /path/to/eggsearch; it never writes a target/debug path into client configuration.

The integrations command does not install clients, start remote services, manage OAuth, or expose eggsearch beyond its loopback endpoint.