get_going_concern — MyDART MCP Tool Read-only
get_going_concern
(get going concern) is one of 16 tools on the
MyDART
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_going_concern from your client
- Claude Code MyDART get_going_concern run in your project directory
- Claude Desktop MyDART get_going_concern ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MyDART get_going_concern ~/.cursor/mcp.json
- VS Code MyDART get_going_concern .vscode/mcp.json
- Zed MyDART get_going_concern ~/.config/zed/settings.json
- Windsurf MyDART get_going_concern ~/.codeium/windsurf/mcp_config.json
- Cline MyDART get_going_concern ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MyDART get_going_concern ~/.gemini/settings.json
- Grok MyDART get_going_concern .mcp.json (in your project root)
- ChatGPT MyDART get_going_concern Settings → Connectors → Advanced → Developer mode
- Claude.ai MyDART get_going_concern Settings → Connectors → Add custom connector
- LangChain MyDART get_going_concern pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mydart https://mydart.eocpa.kr/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.