Blinq

Get one Blinq card by workspace_id and card_id: name, job title, company, department, the public blinq.me sharing URL, a QR code that encodes it, and the contact fields shown on the card (emails, phone numbers, websites, socials, addresses). - The workspace must be your personal workspace or a team workspace you own or administer; plain team membership grants no card access - Returns card_not_found when the card does not exist in that workspace or the workspace is not accessible; existence elsewhere is never revealed - Contact fields are grouped by kind, preserving card order within each group; card styling and images are rendered in the interactive view but not part of the output <examples> get_card(workspace_id="workspace-id", card_id="card-id") </examples> <hints> - Use list_cards to discover card IDs (as card_id) and list_workspaces for workspace IDs (as workspace_id). - The url field is the shareable public link for the card; share it as-is. - The qr_code field is a PNG data URI encoding that link; render or embed it as-is. </hints>

get_card

Get details for a specific Blinq contact by contact_id — name, company, job title, emails, phone numbers, URLs, addresses, tags, notes, and meeting overview. Fetches a personal or business contact, optionally scoped to a workspace. - If workspace_id is provided, the contact must match that workspace type: personal workspaces return personal contacts, business (team) workspaces return business contacts - Omitting workspace_id scans your personal workspace then each team workspace in turn; pass workspace_id (from a list_contacts row or list_workspaces) for a single scoped lookup - Returns workspace_not_found when workspace_id is not one of your accessible workspaces; use list_workspaces to find valid workspace IDs - Returns no_individual_workspace when no personal workspace is available; use list_workspaces to inspect accessible workspaces - Returns contact_not_found when the contact is not found in the requested scope - ai_notetaker_notes are summary metadata only; get_note transcript fields are populated only once the related voice note or phone call completes <examples> get_contact(contact_id="contact-id") get_contact(contact_id="contact-id", workspace_id="workspace-id") </examples> <hints> - Use list_contacts to discover contact IDs (as contact_id), then call this tool for full detail - Use list_workspaces when the user needs to choose a workspace (as workspace_id) - `text_notes` are the contact's saved text notes. - `ai_notetaker_notes` are AI-notetaker note summaries linked to this contact; call get_note with a returned id (as note_id) for the full transcript (team members' notes require workspace admin/owner rights), use search_notes for keyword note search, query_notes for synthesis, and list_notes to browse all notetaker notes. </hints>

get_contact

Get full detail for one of your AI notetaker notes (or an admin/owner-accessible team note) by note_id. Returns full content/AI summary, transcript, linked contacts, source, and call phone numbers. - Returns your own notes, plus team members' notes when you are an admin or owner of that workspace; a note that does not exist or that you cannot access returns note_not_found - `type` selects which detail block is populated: a voice_note note fills `voice_note` (phone_call null) and vice versa; the transcript lives in the populated block - Transcript fields are populated only once the related voice note or phone call is completed - Very long transcripts may be clipped to fit the response budget; when this happens `truncated` is true — open `share_url` (or the note in Blinq) for the full transcript <examples> get_note(note_id="note-id") </examples> <hints> - Use list_notes or search_notes (or a query_notes citation) to discover note ids, then call this tool for full detail. - Use query_notes to ask a question across notes, or get_contact with a linked contact id (as contact_id) for full contact detail. </hints>

get_note

List the Blinq cards in one workspace: a lightweight summary per card with its public blinq.me sharing URL. For a single known card, call get_card with a returned id to fetch full detail, including its QR code. - workspace_id is required and must be your personal workspace or a team workspace you own or administer; plain team membership returns workspace_not_found - Deleted cards, drafts, and card templates are excluded; sorted by creation date, newest first: an empty list is authoritative, not an error to retry - Capped at `limit` per page. When `has_more` is true, pass `next_cursor` as `cursor`; `total_count` is on the first page only, `null` after <examples> list_cards(workspace_id="workspace-id") list_cards(workspace_id="workspace-id", cursor="cursor-from-previous-page") </examples> <hints> - Use list_workspaces first to get workspace IDs (as workspace_id). - The url field on each card is its shareable public link; share it as-is. </hints>

list_cards

