check_in_event — Praetorium MCP Tool Read-only
check_in_event
(check in event) is one of 43 tools on the
Praetorium
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_in_event from your client
- Claude Code Praetorium check_in_event run in your project directory
- Claude Desktop Praetorium check_in_event ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Praetorium check_in_event ~/.cursor/mcp.json
- VS Code Praetorium check_in_event .vscode/mcp.json
- Zed Praetorium check_in_event ~/.config/zed/settings.json
- Windsurf Praetorium check_in_event ~/.codeium/windsurf/mcp_config.json
- Cline Praetorium check_in_event ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Praetorium check_in_event ~/.gemini/settings.json
- Grok Praetorium check_in_event .mcp.json (in your project root)
- ChatGPT Praetorium check_in_event Settings → Connectors → Advanced → Developer mode
- Claude.ai Praetorium check_in_event Settings → Connectors → Add custom connector
- LangChain Praetorium check_in_event pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http praetorium https://praetorium.gg/mcp
Other tools on this server
- list_my_rosters
- get_my_roster
- list_my_battles
- get_my_stats
- save_roster
- set_roster_visibility
- list_my_opponents
- create_battle
- get_my_battle
- submit_battle_action
- get_my_battle_report
- delete_battle
- search_reference
- get_reference
- get_reference_record
- list_factions
- list_reference
- list_units
- get_mission_matchup
- simulate_combat
- optimize_loadout
- list_data_updates
- check_roster
- grade_roster
- get_unit_options
- compare_rosters
- import_roster
- export_roster
- delete_roster
- copy_roster
- set_roster_archived
- get_my_collection
- list_my_events
- get_my_group
- get_my_event
- join_group
- join_league
- join_event
- submit_event_roster
- start_event_battle
- report_table_result
- get_skill
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.