find_context_gaps — Dactic MCP Tool Read-only
find_context_gaps
(find context gaps) is one of 34 tools on the
Dactic
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call find_context_gaps from your client
- Claude Code Dactic find_context_gaps run in your project directory
- Claude Desktop Dactic find_context_gaps ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Dactic find_context_gaps ~/.cursor/mcp.json
- VS Code Dactic find_context_gaps .vscode/mcp.json
- Zed Dactic find_context_gaps ~/.config/zed/settings.json
- Windsurf Dactic find_context_gaps ~/.codeium/windsurf/mcp_config.json
- Cline Dactic find_context_gaps ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Dactic find_context_gaps ~/.gemini/settings.json
- Grok Dactic find_context_gaps .mcp.json (in your project root)
- ChatGPT Dactic find_context_gaps Settings → Connectors → Advanced → Developer mode
- Claude.ai Dactic find_context_gaps Settings → Connectors → Add custom connector
- LangChain Dactic find_context_gaps pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http dactic-mcp https://mcp.app.dactic.io/mcpOther tools on this server
- list_agents
- get_agent
- load_agent
- invoke_agent
- resolve_terms
- check_freshness
- get_policy
- list_skills
- get_skill
- ask_knowledge
- get_context_bundle
- get_user_context
- get_knowledge_provenance
- submit_agent_feedback
- check_against_policy
- get_skill_usage
- synthesize_agent
- create_agent_from_process
- get_task_status
- search
- fetch
- get_usage
- get_sync_status
- get_feedback_status
- recommend_agent
- compare_agent_versions
- get_entity_context
- get_context_delta
- retrieve_similar_cases
- query_work_dataset
- guide_workflow
- recommend_new_agents
- deploy_agent
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.