request_startup_memo — Unicorn Screener MCP Tool
request_startup_memo
(request startup memo) is one of 5 tools on the
Unicorn Screener
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call request_startup_memo from your client
- Claude Code Unicorn Screener request_startup_memo run in your project directory
- Claude Desktop Unicorn Screener request_startup_memo ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Unicorn Screener request_startup_memo ~/.cursor/mcp.json
- VS Code Unicorn Screener request_startup_memo .vscode/mcp.json
- Zed Unicorn Screener request_startup_memo ~/.config/zed/settings.json
- Windsurf Unicorn Screener request_startup_memo ~/.codeium/windsurf/mcp_config.json
- Cline Unicorn Screener request_startup_memo ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Unicorn Screener request_startup_memo ~/.gemini/settings.json
- Grok Unicorn Screener request_startup_memo .mcp.json (in your project root)
- ChatGPT Unicorn Screener request_startup_memo Settings → Connectors → Advanced → Developer mode
- Claude.ai Unicorn Screener request_startup_memo Settings → Connectors → Add custom connector
- LangChain Unicorn Screener request_startup_memo pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http unicorn-screener https://unicornscreener.vc/api/mcpOther tools on this server
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.