env_sync.secret_pull — ainote MCP Tool
env_sync.secret_pull
(env sync secret pull) 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 env_sync.secret_pull from your client
- Claude Code ainote env_sync.secret_pull run in your project directory
- Claude Desktop ainote env_sync.secret_pull ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ainote env_sync.secret_pull ~/.cursor/mcp.json
- VS Code ainote env_sync.secret_pull .vscode/mcp.json
- Zed ainote env_sync.secret_pull ~/.config/zed/settings.json
- Windsurf ainote env_sync.secret_pull ~/.codeium/windsurf/mcp_config.json
- Cline ainote env_sync.secret_pull ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ainote env_sync.secret_pull ~/.gemini/settings.json
- Grok ainote env_sync.secret_pull .mcp.json (in your project root)
- ChatGPT ainote env_sync.secret_pull Settings → Connectors → Advanced → Developer mode
- Claude.ai ainote env_sync.secret_pull Settings → Connectors → Add custom connector
- LangChain ainote env_sync.secret_pull 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
- sync_audit_layer5
- handoff_save
- graph_soft_delete
- env_sync.secret_push
- 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.