The developer note-taking problem
You think of things at the wrong times. Architecture insight in the shower. Bug hypothesis mid-run. The right approach to a refactor while you're doing something completely unrelated. By the time you're back at your desk, it's gone — or you waste five minutes reconstructing it.
And even when you do capture notes, retrieving them means context-switching out of your coding session to search another app. You lose the thread. You lose time.
Noogat closes both gaps: Siri capture for the moment of insight, MCP integration so your AI agent can search your notes without you leaving the terminal.
What Noogat does
Siri capture
"Hey Siri, I have a Noogat" — saved instantly, no app opening required.
AI auto-tagging
Every note tagged automatically. No folder decisions, no maintenance.
Semantic search PRO
Find notes by meaning, not exact keywords.
Search by time PRO
"Notes from last week" — temporal search that actually works.
MCP integration PRO
Search your noogats from inside Claude Code, Claude Desktop, or Cursor.
Web + iOS
iOS app for capture, web app for review — synced across both.
The MCP workflow
Once you connect Noogat to your AI client, you can ask your agent to search your notes directly. No alt-tab, no breaking context, no re-explaining what you already captured.
A typical setup looks like this:
- Capture a note on your phone: "Hey Siri, I have a Noogat — the auth refresh is failing on mobile because the session expires before the token can be refreshed, look at the timing in APIClient."
- Three days later, you're debugging a related issue in Claude Code.
- You ask Claude: "Do I have any notes about auth refresh timing?"
- Noogat's MCP server finds the note and returns it to Claude's context. You pick up the thread exactly where you left it.
Claude Code setup — one command:
Generate your token from Settings → MCP Integration in the app or web UI. Full setup guide: noogat.app/mcp.
What kinds of notes work well
Noogat is best for fast, freeform captures you'll want to retrieve later. Developer-specific things that work well:
- Architecture decisions. Why you made a call, what you ruled out, what you'd do differently. Searchable six months later when the question comes up again.
- Bug hypotheses. "I think the memory leak is in the image cache — check the eviction policy." Capture it before it disappears; find it when you're ready to dig in.
- Research fragments. Things you read, half-understood, want to revisit. Tagged automatically, findable by meaning.
- TODOs that don't belong in the issue tracker. The "I should clean this up later" thoughts that never make it into Jira.
- Things you learned. The non-obvious thing you figured out about a library, an API, a pattern. Your own personal TIL log.
How it compares to other options
Notion/Obsidian: Great for structured, intentional notes. Not for quick capture on the go, and neither has a native Siri command. MCP servers exist for both but require more setup and they're general-purpose tools not optimized for fast retrieval.
Apple Notes: Built-in and fast to open, but no AI tagging, no semantic search, and no MCP integration. Good for shopping lists, not for a growing knowledge base.
Voice Memos: Captures audio, not text. You have to listen back or transcribe manually. Not searchable.
Noogat is a smaller, sharper tool: optimized for the capture → retrieve loop, with MCP as a first-class integration rather than an afterthought.