dev_docs_read — ainote MCP Tool
dev_docs_read
(dev docs read) 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 dev_docs_read from your client
- Claude Code ainote dev_docs_read run in your project directory
- Claude Desktop ainote dev_docs_read ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ainote dev_docs_read ~/.cursor/mcp.json
- VS Code ainote dev_docs_read .vscode/mcp.json
- Zed ainote dev_docs_read ~/.config/zed/settings.json
- Windsurf ainote dev_docs_read ~/.codeium/windsurf/mcp_config.json
- Cline ainote dev_docs_read ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ainote dev_docs_read ~/.gemini/settings.json
- Grok ainote dev_docs_read .mcp.json (in your project root)
- ChatGPT ainote dev_docs_read Settings → Connectors → Advanced → Developer mode
- Claude.ai ainote dev_docs_read Settings → Connectors → Add custom connector
- LangChain ainote dev_docs_read 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_pull
- env_sync.secret_rotate
- env_sync_txn_push
- env_sync_txn_rollback
- tasks_read
- task_write
- 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.