MCP App Store
by KeenEthics
Guidepoint icon

Guidepoint MCP Server for Claude and ChatGPT

By Guidepoint

Overview

Embed trusted expert insights directly into your research and decision making workflows in real-time. Powered by Guidepoint's in-house team of former investment analysts, we combine institutional-grade quality with the volume needed for decision-critical work. Claude pulls verbatim excerpts from 100,000+ compliance-reviewed expert interview transcripts — with every source transcript linked inline for verifiable, trusted data.

How to connect

  1. Claude: Open the Guidepoint listing in the Claude connectors directory and choose Connect. Claude listing Guidepoint exposes 1 tool here.
  2. ChatGPT: Open the Guidepoint listing in the ChatGPT app directory and choose Connect. ChatGPT listing Guidepoint exposes 17 tools here.

Tools

cancel_registration

ChatGPT
Cancel the authenticated subscription client's existing registration for one upcoming Guidepoint event so they can manage their schedule inline in the AI conversation without switching to GP360. Pre-flight When no event_id is available in the current conversation context (e.g. the user said "cancel my Tesla registration" without a preceding read result), call get_user_registrations first to obtain a real event_id and present the matching options to the user. get_user_registrations is preferred over search_events as the id source — it returns only events the user is actually registered for, while search_events does not verify registration status and can surface events the user has not registered for (passing that id here returns NOT_REGISTERED). Fall back to search_events only when get_user_registrations returns nothing matching the user's phrasing — which usually means the user asked to cancel something they aren't registered for. Hand-typed, guessed, or fabricated event_id values are unsupported. Calling this tool with a fabricated id returns NOT_REGISTERED (or EVENT_LOOKUP_FAILED when the id isn't a valid Guidepoint event at all). When to route away from this tool - the user is asking about their calendar / registrations — use get_user_registrations. - the user is browsing the general catalogue — use search_events. - the user asks to register — use register_event. - the user asks to withdraw a private advisor consultation request (identified by requestId + advisorId, not an event_id) — route to cancel_requested_consultation on the network-mcp surface. Split rule: event_id cancellation uses cancel_registration; requestId plus advisorId withdrawal uses cancel_requested_consultation. When the ask is a generic "cancel my Guidepoint call" with no id-shape signal, ask the user whether they mean an event registration or an advisor consultation before choosing. Pre-call confirmation gate Confirmation gate for cancel_registration: 1. Present the event's title, date, event_type, and event advisors (name, job_title, company when disclosed) to the user. 2. Ask for explicit affirmative confirmation (e.g. "Yes, cancel my registration", "Go ahead"). Mere acknowledgment of the event (e.g. "That's the one") is not confirmation. 3. Wait for a clear affirmative before invoking the tool with confirmed=true. The confirmation gate applies to the destructive write path only — confirmed=true requires the three steps above. A confirmed=false (or omitted) call is the documented preview shape and is safe to invoke without prior user consent: it fires no upstream write and returns the CONFIRMATION_REQUIRED envelope carrying the event metadata the caller needs to run steps 1–2 with the user. The non-conforming shape is calling cancel_registration with confirmed=true before an affirmative from the user has reached this side of the wire. Cancellation is irreversible from this tool — re-registering is a separate register_event call and may not always succeed (event may fill up or move into the 24-hour lock-out window). When the event metadata is not already at hand, call get_user_registrations first and present its title/date to the user before asking for confirmation. Response envelope render This is a WRITE action — the response is a success/error envelope. The confirmation line is the minimum required output; the response may additionally render the full event card (title Markdown link, metadata line, date/time, description, event advisors, cost when > 0, CTA row per the read-tool card structure) so the user sees the full context of the event they just acted on. Inline emoji, SVG markup, and image markup are permitted (widget-capable clients pass them through to their renderer; non-widget clients render as raw Markdown/HTML). Success envelope — surface a confirmation with the event title and date. A one-line confirmation is fine when the caller just wants the outcome; a full event card is fine when the user wants full context. Widget-capable cli…

