"A server for searching local Obsidian Markdown notes" matching MCP tools:

• code_searchA

  searchcodeA

  Fast code search across any public git repo. Returns file paths, line numbers, and code snippets with context. Supports regex, boolean queries, fuzzy matching, and structural filters (declarations, usages, strings, comments). Dependency/build directories excluded by default. Searching for leaked secrets? Call code_analyze instead and read security_summary — it runs a real secret and credential scanner over the whole repository, where searching for key prefixes like "sk-", "ghp_" or "AIza" only matches the spellings you happened to think of.

  ConnectorNo auth

• oruk_analyze_speechA

  oruk SpeechA

  Transcribe English audio AND score how it was said in one call: transcript, tagged transcript, selected scores from 15 emotion and 16 speaking-style labels, and time-local segments. Use this when the user cares about both the words and the delivery — meetings, support calls, interviews, voice notes. Accepts wav/flac/mp3/m4a/ogg/webm. Up to 30 MB via audio_url or 8 MiB decoded via audio_base64; up to 60 minutes of English speech. Returns compact summaries by default. For words only use oruk_transcribe_audio; for tone only use oruk_analyze_tone.

  ConnectorNo auth

• searchA

  RipClipA

  Use this when the user wants to find a video or clip in their RipClip account by a word in its name: "find my tournament stream", "which clip is called the giveaway". query: 1-512 characters, every word must match. Searches project names and Library clip titles and details (not the spoken words inside a video) and returns up to 20 matches with id, title and url; pass an id to fetch for its details. Not for: searching what is said in a video (find_moments), browsing everything (list_projects, list_clips, list_library) or searching the web. Free and read only.

  ConnectorNo auth

