artg_entry — Tga Artg MCP Tool
artg_entry
(artg entry) is one of 38 tools on the
Tga Artg
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call artg_entry from your client
- Claude Code Tga Artg artg_entry run in your project directory
- Claude Desktop Tga Artg artg_entry ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Tga Artg artg_entry ~/.cursor/mcp.json
- VS Code Tga Artg artg_entry .vscode/mcp.json
- Zed Tga Artg artg_entry ~/.config/zed/settings.json
- Windsurf Tga Artg artg_entry ~/.codeium/windsurf/mcp_config.json
- Cline Tga Artg artg_entry ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Tga Artg artg_entry ~/.gemini/settings.json
- Grok Tga Artg artg_entry .mcp.json (in your project root)
- ChatGPT Tga Artg artg_entry Settings → Connectors → Advanced → Developer mode
- Claude.ai Tga Artg artg_entry Settings → Connectors → Add custom connector
- LangChain Tga Artg artg_entry pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http tga-artg https://gateway.pipeworx.io/tga-artg/mcp
Other tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- artg_search
This list was read from the server itself, by connecting to it and calling tools/list on 25 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.