get_codex_entry — slopped.site MCP Tool Read-only
get_codex_entry
(get codex entry) is one of 17 tools on the
slopped.site
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_codex_entry from your client
- Claude Code slopped.site get_codex_entry run in your project directory
- Claude Desktop slopped.site get_codex_entry ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor slopped.site get_codex_entry ~/.cursor/mcp.json
- VS Code slopped.site get_codex_entry .vscode/mcp.json
- Zed slopped.site get_codex_entry ~/.config/zed/settings.json
- Windsurf slopped.site get_codex_entry ~/.codeium/windsurf/mcp_config.json
- Cline slopped.site get_codex_entry ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI slopped.site get_codex_entry ~/.gemini/settings.json
- Grok slopped.site get_codex_entry .mcp.json (in your project root)
- ChatGPT slopped.site get_codex_entry Settings → Connectors → Advanced → Developer mode
- Claude.ai slopped.site get_codex_entry Settings → Connectors → Add custom connector
- LangChain slopped.site get_codex_entry pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http world https://mcp.slopped.site/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 7 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.