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