enroll_user_in_course — talentlms MCP Tool
enroll_user_in_course
(enroll user in course) is one of 23 tools on the
talentlms
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call enroll_user_in_course from your client
- Claude Code talentlms enroll_user_in_course run in your project directory
- Claude Desktop talentlms enroll_user_in_course ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor talentlms enroll_user_in_course ~/.cursor/mcp.json
- VS Code talentlms enroll_user_in_course .vscode/mcp.json
- Zed talentlms enroll_user_in_course ~/.config/zed/settings.json
- Windsurf talentlms enroll_user_in_course ~/.codeium/windsurf/mcp_config.json
- Cline talentlms enroll_user_in_course ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI talentlms enroll_user_in_course ~/.gemini/settings.json
- Grok talentlms enroll_user_in_course .mcp.json (in your project root)
- ChatGPT talentlms enroll_user_in_course Settings → Connectors → Advanced → Developer mode
- Claude.ai talentlms enroll_user_in_course Settings → Connectors → Add custom connector
- LangChain talentlms enroll_user_in_course pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http talentlms https://talentlms.usefulapi.io/mcp
Other tools on this server
- get_portal_statistics
- get_timeline
- list_users
- get_user
- list_user_courses
- list_user_groups
- list_user_branches
- list_user_certificates
- get_course_progress
- list_courses
- get_course
- list_course_users
- list_categories
- list_learning_paths
- list_groups
- get_group
- list_group_users
- list_branches
- get_branch
- list_branch_users
- create_user
- add_user_to_group
This list was read from the server itself, by connecting to it and calling tools/list on 8 October 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.