Decide whether registration is needed
Chats inside Notely receive its local workspace tools through their provider connection. Standalone registration is only needed when you want a separate Claude CLI or Kiro session outside the app to use Notely tools.
Notely supplies a local MCP server. Keep the app running and use Check Server in the provider’s settings to inspect its availability and configured port.
Register with Claude CLI or Kiro
- Open Settings → Chat → Claude CLI or Kiro and locate Notely Vault MCP Server. Check that its server is available.
- Review the enabled connections in the MCP settings tab. Registration also syncs enabled MCP-tab servers into the selected CLI’s configuration.
- Choose Register with Claude CLI or Register with Kiro only when you want that CLI configuration changed. Claude registration updates its settings file and restarts the Notely Claude connection; Kiro uses its MCP settings file.
- Test a small workspace search from the standalone CLI and check its permission prompts before allowing more tools.
Review tool permissions separately
Claude’s Allow All Notely Tools action adds Notely tools and currently connected MCP-tab tools to its allowlist so they can run without prompting. Review the connected tools before using this broad permission action.
Using tools from a standalone CLI does not inherit the YOLO flag of a Notely conversation. Notely command permissions, folder access, and the CLI’s own approvals can each affect a request.
Registration does not write global Claude instructions or Kiro steering files. Codex CLI and OpenCode CLI conversations inside Notely receive workspace tools through their app connection without these registration buttons.
If the standalone CLI cannot find a tool
- Keep Notely open, use Check Server, and confirm that the CLI points to the configured local port.
- Review the enabled MCP connections and run registration again if you intentionally changed what should be shared.
- Check CLI authentication, tool permissions, and Notely’s folder grants independently. Do not share configuration containing tokens in a public report.