MCP capability reference
Understand the shape of RepoTunnel's capability-oriented MCP surface without relying on a hard-coded tool count.
Guides follow the current project source. Check the release notes for your installed version.
Project and workspace
- Workspace discovery
- Workflow readiness
- Project setup/memory/resume
- Paged large-project inspection
Work
- Safe file mutations
- Verification commands
- Live terminal and managed processes
- Git/GitHub
- Managed browser
- Desktop and AI Workspace
- Phone
- Team Mode
- Video
- Temporary/media helpers
- Continuity
Compatibility rule
Clients may cache MCP schemas. Refresh or rescan RepoTunnel actions after a schema change before assuming a new tool is missing.
Tool discovery and compatibility
Use the MCP client’s discovery/rescan flow to fetch the current RepoTunnel tool schema. Avoid hard-coding a total tool count; features evolve and some clients cache action definitions.
Workspace tools accept approved workspace IDs and relative paths rather than arbitrary host paths. Several mutation operations are not equivalent to simple filesystem calls because they can queue approval or enforce secret checks.
Read before mutation
Start with workspace discovery and readiness, inspect relevant files and policy, then perform the smallest authorized action. For long commands, use managed processes and inspect their output.
After edits, verify actual source content or Git diff. After browser mutations, inspect the page again when the receipt is ambiguous. After Phone operations, respect the current capability state.