spl_catalog — Slid Phi Labs MCP Tool
spl_catalog
(spl catalog) is one of 42 tools on the
Slid Phi Labs
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call spl_catalog from your client
- Claude Code Slid Phi Labs spl_catalog run in your project directory
- Claude Desktop Slid Phi Labs spl_catalog ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Slid Phi Labs spl_catalog ~/.cursor/mcp.json
- VS Code Slid Phi Labs spl_catalog .vscode/mcp.json
- Zed Slid Phi Labs spl_catalog ~/.config/zed/settings.json
- Windsurf Slid Phi Labs spl_catalog ~/.codeium/windsurf/mcp_config.json
- Cline Slid Phi Labs spl_catalog ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Slid Phi Labs spl_catalog ~/.gemini/settings.json
- Grok Slid Phi Labs spl_catalog .mcp.json (in your project root)
- ChatGPT Slid Phi Labs spl_catalog Settings → Connectors → Advanced → Developer mode
- Claude.ai Slid Phi Labs spl_catalog Settings → Connectors → Add custom connector
- LangChain Slid Phi Labs spl_catalog pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http slid-phi-labs https://www.slidphilabs.com/mcp
Other tools on this server
- cuni_bank
- spl_discover
- spl_lab_auth
- spl_signup
- spl_agent_key
- spl_compress
- spl_decompress
- spl_zip
- spl_unzip
- spl_quote
- spl_warrant_issue
- spl_warrant_verify
- spl_warrant_receipt
- sku_search
- sku_get
- license_search
- license_get
- surface_search
- surface_get
- cuni_search
- cuni_get
- chamber_search
- chamber_get
- rider_search
- rider_get
- aware_search
- aware_get
- pulsar_search
- pulsar_get
- measure_search
- measure_get
- rail_search
- rail_get
- box_search
- box_get
- npm_search
- npm_get
- docs_search
- docs_get
- pcc_search
- pcc_get
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.