catalogues — terminal MCP Tool
catalogues
(catalogues) is one of 27 tools on the
terminal
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call catalogues from your client
- Claude Code terminal catalogues run in your project directory
- Claude Desktop terminal catalogues ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor terminal catalogues ~/.cursor/mcp.json
- VS Code terminal catalogues .vscode/mcp.json
- Zed terminal catalogues ~/.config/zed/settings.json
- Windsurf terminal catalogues ~/.codeium/windsurf/mcp_config.json
- Cline terminal catalogues ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI terminal catalogues ~/.gemini/settings.json
- Grok terminal catalogues .mcp.json (in your project root)
- ChatGPT terminal catalogues Settings → Connectors → Advanced → Developer mode
- Claude.ai terminal catalogues Settings → Connectors → Add custom connector
- LangChain terminal catalogues pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http terminal https://terminal.themonexus.com/mcpOther tools on this server
- search_wire
- list_threads
- get_thread
- get_context
- list_articles
- get_article
- deals
- deals_search
- deals_hot
- transcripts_search
- transcripts_context
- transcripts_episode
- transcripts_sentiment
- funding
- funding_latest
- funding_search
- agentpay
- agentpay_latest
- capex
- capex_summary
- verticals
- verticals_latest
- modelwatch
- modelwatch_latest
- modelwatch_search
- list_categories
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.