cancel_requested_consultation

ChatGPT
Withdraw a phone consultation the client requested with one advisor (requestId + advisorId). Triggers: "cancel the consultation with [advisor name]," "withdraw my call request." Eligibility: only statusInfo.name "selected" with requestedConsultType "call" (get_request_advisors); anything else needs their Project Manager (PM) — the advisorId field lists each case. The service refuses this action on a Closed request. It cannot be un-cancelled here — getting it back needs a fresh select_advisor request. confirmed previews it; nothing is written until true. On success: status "submitted"; re-read get_request_advisors for the new state. Needs a requestId then an advisorId from prior calls. Not for declining an advisor (reject_advisor) or requesting one (select_advisor); a curated Guidepoint event registration is cancelled through cancel_registration, by event_id. Errors: isError, a plain message, and _meta.error_code/retryable — relay the message, never invent a cause; retry once only when retryable is true.

get_advisor_screeners

ChatGPT
The full screener Q&A for one advisor on a request — the pre-consultation vetting questionnaire they answered, already on file. Read-only: it does not contact the advisor or notify the PM. Triggers: "show me this advisor's screener answers," "what did they say about [topic] in screening." Three sources of what an advisor said, not interchangeable: screeners are what they submitted before the consultation; a whole call is get_meeting_transcript; snippets across calls search_my_network_excerpts; the wider library search_library. If the ask does not say which, ask the client. Needs a requestId (get_requests or search_requests) and advisorId (get_request_advisors). Closed requests are returned too; no write tool acts on one. Related: select_advisor to request availability or screening; search_request_advisors_by_screeners to find advisors by screener content. Errors: isError, a plain message, and _meta.error_code/retryable — relay the message, never invent a cause; retry once only when retryable is true. An empty result is not an error.

get_meeting_transcript

ChatGPT
One meeting transcript in full, as speaker-attributed turns. Use when the ask names the transcript or the call, or needs the whole conversation not a quoted line. Triggers: "pull my transcript for [advisor]", "summarise my [angle] transcripts", consensus/outlier questions. Not for a phrase across many calls, nor a direct question a quoted Q&A pair answers ("what did they say about pricing?") even for one meeting — that is search_my_network_excerpts; never summarise from its snippets. Pre-call answers: get_advisor_screeners. If unclear, ask. Needs a transcriptId — only search_meetings returns it, where transcriptionStatus is "completed". From an excerpt: search_meetings on its request_id, match the meeting_id, take its transcriptId. One transcript per call; a cohort is one call per row. Attribute by speakerName. Summarise unless asked to display the full transcript. Errors: isError, a plain message, and _meta.error_code/retryable — relay the message, never invent a cause; retry once only when retryable is true. An empty result is not an error.

get_request_advisors

ChatGPT
Retrieve the advisors on a specific request or project. Returns every status by default (review, selected, scheduled, not_interested, completed). Triggers: "who are the advisors on this project," "who is on the [angle] angle." Needs a requestId from get_requests or search_requests. Closed requests are returned too; no write tool acts on one. For a status-scoped question pass the status filter rather than fetching everything; each row carries statusInfo.name, and statusInfo.details the billing/call metadata for completed calls. Every row carries angles — the step that turns a cohort into people: keep the advisors on the angle, then search_meetings once per advisor id. For screener responses use search_request_advisors_by_screeners. To act: select_advisor, instant_book_advisor, reject_advisor, cancel_requested_consultation. Errors: isError, a plain message, and _meta.error_code/retryable — relay the message, never invent a cause; retry once only when retryable is true. An empty result is not an error.

get_requests

