sync_audit_layer5 — ainote MCP Tool Mutating
sync_audit_layer5
(sync audit layer5) is one of 35 tools on the
ainote
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call sync_audit_layer5 from your client
- Claude Code ainote sync_audit_layer5 run in your project directory
- Claude Desktop ainote sync_audit_layer5 ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ainote sync_audit_layer5 ~/.cursor/mcp.json
- VS Code ainote sync_audit_layer5 .vscode/mcp.json
- Zed ainote sync_audit_layer5 ~/.config/zed/settings.json
- Windsurf ainote sync_audit_layer5 ~/.codeium/windsurf/mcp_config.json
- Cline ainote sync_audit_layer5 ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ainote sync_audit_layer5 ~/.gemini/settings.json
- Grok ainote sync_audit_layer5 .mcp.json (in your project root)
- ChatGPT ainote sync_audit_layer5 Settings → Connectors → Advanced → Developer mode
- Claude.ai ainote sync_audit_layer5 Settings → Connectors → Add custom connector
- LangChain ainote sync_audit_layer5 pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ainote https://api.ainote.dev/api/mcpOther tools on this server
- delete_task
- list_papers
- project_read
- project_write
- assumption_write
- judgment_submit
- judgment_list
- delete_dev_doc
- get_setup_guide
- vault_create
- vault_sync
- sync_push
- sync_push_batch
- sync_delete
- handoff_save
- graph_soft_delete
- env_sync.secret_push
- env_sync.secret_pull
- env_sync.secret_rotate
- env_sync_txn_push
- env_sync_txn_rollback
- tasks_read
- task_write
- dev_docs_read
- dev_doc_write
- sync_read
- vault_read
- env_sync_read
- env_sync_write
- graph_read
- graph_write
- handoff_read
- memory_read
- auth_key
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.