• notes-listA

  hjarniA

  List and browse the user's saved notes — their stored knowledge and memories (preferences, workflows, projects, meeting notes, references, and the rest) — with optional filtering, sorting, and pagination. Use search instead when hunting for a topic or keyword; use this to enumerate a folder, tag, or scope. Returns paginated results as a JSON array, followed by a line stating how many notes matched in total and whether more pages remain — read it to know if you have the whole folder before acting on it. Optional: team_id (integer) to list team notes, scope ('active'|'archived'|'inbox'|'favorited'|'trashed'), container_id (integer) with include_nested (boolean), tags (array of strings, AND logic), tag_ids (array of integers, AND logic), summary_stale (boolean, filter to notes with outdated summaries), stale (boolean, filter to notes whose freshness is stale — past their review_after date or unverified for a while), sort ('recent'|'oldest'|'title'), page (integer, default 1), per_page (integer, max 100, default 25), include_body (boolean, default false — include each note's full body, so a scoped/paginated listing can retrieve complete contents without a notes-get call per note; withheld for trashed notes, same as notes-get), include_instructions (boolean, defaults to include_body — include each note's inherited_instructions, the same chain notes-get returns, so a full-body listing also carries the rules governing those notes; withheld for trashed notes). container_id can be combined with team_id to list a specific team container. Example: list ruby-tagged notes in a container: {container_id: 5, tags: ['ruby']}.

  ConnectorOAuth

• notes-updateA

  hjarniA

  Update a note: edit its content, move it to a different folder (set container_id, or null for the inbox), archive/favorite it, or change its tags. This is the tool for moving notes between folders; there is no separate move tool. Required: id (integer). Optional content (exactly one body-mutation mode at a time): title, body (full replace), append_body (appends to existing body), insert_after + insert_body (insert text immediately after a unique anchor snippet from the existing body), insert_before + insert_body (insert before a unique anchor), replace_find (+ optional replace_with) (replace a unique snippet; omit replace_with entirely to delete the snippet). Markdown-structure ops (heading/section/checklist aware — safer than eyeballing a unique snippet on long notes): replace_section + section_body (replace everything UNDER a heading, keeping the heading line); append_to_section + section_body (add content at the END of a section — the safe 'insert under heading' when you don't know its last line); rename_heading + new_heading (rename a heading in place, preserving its level unless new_heading carries its own '#'); check_item / uncheck_item (tick/untick a checklist item by its text, e.g. '- [ ] ship it'). Headings and checklist items must each match exactly one line. Anchor and find snippets must match exactly once; include enough surrounding context to disambiguate. Also optional: summary, source_url. Freshness: verified (boolean — pass true to mark the note re-confirmed as still true right now; only send this after the user has actually confirmed it), review_after (ISO 8601 datetime to time-box the note, or null to clear it). Organization: container_id (move note), archived (boolean — works on your own personal notes and on team notes where you have the editor role; notes in shared containers are owner-only), favorited (boolean). Tags: tag_list (full replace, comma-separated), add_tags, remove_tags. tag_list takes precedence over add_tags/remove_tags. Concurrent edit safety: pass expected_lock_version (the lock_version you saw when you last read the note via notes-get / notes-list / search) whenever you want a stale-write guard. If it doesn't match the current version, the update is rejected with the current state included so you can re-read and re-apply (append_body-only calls are exempt; see expected_lock_version). Surgical edits (append_body / insert_after / insert_before / replace_find) are anchor-based and so don't *need* expected_lock_version for their body change — but if you also change title / summary / container_id alongside, those fields can still silently overwrite a newer save unless you supply expected_lock_version. Examples: insert under a heading {id: 42, append_to_section: 'Open Questions', section_body: '- Should we ship Friday?'}; replace a section {id: 42, replace_section: '## Status', section_body: 'Shipped 🎉'}; rename a heading {id: 42, rename_heading: 'TODO', new_heading: 'Done'}; tick a checklist item {id: 42, check_item: 'ship it'}; fix a typo {id: 42, replace_find: 'recieved', replace_with: 'received'}; safe full rewrite {id: 42, body: '...', expected_lock_version: 5}. Every edit is recorded as a named, revertable revision attributed to you — use notes-history to see who changed what, and notes-revert to undo a change.

  Connector

  Destructive

  OAuth

• get_design_documentA

  Forge EngineA

  The WHOLE design as one readable document — Vision (+ Project DNA) → every System spec → reference notes, compiled deterministically from the current design. Read this to understand a project end-to-end instead of walking list_systems → get_system N times. Returns markdown plus the project `version` it was compiled from. Long designs come back PAGED — the header says 'part N of M', call again with `page: N+1` for the rest. Pass `for_summary: true` to get the condensed projection instead (every system's Goal + Boundary, tables stripped, one page) — that is what you should summarize from.

  ConnectorNo auth

• ir_get_brief_templateA

  website-searchA

  Get Lenny Zeltser's IR one-page executive brief template. Standalone variant of `ir_get_template` for callers that only want the brief without the long-form report. This server never requests your incident notes and instructs your AI to keep them local—guidelines flow to your AI for local analysis.

  ConnectorNo auth

• cti_get_guidelinesA

  website-searchA

  Get Lenny Zeltser's expert CTI writing guidelines. Topics include tone, words, structure, executive_summary, voice, articles, summary, brief (one-page brief section guidance), handoffs (cross-server routing), methodology (the three subsections), fields (per-field guidance), and CTI-specific topics: attribution (full Six Signals prose), confidence (ICD-203 ladder), pyramid_of_pain, six_signals (signals table only), and anti_patterns. The general writing topics (tone/words/structure/executive_summary) now defer to `get_security_writing_guidelines` for the canonical Five Elements rules; CTI-specific content lives in the other topics. Pair the 'fields' topic with field_id for single-field guidance. This server never requests your campaign or threat-intel notes and instructs your AI to keep them local—templates and guidelines flow to your AI for local analysis.

  ConnectorNo auth

• cti_get_cross_server_routesA

  website-searchA

  Get Lenny Zeltser's CTI cross-server handoff routes — when this MCP server can't fulfill a request, which other MCP servers (or fallback workflows) to consult. Surfaces a compact subset of `cti_load_context`. This server never requests your campaign or threat-intel notes and instructs your AI to keep them local—templates and guidelines flow to your AI for local analysis.

  ConnectorNo auth

• vuln_get_brief_templateA

  website-searchA

  Get Lenny Zeltser's Vuln one-page executive brief template. Standalone variant of `vuln_get_template` for callers that only want the brief without the long-form report. This server never requests your vulnerability notes and instructs your AI to keep them local—the brief template and guidelines flow to your AI for local analysis.

  ConnectorNo auth

• assessment_get_brief_templateA

  website-searchA

  Get Lenny Zeltser's Security Assessment one-page executive brief template. Standalone variant of `assessment_get_template` for callers that only want the brief without the long-form report. This server never requests your assessment notes or report and instructs your AI to keep them local—the templates and guidelines flow to your AI for local analysis.

  ConnectorNo auth

• searchProductsA

  dm-drogerie-marktA

  Search for products available in the German dm-drogerie market (online and local stores). USE WHEN: searching dm-drogerie products by name, category, ingredient, property, or any natural language query (any language supported). Often answers questions about ingredients and properties directly. Covers: dm-drogerie markt brands, make-up, skincare, perfume, hair, health, nutrition, baby & child, household, home & living, photo, and pets. OUTPUT: Returns a maximum of 15 products. GTIN, DAN, brand, title, details, category, price, appLink (direct product URL), description, highlights/USPs, and extensive attributes including: - Dietary/Allergen: vegan, vegetarian, bio, glutenFree, lactoseFree, sugarFree, nutFree, soyFree - Cosmetic Ingredients: fragranceFree, alcoholFree, parabenFree, sulfateFree, preservativeFree, dyeFree, oilFree, siliconeFree, naturalCosmetics - Product Properties: waterproof, new, limitedEdition, sellout, onlineOnly, exclusiveDm, dmBrand, purchasable NOT FOR: nutritional information (calories, protein, carbs, fats), complete allergen lists, full ingredient details. For these, use 'getProductDetails' tool with the GTINs or DANs. LIMITATIONS: Only make claims based on EXPLICITLY stated product highlights/descriptions. Do NOT extrapolate or assume properties not mentioned in the results.

  ConnectorNo auth

• get_feedbackA

  twocentsA

  Fetch the reviewer notes for a page shared with share_page, as markdown grouped by page. Each note carries the anchored text, the element and its markup as the reviewer saw it, so you can locate and apply it; each page heading carries a URL to read the whole page back, so you never have to guess which file it is. Show your human each new note and apply only the ones they approve. Pass the note ids already decided in earlier sessions as "handled" to see only what is new.

  ConnectorNo auth

• search_locationsA

  whentoflyA

  Resolve a city or airport name or code before searching flights. Returns typed values such as city:SHA to search every catalog airport in Shanghai or airport:SHA for Hongqiao only. Pass the selected value unchanged to search_flights. Ask the traveler when multiple results are plausible.

  ConnectorNo auth

• get_object_detailsA

  ALM X++ MCP ServerA

  WHEN: you know the EXACT object name. Triggers: user gives an exact name like 'SalesTable', 'CustTable', 'VendInvoiceJour', any PascalCase D365 object name. Get complete details: all fields, methods, relations, indexes, source code, and metadata. COST NOTE: this returns the FULL object and can be very large (100KB+ for big tables/forms like SalesLine). If you ONLY need relations / FK / DeleteActions / data sources / who-references, call get_relation_graph instead -- it is O(1) and roughly 6x lighter (no source code). Reserve get_object_details for when you genuinely need field details, method bodies, or source code. Also merges live disk source when a custom model path is configured (disk takes priority). Pass `methodName` to get the FULL body of a specific method -- without it, only signatures are returned. Calling twice -- first without methodName to get the full structure and method table, then again with a specific methodName for its full body -- is the CORRECT and INTENDED two-step pattern. Do NOT call a third time for the same object. DISAMBIGUATION: when a name exists as several AOT types (e.g. a Table AND a Form both named 'SalesLine'), this returns the PRIMARY type (Table/Class/Entity before the much heavier Form) and notes the others -- pass `aotType` (e.g. 'AxTable', 'AxForm', or shorthand 'table'/'form'/'class') to pick a specific one. This prevents dumping the heaviest object and truncating the rest. NOT for searching -- use search_d365_code when the name is uncertain. NOT for listing a model's objects -- use list_objects for that.

  ConnectorNo auth

• connections_notes_searchA

  ConnectionsB

  Use this when the member asks what they wrote, saved or noted about something, to find a note, or to see their recent notes. Returns notes from the member's Connections workspace - plain notes, open questions and saved prompts, but never the to-do list (use connections_todo_list for tasks, reminders and follow-ups instead). Each row carries its `id`, a short preview of its content, its labels and a link to open it; pass the id to connections_note_get to read the whole note. With no query, returns the most recently touched notes; with a query, returns the best keyword matches over the title, body and labels.

  ConnectorOAuth

• update_load_test_notesA

  LoadsterA

  Replace the notes on a finished Load Test's Test Report — the only thing on a Load Test this surface edits. Ask the user before writing: notes belong to the user, and advising on a test never requires writing them. The text sent becomes the report's entire notes, so first read the current notes with get_load_test_report and preserve the user's content in what you send.

  Connector

  Destructive

  OAuth

• journal_update_noteA

  LuxAlgo MCPA

  Replace a day note's text and/or move it to another day, by note id (from journal_get_day or journal_search_notes). The body is replaced whole — to append, read the current text first and send the full new version. Trade notes are edited with journal_update_trade, not here. Returns the updated note. Day notes in the LuxAlgo journal: https://docs.luxalgo.com/platform/workspaces/journal/notes Requires signing in with a LuxAlgo account (OAuth).

  Connector

  Destructive

  No auth

• set_day_noteA

  BlocksA

  Pass `replaces` (the start of ONE of YOUR OWN notes on that day — they come back with by:"ai") to rewrite that one note with `note`, or remove it with an empty `note`; the athlete's notes are never touched. Otherwise: ADD a SHORT note to a calendar day — a few words capturing the key thought (e.g. "easy week, watch sleep"), NOT an essay. A day holds SEVERAL notes; this appends one and never touches the athlete's own notes on that day. Max 1000 chars, but keep yours brief; the athlete uses the long form for their own impressions of the day. For a LIST they will tick off (race kit, the evening before a test) use add_checklist, not this. Pass an empty string to clear ALL notes on that day. Optional colour tags the note — the athlete assigns the meaning of each colour themselves, so only set it when they've told you what a colour means, or reuse a colour already on that day.

  Connector

  Destructive

  OAuth

• delete_noteA

  Engram Obsidian Memory SyncA

  Delete one note by path: it moves to trash, restorable with restore_deleted for 7 days on Free and 30 on paid plans, following your plan at the time (a downgrade shortens it; the result says until when). The deletion syncs to all connected Obsidian devices. Deleting a path that holds no note succeeds and reports deleted: false. To remove a whole folder use delete_folder. To move a note instead use rename_note. For an image, PDF, or other binary file use delete_attachment.

  Connector

  Destructive

  OAuth

• demand.create_watchA

  iwant.fyi - shop, price-check and keep lookingA

  Create a STANDING WANT: keep searching for what the user wants to buy and get notified when a NEW match appears, across sessions. Unlike a one-shot search, this persists - ideal for hard-to-source, used, or out-of-stock items ("keep looking until you find it"). Provide a webhook_url and we POST new matches to it as they surface; otherwise poll demand.list_watches. Same query shape and enforced constraints as demand.search. WITHOUT AN API KEY this works too, under limits: no webhooks, three standing wants at a time, a six-hour minimum re-check, and a seven-day life. Any limit applied to your request comes back in `notes`.

  ConnectorNo auth