orca server get-logs --tail 200
SERVERS / SERVER FILES AND LOGS
Find the crash, fix the right file
Read logs, inspect files, update one configuration value, and confirm the server starts cleanly afterward.
Real example: Logs and scoped file editing
SURVIVALOWNER SCOPED
$ orca server read latest.logRun the example to see the verified result.
Use the protected server surface
The owner-bound CLI controls live servers. Public MCP can list your servers and install finished Orca creations.
Public MCP does not expose private server logs; use the owner-bound Orca server agent.
manage_server:get_logsmanage_server:list_filesmanage_server:read_filemanage_server:edit_filemanage_server:write_file
Private server files and logs stay in the protected owner-bound server surface.
How Orca makes it
Start with the result you want. Orca handles the Minecraft file structure and verifies the build.
Read the first failure
Orca follows the log from the origin instead of guessing from the last line.
Edit narrowly
Only the required configuration or project file is changed.
Restart and confirm
The server is checked again to prove the failure is gone.
What you get
The deliverable is Minecraft-ready, not just a concept image or a pasted code sample.
Recent logs
File tree
Focused configuration diff
Restart result
Keep building
Combine capabilities into one mod, plugin, world, or server workflow.