"Tools or methods for keeping track of conversations" matching MCP tools:

• list_categories

  AgentCrush

  List the 4 AgentCrush agent categories with tracked + evidence-ranked counts and current methodology versions. Use this for market-level discovery — what kinds of agents does AgentCrush track and how many of each?

  Connector

• glim_github_search

  glim.sh

  Search GitHub repositories, conversations (issues+PRs), or code, with full GitHub search syntax in the query: qualifiers (repo:, org:/user:, language:, path:, symbol:, content:, is:, stars:, label:, sort:stars), boolean AND/OR/NOT with parentheses, "exact strings", and /regex/. kind='repos': MINIMAL distinctive keywords - the project/library name only ('rtk', 'react query'); every extra word must ALL match and buries the canonical repo - filter with qualifiers, not prose. kind='code': ONE literal code pattern as it appears in files ('useState('), an "exact string", a /regex/, or symbol:name to find definitions, across 2.8M+ public repos; narrow with repo:/language:/path:. Not supported in code search: license:, enterprise:, is:vendored, is:generated. kind='conversations': returns compact previews - use glim_github_get for full content; sort: REPLACES relevance ranking (words match anywhere incl. comments), omit it for best matches. Set repo='owner/name' to scope to one repository (works with any kind; with repos it routes to conversations). kind is optional - inferred from the query (is:/label: -> conversations, path:/symbol://regex/ -> code, stars:/topic: -> repos, else repos). Returns compact text by default; pass format='json' for full structured data.

  Connector

• perspective_list_conversations

  Perspective AI

  Lists conversations for a perspective, with optional filters by status, trust score range, and date range. Each item includes conversation_id, status, structured-output fields, trust score, and a transcript URL. Behavior: - Read-only. - Errors when the perspective is not found or you do not have access. - Pass nextCursor back as cursor for the next page. Empty results return an empty array. - This list view does NOT include transcripts or summaries — metadata only. - date_from / date_to must be ISO 8601 strings (e.g. "2026-04-28T00:00:00Z"). Malformed dates are rejected at the schema level rather than silently treated as no-filter. When to use this tool: - Picking specific conversations by status / trust / date before deep-diving. - Showing the user a browsable list of responses. When NOT to use this tool: - Need transcript or summary for one conversation — use perspective_get_conversation. - Bulk analysis across many conversations — use perspective_get_conversations (batch with optional transcripts). - Aggregate counts/rates only — use perspective_get_stats.

  Connector

• find_tracks_by_bpm

  FreqBlog Music Metadata

  Find catalog tracks near a target tempo. Returns tracks whose BPM is within +/-`tolerance` of `bpm`, ordered by closeness then popularity — useful for DJ set planning, workout playlists, or tempo-matching. Each returned track carries full audio features. To also constrain by musical key, combine with find_tracks_by_key.

  Connector

• truncate_to_tokens

  IA-QA — 130+ QA & Dev Tools for AI Agents

  Truncate text to at most N tokens (cl100k_base: ~4 chars/token) to avoid exceeding an LLM context window. Optionally keeps the end of the text instead of the start (useful for keeping recent conversation history). Reports whether truncation occurred and the estimated token count.

  Connector

• get_audio_features

  FreqBlog Music Metadata

  Get audio features for ONE track — BPM, musical key (name + Camelot + Open Key), energy, danceability, valence, acousticness, instrumentalness, liveness, speechiness, loudness, mood, mood_vector, genre, time signature, duration and more. This is the drop-in replacement for Spotify's deprecated /audio-features endpoint. Provide EXACTLY ONE identifier: - `track` (optionally with `artist`) — e.g. track="Blinding Lights", artist="The Weeknd". - `isrc` — e.g. "USUM71900001". - `mbid` — a MusicBrainz recording UUID. - `spotify_id` — a Spotify track ID, URI, or URL. Returns a JSON object of features. Some feature fields may be null for tracks resolved via the fallback catalogs (only audio-derived values are present for fully analysed tracks). If a track name is not yet in the catalog, the API queues an on-demand analysis and this tool reports that it is queued — retry in ~30s-2min. If you only have a fuzzy or partial name, call search_catalog first to find the exact track.

  Connector

• list_services

  Parallax Ventures

  List Parallax’s services with real pricing. Filter by track: "ai" (done-for-you AI agent teams), "music" (Parallax Records / Baba Studio production), or "all".

  Connector

• report_get

  Kash.click

  Download a synthetic HTML sales report for a given period. Period logic: omit all date fields to get yesterday's report; provide y only for a full-year report; y + m for a full-month report; y + m + d for a specific day. Returns an HTML summary including total revenue, number of orders, breakdown by department, VAT summary, and payment methods.

  Connector

• billing.get_portal

  Admin Substitute

  Get a Stripe Billing Portal URL for the human to manage their subscription — update payment methods, view invoices, change plans, or cancel. Requires an existing Stripe subscription.

  Connector

• compare_validation_approaches

  Demand Discovery AI

  Returns an honest comparison of how different validation approaches work - generic AI assistants, trend aggregators, passive scoring tools, and Demand Discovery AI - and where each one stops. Use when a user is evaluating approaches, asking "what makes Demand Discovery different?", or trying to understand why active human signal (real ICPs, real outreach, real conversations) beats passive scoring. Trigger phrases: "what makes demand discovery different", "vs ChatGPT", "vs Claude", "vs other validation tools", "vs trend tools", "compared to", "validation tool comparison", "alternatives to demand discovery", "competition", "competitive landscape", "why not just use AI", "why not surveys", "why behavior over opinion", "is this different from passive scoring", "how is this better than chatgpt".

  Connector

• search_threads

  DialogBrain

  Find or list chat threads/conversations — by topic, participant, unread/unanswered status, or recency. Omit `query` to list threads by filter. For message content use search.messages; for files use search.files. `since` filters by recency and pairs with only_unread / only_unanswered.

  Connector

• list_tasks

  NeedHuman

  Use when you have lost track of a task_id or want to review your past human task requests. Returns all tasks you have submitted, newest first: id, status, description, result, and timestamps.

  Connector

• get_trade_signal

  AlgoVault — Crypto Quant Trade Calls

  Returns a composite verdict — BUY SELL HOLD trade call with confidence and market regime — for one crypto or tokenized-stock perpetual futures. One asset only; for a whole-market scan use scan_trade_calls, for US stocks use get_equity_call. Read-only: reads live exchange APIs, no orders. Verified track record, on-chain verified merkle anchor. [ALIAS] This tool is an alias of get_trade_call — same behavior, kept for backward compatibility.

  Connector

• lookup_paper

  BGPT - Scientific Paper Search

  Look up a single paper by its DOI. Args: doi: The DOI of the paper (e.g. "10.1038/s41586-024-07386-0"). api_key: Optional: Your Stripe subscription ID for paid access. Get one at https://bgpt.pro/mcp Returns: Paper with title, DOI, Raw Data, methods, results, quality scores, and 25+ metadata fields — or an error if not found. Costs $0.02 if found, free if not.

  Connector

• perspective_get_conversation

  Perspective AI

  Returns the full record for a single conversation: rendered transcript, summary, trust assessment with per-dimension scores and recommendations, structured-output fields, voice-message snippet URLs, duration, and timestamps. Behavior: - Read-only. - Errors when the conversation does not exist, belongs to a different workspace, or the id is malformed. - Transcript joins participant and agent turns with role labels. - voice_snippets are present only for voice-mode messages. When to use this tool: - Deep-dive on one conversation: full transcript, why trust was low, what was said. - Pulling exact quotes or audio links for a single response. When NOT to use this tool: - Browsing many conversations — use perspective_list_conversations. - Bulk analysis or thematic patterns across many conversations — use perspective_get_conversations (batch, token-efficient). - Aggregate stats only — use perspective_get_stats.

  Connector

• perspective_get_stats

  Perspective AI

  Returns aggregate conversation counts and breakdowns for a perspective over a chosen window (7d, 30d, 90d, or all). Includes totals, completion rate, average duration, plus distributions by period, trust score band, and status. Behavior: - Read-only. - Errors when the perspective is not found or you do not have access. - total_conversations / completed / completion_rate cover real (NORMAL mode) production conversations only. preview_count is reported separately so you can see how much test traffic the perspective received from /share?mode=preview links. - avg_duration_seconds is computed across the requested period. - perspective_get's stats use the same definition — the two tools agree on the headline number. When to use this tool: - Sizing the dataset before pulling conversations in batches with perspective_get_conversations. - Quick health check: completion rate, volume by period, trust distribution. When NOT to use this tool: - Reading individual transcripts or summaries — use perspective_list_conversations or perspective_get_conversation. - Inspecting setup and outline — use perspective_get.

  Connector

• perspective_get_embed_options

  Perspective AI

  Returns the deployment artifacts for a perspective: the share_url and direct_url for outreach plus ready-to-paste embed snippets (fullpage, widget, popup, slider, float, card) and an SDK reference (script URL, events, URL/brand/theme params, JS API methods, callbacks). Behavior: - Read-only. - Errors when the perspective is not found or you do not have access. - URLs are stable per perspective. Conversations started from these embeds count toward the workspace's quota (preview conversations do not — see perspective_get_preview_link). - Use the snippet returned for that specific perspective rather than hand-rolling URLs. - share_url / direct_url accept these URL params: name, email, returnUrl, plus arbitrary tracking keys (source, campaign, etc.). When to use this tool: - Deploying a perspective to a real site, email, or app surface. - Generating SDK integration code (Next.js layout, raw HTML, popup trigger button, etc.). - Looking up event names or URL parameters the embed accepts. When NOT to use this tool: - Internal smoke testing — use perspective_get_preview_link (preview conversations don't count toward quota). - Inspecting outline / setup — use perspective_get. Typical flow: 1. perspective_create → design 2. perspective_get_preview_link → test 3. perspective_update → refine 4. perspective_get_embed_options → deploy 5. automation_create → (form / lead-capture contexts) wire conversation data to a CRM or backend Snippet placement, by embed type: - Popup / Slider / Float: the script goes before `</body>` in HTML, or in `_app.tsx` / `layout.tsx` for React/Next.js. - Widget: the div marks where the widget renders. - Fullpage: a dedicated page or iframe container. - Card: a preview link for landing pages or emails. For form / lead-capture perspectives, automation_create can forward each completed conversation to a CRM, database, or notification channel. Examples: - Optional URL params on the share link: `email` (pre-fills participant email), `returnUrl` (redirect after the conversation completes), and arbitrary `key=value` pairs for tracking (e.g. `source=email`, `campaign=q4-launch`, `user_id=...`). Embed snippets accept additional appearance params (brand colors, theme) — see the `sdk.parameters` section in the response. - Each perspective has unique URLs — always use the URL returned for that specific perspective.

  Connector