ChatGPT
Retrieve a paginated list of the authenticated client's own expert network requests (also called projects), unfiltered. Scoped to that one client — no client or user argument, so "my requests" and "all requests" mean the same set. Use when browsing, or when the right filter values aren't known yet. Triggers: "show me all projects," "list my requests." One page per call, no total: hasMore true means another page probably exists, so page on until it is false before quoting a count or calling a list complete. Rows come in no guaranteed order — position carries no recency or rank. Closed requests are returned too; no write tool acts on one. For anything filtered — status ("what engagements are open") or cohort ("what do formers think") — use search_requests (title, type, status, transcripts-enabled, angle, creation date). Errors: isError, a plain message, and _meta.error_code/retryable — relay the message, never invent a cause; retry once only when retryable is true. An empty result is not an error.

get_user_registrations

ChatGPT
Response shape. Each registration renders as its own multi-line card block — not as a Markdown table row, a numbered list, or a compact one-line prose row. A table with one row per registration is a regression: it hides the description line, event-advisor line, and CTA row, and breaks the widget pattern-match on client renderers. Section headers group the cards and carry the section's count as a trailing suffix (## Upcoming Registrations — 7, ## Pending Compliance — 2, ## Past Registrations — 20); the count comes from each section's count field on the envelope. Cards inside a section render in the array order the sidecar returned. Full card contract is in ## Card contents further down. CTA labels this tool emits — a two-value subset of the shared card-component vocabulary. The shared card component (used by both search_events and this tool) supports four CTA labels: Register, Cancel registration, Request, View in Guidepoint. `get_user_registrations` emits only `Cancel registration` or `View in Guidepoint` from that set — every event returned by this tool has user_registration_status: "registered" (or is a pending-compliance PreOrder), so Register and Request never fit. The sidecar resolves the correct label per event and emits it as `cta_label` on the event object — render cta_label verbatim rather than re-deriving it from registration_state, event_is_past, and cu_cost. The priority the sidecar applies (first match wins, top to bottom): | | Condition | cta_label | |---|---|---| | 1 | event_is_past == true | View in Guidepoint | | 2 | registration_state == "pending_compliance" | View in Guidepoint | | 3 | upcoming confirmed registration | Cancel registration | Full per-row button templates live in ## CTA logic further down. The label vocabulary is closed: View event, View transcript, View, Attend, Join, Open in Guidepoint, Details, Learn more, or any variant outside the two-value subset above is non-conforming. Actionable CTAs (Cancel registration) render as two lines: a Markdown link [Cancel registration](event_url) on line 1, then an italic prompt hint Or copy this prompt: *"…"* on line 2. Both lines are part of the card — the prompt-hint line gives the reader a copy-paste form of the CTA text and is carried on every actionable card. View in Guidepoint is a single Markdown link line with no italic hint. Actionable CTA — the two-line form in full. Every actionable CTA carries a two-line form: the Markdown link on line 1, the italic prompt hint on line 2. The canonical shape for a Cancel registration CTA on a registered upcoming event is two physical lines: [Cancel registration](event_url) Or copy this prompt: "Cancel my registration for [title] on [date]" Non-conforming card shapes to avoid: - Card ending on the bare word Cancel registration (no link, no hint). Conforming shape: the two-line form above. - Card ending on [Cancel registration](event_url) alone (link but no italic prompt-hint line below). Conforming shape: append the italic hint line. - Card with the prompt-hint line merged into the link line. Conforming shape: the hint sits on its own physical line, so widget renderers can keep it visually distinct from the button. Both lines are emitted on every actionable card. The widget layer decides whether to display the hint as caption text or fold it behind a button; the response carries both. Section-count line — the closing form. Sections use the header form ## Upcoming Registrations — N. Two independent envelope conditions can add a trailer, and the two conditions render different trailers — they do NOT compose into one: - Truncation trailer — fires only when total_events > returned (the visible list was truncated by limit). Trailer text is exactly Showing N of M registrations. and nothing else. - Degraded-enrichment notice — fires only when enrichment_degraded_count > 0. Rendered as a separate one-line notice ('N registrations had incomplete details and are shown with limited information.'…