List Blinq contacts across the user's personal workspace and team workspaces they own or admin — a lightweight summary per contact. For full detail, call get_contact with a returned id. - Business contacts appear only for business workspaces where you are an owner or admin, so some workspaces may be absent - Sorted by creation date, newest first; an empty list means no contacts match — authoritative, not an error to retry - Filter with search (name/job title/company/the contact's text notes), date_from/date_to, or workspace_ids; capped at `limit` per page — lower `limit` or add filters to narrow. When `has_more` is true, pass `next_cursor` as `cursor`; `total_count` is on the first page only, `null` after <examples> list_contacts(search="acme") list_contacts(date_from="2024-01-01T00:00:00Z", date_to="2024-12-31T23:59:59Z") </examples> <hints> - Use list_workspaces to get workspace IDs before scoping with workspace_ids, and get_contact to fetch full detail for a returned contact. - search matches the contact's own text notes, not AI notetaker notes — for notetaker note content use query_notes (questions) or search_notes (keyword). </hints>

list_contacts

List the authenticated user's AI notetaker notes, newest first — a lightweight summary per note. For full content or transcripts, call get_note with a returned id. - Lists only your own notes; team members' notes (reachable by id via get_note when you admin/own that workspace) are NOT listed here - Summaries only (full content/transcripts live in get_note); an empty list means you have no notes — authoritative, not an error to retry - Capped at `limit` per page and sorted by `order_by` (keep it stable across pages). When `has_more` is true, pass `next_cursor` as `cursor`; `total_count` is on the first page only, `null` after <examples> list_notes() list_notes(order_by="updated_at", limit=50) </examples> <hints> - To find specific notes rather than browse, use search_notes (keyword) or query_notes (a synthesised, cited answer); returned note ids can be passed to query_notes(note_ids=[…]). - Use get_note with a note id (as note_id) for full content/transcripts, or get_contact with a linked contact id (as contact_id) for full contact detail. </hints>

list_notes

List the Blinq workspaces the authenticated user can access. Returns every accessible workspace (id, name, type, role) in one call — no pagination or filters. An empty list authoritatively means none. Pass a returned workspace id to get_contact or list_contacts to scope a request to that workspace. Pass a returned workspace id to list_cards or get_card for lightweight card details and sharing links. Business-contact and business-card access require an owner or admin role. Use whoami to confirm the signed-in account.

list_workspaces

Answer a natural-language question — or summarise/recap — from the authenticated user's AI notetaker notes, returning a synthesised written answer with inline [n] citations to the source notes. Returns a written, cited answer rather than a list of notes, and is slower than search_notes. Prefer it for open-ended questions about note content ("what did we decide about pricing?", "summarise everything about X", "catch me up on the Acme account", "what are my action items"). Use search_notes when you only need a list of matching notes. - Uses only the authenticated user's own notes, and answers from note titles and AI summaries (not raw transcripts), so a detail absent from the summary may be missing - Cites sources inline as [n] markers (1-based) mapping to the returned `citations` array; returns one answer plus citations, not a paginated list - Says so when the notes lack the information — it will not invent an answer - Pass `note_ids` (e.g. from search_notes or list_notes) to answer strictly from specific notes <examples> query_notes(query="what did we agree on about the timeline?") query_notes(query="summarise my action items from the Acme calls", note_ids=["note_123", "note_456"]) </examples> <hints> - Preserve the [n] markers and surface `citations` (title + share_url) so the user can open the sources. - Use search_notes for raw keyword matches, get_note with a citation's id (as note_id) for full detail, or list_notes to browse chronologically. </hints>

query_notes

Search the authenticated user's AI notetaker notes by keyword, ranked by relevance — returns matching notes with their AI summary (content), so you can often answer without a follow-up call. For full transcripts, call get_note with a returned id. - Searches only your own notes; team members' notes (reachable by id via get_note when you admin/own that workspace) are NOT searched here - Matches note titles and AI summaries, not raw transcripts, so a detail absent from the summary may not match - Ordered by relevance, capped at `limit`; returns the top matches only and is not paginated — narrow the query to surface different notes. An empty list means nothing matched - In a large result set, long summaries may be clipped to fit and `truncated` is set — call get_note for the full text <examples> search_notes(query="acme pricing") search_notes(query="onboarding feedback", limit=5) </examples> <hints> - Use query_notes for a synthesised, cited answer instead of a list; returned note ids can be passed to query_notes(note_ids=[…]). - Use get_note with a note id (as note_id) for full summary/transcript/call details, list_notes to browse chronologically, or get_contact with a linked contact id (as contact_id) for full contact detail. </hints>

search_notes

Return the authenticated Blinq user (user_id and email) for the current MCP session. Use it to confirm which account the session is acting as before scoping other calls. Use list_workspaces to see the workspaces this user can access.

whoami