• perspective_get_preview_link

  Perspective AI

  Returns a shareable URL that opens the perspective in preview mode, so you (or a teammate) can have a sample conversation with it before deploying. Behavior: - Read-only. The same stable preview URL every time for a given perspective; the link does not expire. - Conversations started from this URL are preview conversations and do NOT count toward the workspace's quota. - Anyone with the link can start a preview conversation, even unauthenticated — treat as semi-public. When to use this tool: - After perspective_create or perspective_update, to manually verify the perspective's behavior before going live. - To share a preview link with a teammate for review. When NOT to use this tool: - For production deployment — use perspective_get_embed_options, which returns embed snippets and a public share link whose conversations count toward quota. - To inspect existing real conversations — use perspective_list_conversations / perspective_get_conversation. Typical flow: 1. perspective_create → design 2. perspective_get_preview_link → test 3. perspective_update → refine 4. perspective_get_embed_options → deploy

  Connector

• assemble_demo_video

  TestMyVibes

  Stitches video clips + voiceover narration into a single MP4 published to Spaces. Each segment is one of: (a) videoUrl + narrationText (voiceover replaces video's audio track), (b) narrationText only (generates a brand-color title card sized to narration length), (c) videoUrl + audioUrl (drops in a pre-baked audio track). Returns a 24h signed URL to the final MP4. Use this for marketplace catalog submissions, tutorial videos, or any time you'd otherwise screen-record + iMovie by hand. Charged on success only; failed runs are free.

  Connector

• list_rooms

  roomcomm

  List public Roomcomm rooms for discovery. Use when the owner asks you to find a room to join, or when you want to discover ongoing conversations on a topic. Returns {rooms: [{uuid, description, message_count, last_activity_at}], total}. Args: sort: "active" (most recent activity first) or "new" (creation order). limit: How many rooms to return (max 200). offset: Pagination offset. Example: list_rooms() to see what's happening right now.

  Connector