instant_book_advisor

ChatGPT
Book a private 1:1 phone consultation onto one advisor's calendar, with no Project Manager (PM) step. Keyed by requestId + advisorId; a curated Guidepoint event registers by event_id through register_event instead. Triggers: "book a call with [advisor name]," "schedule them for Tuesday at 10." Eligibility: only when instantBook.canInstantBook is true (get_request_advisors); when false use select_advisor. The service refuses this action on a Closed request. timeSlot: one 15/30/45/60-minute interval inside an instantBookAvailability window, never a whole window (see that field). Needs a requestId then an advisorId from prior calls. confirmed previews it; on success status is "submitted" with no booking ID — read statusInfo on get_request_advisors. Not for declining an advisor (reject_advisor) or cancelling a requested one (cancel_requested_consultation). Errors: isError, a plain message, and _meta.error_code/retryable — relay the message, never invent a cause; retry once only when retryable is true.

register_event

ChatGPT
Register the authenticated subscription client for one specific Guidepoint event (moderated call, roundtable, group meeting, focus poll, insight tracker, client-generated call, or AI-guided transcript) so they can complete registration inline in the AI conversation instead of switching to GP360. Pre-flight When no event_id is available in the current conversation context (e.g. the user said "register me for the next Tesla earnings call" without a preceding search_events result), call search_events first to obtain a real event_id and present the options to the user. Hand-typed, guessed, or fabricated event_id values are rejected — calling this tool with a fabricated id returns EVENT_LOOKUP_FAILED. When to route away from this tool - the user is asking about their own calendar / registrations — use get_user_registrations. - the user is browsing the general catalogue — use search_events. - the user asks to cancel — use cancel_registration. - the user asks to book an advisor consultation on an existing request (they carry a requestId and either an advisorId or a shortlist) — route to select_advisor or instant_book_advisor on the network-mcp surface. Split rule: event_id means register_event; requestId plus advisorId means select_advisor or instant_book_advisor. - the user asks for a new persona-based advisor engagement keyed by persona_uuid (no existing event_id, no requestId) — route to schedule_interview. Split rule: register_event only for an existing catalogue event_id; schedule_interview only for a persona_uuid returned by search_expert_hint. Pre-call confirmation gate Confirmation gate for register_event: 1. Present the event's title, date, event_type, and event advisors (name, job_title, company when disclosed) to the user. 2. Ask for explicit affirmative confirmation (e.g. "Yes, register me", "Go ahead"). Mere acknowledgment of the event (e.g. "That's the one") is not confirmation. 3. Wait for a clear affirmative before invoking the tool with confirmed=true. The confirmation gate applies to the destructive write path only — confirmed=true requires the three steps above. A confirmed=false (or omitted) call is the documented preview shape and is safe to invoke without prior user consent: it fires no upstream write and returns the CONFIRMATION_REQUIRED envelope carrying the event metadata the caller needs to run steps 1–2 with the user. The non-conforming shape is calling register_event with confirmed=true before an affirmative from the user has reached this side of the wire. Registration consumes the user's calendar slot and credit-unit allocation; treat it like a financial commitment. Response envelope render This is a WRITE action — the response is a success/error envelope. The confirmation line is the minimum required output; the response may additionally render the full event card (title Markdown link, metadata line, date/time, description, event advisors, cost when > 0, CTA row per the read-tool card structure) so the user sees the full context of the event they just acted on. Inline emoji, SVG markup, and image markup are permitted (widget-capable clients pass them through to their renderer; non-widget clients render as raw Markdown/HTML). Success envelope — surface a confirmation with the event title and date. A one-line confirmation is fine when the caller just wants the outcome; a full event card is fine when the user wants full context. Widget-capable clients may upgrade either shape to a styled confirmation banner or card. Confirmation-required envelope (status: "confirmation_required", isError: false, success: false) — this is a control-flow signal, not an error. The write did not fire yet; the sidecar is asking the caller to present the event to the user and collect explicit consent. Read structuredContent.event (title, date, event_type, event_advisors, cu_cost, requires_compliance_approval), render it as a preview card, and ask the user a yes/no question. On explicit affirmative, c…

