MCP Tools
Scape exposes 100+ MCP tools to every coding session — browse the web, manage notes, run playbooks, query tables, and more.
Scape runs a Model Context Protocol (MCP) server that's automatically available to every coding session launched from Scape — Claude Code, Codex, and OpenCode. This gives your AI agents direct access to Scape's features — notes, playbooks, tables, the browser, and more — without leaving the terminal.
How it works
The MCP server (ScapeMCPServer) is installed at ~/Library/Application Support/Scape/bin/ and registered machine-wide. Every session can discover and call its tools automatically.
Tool calls are ownership-gated — each call is verified against the session that made it via PID-lineage walk, so sessions can only access their own project's resources.
Tool categories
Core
| Tool | Description |
|---|---|
create_session | Launch a new coding session |
create_worktree | Create a git worktree and optionally start a session in it |
list_sessions | List all active sessions |
open_file | Open a file in Scape's code editor |
query_oslog | Query macOS system logs for debugging |
Browser (22 tools)
Drive Scape's embedded browser programmatically. See the Browser Companion docs.
Notes (17 tools)
Full CRUD on notes, sections, versions, and search. See the Notes docs.
Playbooks
Create, run, and manage automation routines. See the Playbooks docs.
Tables (16 tools)
Create, query, and manage structured data tables. See the Tables docs.
Integrations
| Tool | Description |
|---|---|
list_github_prs / get_github_pr | Read GitHub pull requests |
list_jira_issues / get_jira_issue / search_jira_issues | Read and search Jira issues |
list_slack_messages | Read Slack channel messages |
SSH
| Tool | Description |
|---|---|
list_ssh_connections | List saved SSH connections |
delete_ssh_connection | Remove a saved connection |
Agent communication
| Tool | Description |
|---|---|
send_session_message | Send a message to another session |
message_parent | Report to your Argus manager |
scape_rendezvous_* | Agent-to-agent chat channel |
Approval behavior
Tools follow an approval taxonomy:
- Read-only and additive tools (listing, searching, creating notes) auto-approve.
- Destructive and execution-external tools (deleting resources, running playbooks, remote execution) require user confirmation.
Custom tools
You can define your own tools that agent sessions can discover and call.
Custom tools are stored at ~/.scape/tools.json and managed via the Tool Manage UI. The MCP server exposes list_custom_tools and run_custom_tool so sessions can discover and invoke them.