Tool catalog
Every tool an MCP client can call against your Skeleton. Identity tools return data you already authored — no approval needed. Everything else routes through the access-request gate. Pair from the Apps page to add an MCP client.
get_profile
Read the user's identity: display name, bio, tone, the active space, and the list of spaces this account can reach.
get_spaces
List every space the user can reach — owned, org-shared, and P2P-shared. Spaces are context containers; memories and inputs scope to them.
set_active_space
Switch the active space for this MCP session. Memory writes and reads route to whichever space is active.
get_memory
Retrieve memories matching a query. Returns the most relevant + recent items, with full provenance.
save_memory
Save a fact the user wants carried forward across sessions and clients. Stored verbatim with version history.
update_memory
Edit an existing memory by ID. Supports optimistic concurrency via a content hash to surface stale writes.
delete_memory_tool
Remove a memory. The version history persists so the deletion is auditable.
propose_consolidation
Suggest a consolidation of related memories — merge near-duplicates, retire stale ones, rewrite for clarity. The user reviews and approves the diff.
conn-*
Connector tools (Gmail, GitHub, Google Calendar, Jira, …) are registered dynamically at server start. Each upstream MCP server's tool list appears with a `conn-<provider>_` prefix.
list_pairings
List every MCP client paired to this account — with the OAuth client_id, scope, and last-used timestamp.
revoke_pairing
Disconnect a paired MCP client. Token is revoked immediately and the consumer must re-authenticate.