reject_advisor

ChatGPT
Mark an advisor as declined / not interested on a request or project — use when the client has reviewed them and does not want to move forward. Triggers: "not interested in this advisor," "pass on this expert," "reject [advisor name]." It records the client's decision and does not delete the advisor, but it cannot be undone here — select_advisor will not move a declined advisor back, so a reversal needs the Project Manager (PM). confirmed previews the decline first. The service refuses this action on a Closed request. Workflow: get_requests/search_requests → get_request_advisors/search_request_advisors_by_screeners → reject_advisor, using the IDs from those calls. Not for moving an advisor forward (use select_advisor or instant_book_advisor) or withdrawing a consultation already requested (use cancel_requested_consultation). Errors: isError, a plain message, and _meta.error_code/retryable — relay the message, never invent a cause; retry once only when retryable is true.

search_events

ChatGPT
Search Guidepoint's curated catalogue of event advisor events — moderated calls, roundtables, group meetings, focus polls, insight trackers, client-generated and AI-guided transcripts — so a subscription client can discover and evaluate live or recorded event advisor events relevant to their research thesis, due-diligence question, sector tracking work, or upcoming-catalyst monitoring WITHOUT leaving the AI chat surface. Guidepoint events are compliance-reviewed, scheduled engagements where one or more vetted subject-matter event advisors present and answer questions on a specific industry, company, regulatory, or technology topic. Every returned event includes a brief description when one is available. Past events return the AI-generated post-event summary. Upcoming events return a 1-2 sentence agenda summary (from the moderator's published agenda items) so the user has topical context before deciding whether to register. Upcoming events also return registration metadata so the user can register through the register_event tool in the same conversation. Response shape. Every event in the response renders as its own multi-line card block — not as a Markdown table row, a numbered list, a compact one-line prose row, or a bulleted list of titles. A table or compact-list rendering is a regression: it hides the description line, event-advisor line, and CTA row, and breaks the widget pattern-match on client renderers. The N events in the response render as N sequential card blocks in the exact order the events array arrived — no theme subsections, no tense buckets (a "Upcoming — 1 event" / "Recent past — 8 events" split of one call's array is a regression), no sector groupings, no company groupings. Full card contract is in ## Card contents further down. CTA labels are FIXED — exactly `Register`, `Cancel registration`, `Request`, or `View in Guidepoint`. No other label is valid. View event, View transcript, View, Attend, Join, Open in Guidepoint, Details, Learn more — any variant outside the four-value set is a regression. The sidecar resolves the correct label per event and emits it as `cta_label` on the event object — render cta_label verbatim rather than re-deriving it from registration_status, user_registration_status, cu_cost, and requires_compliance_approval. The priority the sidecar applies (first match wins, top to bottom): | | Condition | cta_label | |---|---|---| | 1 | cu_cost > 0 | View in Guidepoint | | 2 | open + registered | Cancel registration | | 3 | open + not registered + cu_cost == 0 + requires_compliance_approval == True | Request | | 4 | open + not registered + cu_cost == 0 + no compliance requirement | Register | | 5 | closed (any user state) | View in Guidepoint | Rule #1 dominates: paid events (cu_cost > 0) always route to View in Guidepoint, even when the user is registered and even when compliance approval would otherwise apply. Full per-row button templates live in ## CTA logic further down. Actionable CTAs (Register / Cancel registration / Request) render as TWO lines: a Markdown link [Label](event_url) on line 1, then an italic prompt hint Or copy this prompt: *"…"* on line 2. Both lines are part of the card — the prompt-hint line gives the reader a copy-paste form of the CTA text and is carried on every actionable card. View in Guidepoint is a single Markdown link line with no italic hint. Actionable CTA — the two-line form in full. Every actionable CTA carries a two-line form: the Markdown link on line 1, the italic prompt hint on line 2. The canonical shape for a Register CTA is two physical lines: [Register](event_url) Or copy this prompt: "Register me for [title] on [date]" The same shape carries for Cancel registration and Request — different prompt text, identical two-line format. Non-conforming card shapes to avoid: - Card ending on the bare word Register (no link, no hint). Conforming shape: the two-line form above. - Card ending on [Register](event_url) alone (link but …

search_library

ChatGPT
Search Guidepoint's compliance-reviewed library of expert interview transcripts — firsthand intelligence from former executives, operators, and industry practitioners across hundreds of industries, curated by former investment analysts for decision-critical work. Each transcript is a structured Q&A exchange between an inquirer and a subject-matter expert, covering investment and market diligence, product and adoption research, and advisory and thematic research. Best for on-the-ground competitive intelligence, channel checks, and practitioner perspectives not available in public filings, news, or analyst reports. Each result returns: - transcript_name Name of the source transcript - date Date the expert call took place - inquirer Person or organization who posed the question - respondent Subject-matter expert who answered - question The specific question asked in the transcript - answer The expert's response - context Surrounding passage from the transcript (if available) - reference_url Link to the full transcript on the Guidepoint 360 platform - attribution_label Preformatted citation combining transcript name and URL How to search: send a direct thematic query, concrete keywords (names, products, tickers) to narrow which transcripts (calls) matter, optional start_date / end_date, optional recency_bias, and size for how many ranked excerpts to return in one response. When both query and keywords are set, keywords narrow transcripts first; the query then ranks excerpts within that set. Keywords need not appear in every returned chunk—they gate which calls are in scope; individual excerpts may omit a keyword entirely. See the tool parameter descriptions for phrasing and limits.

search_meetings

ChatGPT
Search completed consultations on one request, optionally by advisor: with whom, when, and their meeting ids, for the authenticated client. Upcoming ones are out of scope, and nothing on this connector reads upcoming 1:1 calls — so no calendar answer that omits them is complete. Not transcript text. Whole call: transcriptId + get_meeting_transcript (transcriptionStatus completed). Snippets: id + search_my_network_excerpts (excerptsAvailable). For "what is [person] saying about [topic]": search_requests, then this with advisorName. Only where the request row has transcriptsEnabled true. Needs a requestId (get_requests/search_requests); for one advisor advisorId (get_request_advisors) or advisorName. Cohort: one call per advisor. Closed requests are returned too; no write tool acts on one. One page per call; matchCount is the full total — page with page/perPage, check hasMore. Errors: isError, a plain message, and _meta.error_code/retryable — relay the message, never invent a cause; retry once only when retryable is true. An empty result is not an error.

search_my_network_excerpts

ChatGPT
Search My Network Q&A excerpts from my expert meeting transcripts (authenticated caller's completed 1:1 meetings within their organization entitlement)—questions, answers, and discussion content from completed 1:1 client–expert meetings. Use when the user asks about their own meetings, our calls, meetings they attended, or provides request/meeting IDs from their organization. Language: All search parameters must be English. Translate non-English user input before constructing query or keywords. Returns { count, data } per outputSchema (count = excerpts returned, 0 to size; data ranked best match first). Empty match: { count: 0, data: [] }. Empty results are normal—rephrase the search; do not retry identical parameters. Each item in data includes: - request_id Integer Guidepoint request ID for the engagement - request_name Name of the request - meeting_id ID of the specific meeting - meeting_date Date the meeting took place (YYYY-MM-DD or null) - question The question asked in the meeting - answer The expert's response - context Surrounding passage from the transcript (if available) - expert Expert who participated in the meeting (object or omitted) - primary_client Client participant on the meeting (object or omitted) - reference_url Link to the full transcript on the Guidepoint 360 platform - source_attribution { description, markdown } when reference_url present; omitted otherwise How to search: send a direct thematic query, concrete keywords (names, products, tickers) to narrow which meetings matter, optional request_ids (integer Guidepoint request IDs), optional start_date / end_date (meeting date, UTC, inclusive), optional meeting_ids to limit to specific meetings, and size for how many ranked excerpts to return in one response. When both request_ids and meeting_ids are set, all supplied filters apply together (intersection). When both query and keywords are set, keywords narrow meetings first; the query then ranks excerpts within that set. Keywords need not appear in every returned chunk—they gate which meetings are in scope; individual excerpts may omit a keyword entirely. See the tool parameter descriptions for phrasing and limits. Availability: Newly published meeting transcripts can take up to 2 hours to appear in search. Recent meetings may return { count: 0, data: [] } until indexed—same empty shape as a successful no-match, not an error. Parameter limits (query length, integer ranges, date format, ID rules) are enforced at call time; violations return isError: true before search. Validation failures and upstream errors are thrown by the MCP layer; they never return { count: 0, data: [] }. Empty { count: 0, data: [] } means the search succeeded with no matching excerpts.

search_request_advisors_by_screeners

ChatGPT
Search and filter advisors on a specific request by their screener Q&A responses. Use when looking for advisors who mentioned a keyword or answered a question a certain way. Triggers: "find advisors who mentioned [keyword]," "which experts said they worked in [region]," "filter by screener response." Screener answers are short vetting responses, not call commentary. Requires a requestId plus at least one text filter. Preferred when you need to find advisors by screener content and read their answers in one call — see includeFullScreeners. Returns advisorId, name and matching screener rows only — no status or availability fields, so call get_request_advisors before scheduling a match. For the full unfiltered advisor list, use get_request_advisors instead; for project text rather than screener answers, search_requests. Closed requests are returned too; no write tool acts on one. Errors: isError, a plain message, and _meta.error_code/retryable — relay the message, never invent a cause; retry once only when retryable is true. An empty result is not an error.

search_requests

ChatGPT
Search the authenticated client's own expert network requests (also called projects) by title, research-brief text, angle, type, status, transcripts-enabled, or creation-date range. Scoped to that one client — no client or user argument. Triggers: "show me open requests," "find the project called [title]," "which projects mention [topic]." titleContains searches the title only; anyText searches the title or the research brief, so prefer it for a topic that may not be in the title. For a cohort — "what do formers think" — start with angleContains, then get_request_advisors on each to see who carries it. For screener answers use search_request_advisors_by_screeners. Every filter is ANDed; at least one is required — for an unfiltered list use get_requests. Closed requests are returned too; no write tool acts on one. Errors: isError, a plain message, and _meta.error_code/retryable — relay the message, never invent a cause; retry once only when retryable is true. An empty result is not an error.

select_advisor

ChatGPT
Ask one advisor on the client's own request (requestId + advisorId) for a consultation, or for their screening answers and availability — the two clientAction values. Actions (clientAction): - request_consultation: set up a phone or AI-Moderated (aim) consultation. Requires consultationType. - request_screening_responses_and_availability: request the advisor's screening answers and availability. Needs a requestId, then an advisorId, from prior calls. Confirm the action with the client first. The service refuses this action on a Closed request. timeSlots: each slot is a 30- or 60-minute interval inside an availability window, never a whole window (see that field). Not for rejecting (reject_advisor), booking outright (instant_book_advisor), or cancelling a requested consultation (cancel_requested_consultation); a curated Guidepoint event registers through register_event by event_id, never here. Errors: isError, a plain message, and _meta.error_code/retryable — relay the message, never invent a cause; retry once only when retryable is true.

search_library

Claude

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/guidepoint"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/guidepoint)