MCP App Store
by KeenEthics
Enterpret icon

Enterpret MCP Server for Claude and ChatGPT

By Enterpret Inc

Overview

Connect Enterpret to analyze customer feedback and voice of customer data in Claude. Ask what customers are saying across support tickets, sales call transcripts, app reviews, NPS and CSAT surveys, and Slack, all unified in your Enterpret customer context graph. Enterpret brings together feedback from 50+ sources like Zendesk, Intercom, Salesforce, Gong, the App Store, Google Play, G2, Qualtrics, and more. Find top complaints and feature requests, uncover churn reasons and NPS drivers, track sentiment trends, measure feedback after a product launch, and pull customer evidence for PRDs and roadmap prioritization. Built for Product, CX, and support teams, every insight links back to the real customer conversations behind it. No dashboards or query language needed. Just ask.

How to connect

  1. Claude: Open the Enterpret listing in the Claude connectors directory and choose Connect. Claude listing Enterpret exposes 8 tools here.
  2. ChatGPT: Open the Enterpret listing in the ChatGPT app directory and choose Connect. ChatGPT listing Enterpret exposes 8 tools here.

Tools

archive_session

ChatGPT
Archive a session Changes data: supply operation_id so a retry cannot duplicate it. Uses this connection's session unless you name another session_id.

await_session_events

ChatGPT
Follow the work until this watch stops Uses this connection's session unless you name another session_id, which is how you resume an earlier session. Blocks while Enterpret Agent works; repeat with the same connection after a progress page. A terminal watch is an answer only when it contains final_answer or structured_output; awaiting human input needs respond_to_inbox_item and another watch, while cancellation or error is not a successful answer. Citation links come back exact: never rewrite or invent them.

cancel_session_current_turn

ChatGPT
Stop the turn Enterpret Agent is currently working on Changes data: supply operation_id so a retry cannot duplicate it. Uses this connection's session unless you name another session_id.

check_provider_connection_health

ChatGPT
Check whether a connected account still works — probes the provider and may mark it needing reauth Changes data: supply operation_id so a retry cannot duplicate it.

create_agent_message_feedback

ChatGPT
Record thumbs up or down on an agent answer Changes data: supply operation_id so a retry cannot duplicate it. Uses this connection's session unless you name another session_id.

create_agent_settings_instruction_block

ChatGPT
Add a custom instruction block to your organization's or your personal agent settings — read the current settings first for version Changes data: supply operation_id so a retry cannot duplicate it.

create_session_message

ChatGPT
Give Enterpret Agent work on this connection Changes data: supply operation_id so a retry cannot duplicate it. Uses this connection's session, creating one on first use, unless you name another session_id — that resumes it with this message. For a machine-readable answer, set body.output_contract to a JSON Schema contract with type=json_schema and a schema object; the completed watch returns EA-emitted data at structured_output.data. Check it against the requested schema before use; conformance enforcement may be disabled for this organization. Let EA ask the user through its inbox if the brief is ambiguous rather than guessing. Returns once the work is accepted, with the sequence to follow from; call await_session_events until it returns an answer or needs human input.

create_skill

ChatGPT
Create a skill for Enterpret Agent Changes data: supply operation_id so a retry cannot duplicate it. Builds the skill bundle from skill_md (and optional files) and registers it at the given scope; the agent can use it from its next turn.

delete_agent_settings_instruction_block

ChatGPT
Remove one instruction block from agent settings — read the current settings first for version Changes data: supply operation_id so a retry cannot duplicate it.

delete_session_file

ChatGPT
Delete a file from a session Changes data: supply operation_id so a retry cannot duplicate it. Uses this connection's session unless you name another session_id.

delete_skill

ChatGPT
Remove a skill so the agent stops using it (archived, not erased) Changes data: supply operation_id so a retry cannot duplicate it.

download_session_file_content

ChatGPT
Read a session file's contents Uses this connection's session unless you name another session_id.

download_session_file_version_content

ChatGPT
Read the contents of one revision of a session file Uses this connection's session unless you name another session_id.

download_skill_bundle

ChatGPT
Read a skill's bundled files

edit_user_message

ChatGPT
Rewrite one of your earlier messages and have the agent redo its answer from that point — follow with await_session_events Changes data: supply operation_id so a retry cannot duplicate it. Uses this connection's session unless you name another session_id.

find_user_quote

ChatGPT
Extract validated verbatim quotes matching a focused criterion from Enterpret records. Use for direct quotations from records discovered through a graph query. Accepts 1-10 candidate record IDs and returns up to 5 matching quotes with speaker attribution and source links. It may return fewer quotes or none when the records lack matching evidence. Do not substitute summaries or raw record text for a missing validated quote. Preserve returned quote text and its speaker attribution link together. For prose: > "Quote text" > — [Speaker](record link) For tables, keep "Quote text" — [Speaker](record link) in the same cell, including when a separate record-link column is requested. Do not replace the linked speaker attribution with an unlinked name or a separate "Source" link. Keep candidate records within any source or date scope requested by the user. Args: criteria: A self-contained description of the evidence needed for this call: product or feature, topic, kind of statement, comparison direction, and necessary conditions or exclusions. Preserve logical relations: "A and B" requires both; "A or B" permits either. Do not weaken necessary conditions or strengthen alternatives. Describe what the speaker must actually say. Preserve explicit author/account exclusions in every applicable call, including retries; speaker_type is a broad role selector, not a substitute for these exclusions. For example, customer-only speech does not by itself establish that a quote excludes the organization's own account. Match the original request's required and excluded evidence before calling; do not drop an exclusion when splitting the request into topic-specific calls. On retries keep the evidence conditions, sentiment, logical relations and exclusions unchanged. Broaden the candidate graph query or record pool. Correct criteria only when they misstate the user's request. Keep dates, sources, customer cohorts and release/platform filters in the candidate graph query; include them here only when the quotation itself must establish that fact. Do not turn a request to cancel into proof of a completed cancellation, or add a cause, outcome or named launch absent from the requested evidence. Include only this call's evidence focus, not every report section, the original user message or conversation history. Do not impose an arbitrary word limit. record_ids: Candidate NLI record IDs returned by a previous graph query. count: Number of quotes to return, between 1 and 5; defaults to 1. speaker_type: Whose words to extract: customer, agent (including the organization's own support staff or sales representatives), or either. If omitted, the tool infers the speaker role from criteria alone. Supply this preference explicitly when known to skip the classification call. Choose who speaks, not who the quote is about: customer feedback about support is still customer speech. Use agent or either only when the request asks for the internal team's own words, or explicitly asks for both sides. language: Quote language: organization_default (default), english, or original for the source's untranslated language. Use original for a non-English request unless English translation is explicitly requested. Otherwise, use organization_default when no language preference is specified. Returns: Validated quotes with speaker attribution and source links, or an explanation when no matching quotes are found. Use only results that satisfy the retained exclusions. A returned speaker label that conflicts with an exclusion is unresolved evidence, not permission to relabel the speaker or include the quote because its wording sounds like a customer.

fork_session_file_revision

ChatGPT
Copy an agent-generated session file into your own editable standalone file Changes data: supply operation_id so a retry cannot duplicate it.

fork_skill

ChatGPT
Make your own editable copy of a shared or built-in skill Changes data: supply operation_id so a retry cannot duplicate it.

get_agent_settings_customization

ChatGPT
Read custom instructions for the org or yourself

get_connector

ChatGPT
Read one integration's details — refreshes the connected account's health, which may mark it needing reauth

get_effective_agent_settings

ChatGPT
Read the settings the agent will actually use

get_graph_schema

ChatGPT
Get the Knowledge Graph schema structure for a specific organization. Retrieves entity names, relationships, and static properties. The compact properties list retains static fields but omits source-specific metadata. Account/User names and emails may be omitted; absence here does not mean absence from the organization. For attributes not listed, use search_graph_fields and copy the exact entity and query_name returned. An empty field search means that lookup did not resolve the attribute. Do not claim an entity has only identifiers or no custom fields from this compact view. Use the returned relationship type, source_node, and target_node to form joins. Do not infer a relationship merely because both entities exist. If the requested path is absent, do not guess another spelling or invent an intermediate edge. IMPORTANT — check this flag in the response: has_source_fields: - If true: call search_graph_fields(query) to resolve relevant integration fields not already verified in this turn (Zendesk, Salesforce, Gong, etc.) - If false: the source-field search index is unavailable for this org. This is not proof that source fields do not exist. Do not guess them; disclose unresolved attributes unless another schema discovery tool verifies their exact names. Returns: Schema structure with has_source_fields flag

get_inbox_item

ChatGPT
Read one request waiting on a human

get_organization_details

ChatGPT
Get details about your organization. Fetches organization metadata including name, slug, and dashboard URL. This is useful for understanding your organization context and generating proper links to customer records. Returns: Organization details including name, slug, and dashboard URL

get_profile

ChatGPT
Return the profile represented by this request's authenticated credentials. The opaque id is unique within this app and unchanged across token refresh and reconnection; display fields are included when known. Read-only; takes no arguments.

get_query_examples

ChatGPT
Get sample Cypher queries similar to what you need to build. Returns reference examples showing correct compiler dialect. Some examples include a wrong_cypher field showing a common mistake and why it fails — study these to avoid the same errors. Examples that need a label, relationship or property this tenant's schema lacks are hidden (see hidden_by_schema and warnings). Never reintroduce a label, relationship or field from memory; confirm it in get_graph_schema first. HOW TO USE THE RESULTS: 1. Study the correct_cypher patterns — relationships, COUNT DISTINCT, date functions, MISC filters, category_enum usage 2. If wrong_cypher is present, understand what mistake it shows and avoid it 3. ADAPT the patterns with exact values, entity labels, and field names discovered from search_graph_values, search_graph_fields, and schema results 4. Build your own query — do NOT copy-paste. Check every added/changed property against its owning entity and every join against the exact schema endpoints and direction. A supported example does not validate your modified query. wrong_cypher is a negative example: never execute it to probe the schema. If a field or join cannot be resolved, report that lookup as unavailable. 5. For month/month-range requests with no year, use the most recent fully completed occurrence relative to the current date. If the range is upcoming or in progress this year, use the previous year. 6. For "last month" / "past month" without a named calendar month, use a rolling window: now() - INTERVAL 30 DAY. For daily/weekly/monthly analysis, keep that same filter for every query; group daily/weekly with toStartOfDay/toStartOfWeek, and make monthly the window total unless the user asks for a multi-month trend. 7. For quote requests inside explicit date windows, candidate-record queries should return record_id plus record_timestamp/source/summary. Make the first sentence of the final answer state the actual earliest/latest records analyzed, before any title/heading/quote list; do not only repeat the requested window. 8. For CASE-bucket counts, prefer WITH ... CASE ... END AS bucket, then RETURN bucket, COUNT(DISTINCT ...) so the compiler groups by the bucket. 9. Preserve explicit source filters from the user. If the user says Zendesk/App Store/Gong/G2, do not swap in a different source discovered from exploratory results. 10. "General" and "Generic" taxonomy values are not Miscellaneous. Unless the user explicitly says "miscellaneous", still filter only type != 'MISC' and do not add type != 'GENERIC'. 11. For source metadata prompts, include the source and field intent in search_graph_fields: "appstore rating country", "zendesk tags customer experience", "gong account name call title", "g2 star rating". 12. Resolve taxonomy/source values with search_graph_values before filtering names. If level is unknown, search relevant types and use the returned object_label/property_path; do not assume the level upfront. 13. Prefer taxonomy filters over content keywords when a relevant taxonomy value exists. Pin the resolved node's record_id with equality/IN, and type != 'MISC' unless miscellaneous is explicitly requested. 14. L1/L2/L3 are product scope. Theme/Subtheme are customer topics/issues. For complaints/topics under product scope, join Theme/Subtheme from the same cft; complaints use t.category_enum CONTAINS 'COMPLAINT'. 15. If no relevant taxonomy value exists, use content fallback: summary/content searches use fi.content; exact/raw wording searches use nli.content. Preserve quoted/exact phrases as one string. 16. For generic "top themes" / "dominant themes" / theme-ranking requests, always run the Theme-level ranking first without Subtheme: join (cft)-[:HAS_THEME]->(t:Theme), filter t.type != 'MISC', and aggregate by t.record_id, t.display_name to get the exact total for each theme. Do not substitute L1/L2/L3 product taxonomy or content keyword buckets unless the user asks for product/feature areas instead of themes. Then, when subthemes are requested, run a second query for the returned theme ids (t.record_id IN [...]) us…

get_session

ChatGPT
Read one session's title, status, and owner Uses this connection's session unless you name another session_id.

get_session_file

ChatGPT
Read one session file's metadata Uses this connection's session unless you name another session_id.

get_session_file_download_signed_url

ChatGPT
Get a download link for a session file Uses this connection's session unless you name another session_id.

get_session_file_signed_url

ChatGPT
Get a preview link for a session file Uses this connection's session unless you name another session_id.

get_session_file_version

ChatGPT
Details of one revision of a session file: size, author, when Uses this connection's session unless you name another session_id.

get_session_file_version_download_signed_url

ChatGPT
Get a download link for a file revision Uses this connection's session unless you name another session_id.

get_session_file_version_signed_url

ChatGPT
Get a preview link for a file revision Uses this connection's session unless you name another session_id.

get_session_settings

ChatGPT
Read one session's model and behaviour settings Uses this connection's session unless you name another session_id.

get_session_settings_defaults

ChatGPT
Read the default session settings for this tenant

get_skill

ChatGPT
Read one skill's definition

get_standalone_file

ChatGPT
Read a file that is not attached to a session

get_standalone_file_download_signed_url

ChatGPT
Get a download link for a standalone file

get_standalone_file_signed_url

ChatGPT
Get a preview link for a standalone file

list_connectors

ChatGPT
List integrations the agent can use

list_inbox_items

ChatGPT
List requests waiting on a human

list_provider_connections

ChatGPT
List connected accounts per integration

list_session_available_skills

ChatGPT
List the skills one session can actually use Uses this connection's session unless you name another session_id.

list_session_feedback

ChatGPT
Read thumbs and comments left on a session Uses this connection's session unless you name another session_id.

list_session_file_versions

ChatGPT
List a session file's revisions Uses this connection's session unless you name another session_id.

list_session_files

ChatGPT
List files attached to or produced by a session Uses this connection's session unless you name another session_id.

list_session_tool_approval_preferences

ChatGPT
List tool approvals for one session Uses this connection's session unless you name another session_id.

list_sessions

ChatGPT
List agent sessions, newest first

list_shared_sessions

ChatGPT
List sessions shared with you

list_skills

ChatGPT
List every visible skill — platform, organization and your own — or one scope via scope

list_tool_approval_preferences

ChatGPT
List standing tool approvals

promote_skill

ChatGPT
Publish your personal skill to your whole organization — it moves out of your personal set Changes data: supply operation_id so a retry cannot duplicate it.

rename_session

ChatGPT
Rename a session Changes data: supply operation_id so a retry cannot duplicate it. Uses this connection's session unless you name another session_id.

resolve_taxonomy_scope

ChatGPT
Resolve the subject of a counting or breakdown question to the exact taxonomy nodes to filter on. Call this BEFORE writing any Cypher that filters L1/L2/L3/Theme/Subtheme nodes for a subject the person named ("volunteers", "the Record Page feature", "asked to pin the calendar to the sidebar", "running out of leads"). Do not pick taxonomy nodes yourself: the same question must give the same number on every run, and this tool makes that choice deterministically. What it does: searches the phrase and its variants across all five taxonomy levels, keeps nodes sharing most of the phrase's words, looks up which parent each matching child is tagged under (for Theme/Subtheme matches, also the product node most of them sit under), and applies fixed scope rules (an exact or uniquely named node wins; otherwise the parent covering the matching children is preferred over any one child). Where the rules leave more than one reasonable scope, a pinned server-side model picks from the fixed option list. Pass the question's date window (window_start, window_end, inclusive YYYY-MM-DD) and the tool also builds the final count query itself, runs it and returns count with the exact count_cypher. count is the number of distinct feedback records tagged with the taxonomy scope within the window, of every category: not users or accounts, and not only complaints, requests or praise. When the question asks for exactly that total, report it as the answer; do not write your own count query for this subject, and do not run run_graph_query to recount or double-check it. Otherwise do NOT report count: when the question counts users, accounts or another entity, keeps only complaints, requests or praise, groups the result, or filters on source, segment, account, rating or any other field, run run_graph_query on exactly the returned scope record_ids and the window plus those conditions. The same question and window always produce the same Cypher text, and so the same number. Always pass question (the full question) and the window when the question has one. If the tool answers that the label search did not complete, call it once more with the same arguments. Without a window, filter run_graph_query on EXACTLY the returned scope nodes by record_id (<alias>.record_id IN [...]), with <alias>.type != 'MISC', and count DISTINCT feedback records (nli.record_id) across them, or the users or accounts behind them when the question counts those. Do not add, drop or swap nodes, and do not switch to label filters. When scope is empty no taxonomy node matched: say so and fall back to a content search. Args: phrase: The person's own wording for the subject, kept complete: keep feature, tab and product names and qualifiers exactly as written ("volunteers", "navigation in the subscribers page top-level tabs (Analytics, More)"). Do not shorten, paraphrase or translate it. It is the subject, not the whole question. Call once per subject and do not retry with a reworded phrase. scope_kind: "product" for a product area or feature ("about X"), "opinion" for a complaint, request or praise ("complained about X", "asked for X"), "unknown" if the wording does not say. question: Optional. The person's full question, used only to choose between options when the rules do not decide ("including..." keeps the broad subject; "only..." narrows it). window_start: Optional. First day of the question's window, YYYY-MM-DD. window_end: Optional. Last day of the question's window, inclusive, YYYY-MM-DD. Pass both or neither. Returns: scope (level, name, record_id), scope_complete (false when a chosen node had no non-MISC record_id and was left out, or the chosen labels name more than 500 nodes; no count is run then), search_truncated (true when the label search hit its limit or the per-field value cap, so the candidate pool may be incomplete; a count over a set of matched nodes is not run then, nor over the one product node containing every word of the phrase when an L1/L2/L3 search was cut), decided_by (rule, model, rule_fallback), rule, confidence, reason, every opt…

respond_to_inbox_item

ChatGPT
Answer a request that is waiting on a human Changes data: supply operation_id so a retry cannot duplicate it.

revoke_session_tool_approval_preference

ChatGPT
Withdraw a tool approval you granted for one session, so the agent must ask again there Changes data: supply operation_id so a retry cannot duplicate it. Uses this connection's session unless you name another session_id.

revoke_tool_approval_preference

ChatGPT
Stop the agent auto-running a tool you always-allowed (also clears its per-session approvals) Changes data: supply operation_id so a retry cannot duplicate it.

run_graph_query

ChatGPT
Execute a Cypher query against Enterpret's Knowledge Graph. Translates your Cypher to SQL and returns structured results. Enterpret's KG unifies 100+ sources (Zendesk, Gong, Slack, AppStore, etc.) into a single graph. Source identity: nli.source. Source-specific metadata fields live on whichever entity the field belongs to — qualify each one with the alias matching its entity group as returned by search_graph_fields (nli.* for NLI/FeedbackRecord, the joined account/user alias for Account/User fields). Supported aggregates: COUNT, SUM, AVG, MIN, MAX. COLLECT is unsupported; use separate RETURN DISTINCT rows and aggregate counts instead. Sort by a returned property or alias, not ORDER BY (CASE ...). WITH ... ORDER BY ... LIMIT followed by MATCH is unsupported; select IDs first, then query those IDs for details. After a syntax error, make at most one correction using these supported forms; do not keep trying new syntax after the requested data was already retrieved. BEFORE writing any Cypher, resolve the schema first: - Use only node labels, relationships, and attributes actually present in this organization's active get_graph_schema result or returned by search_graph_fields. For each property, verify its exact stored name, owning entity, and type BEFORE constructing the query. Reuse schema-backed results already in this turn. - For every join, verify the relationship type AND its source/target entities and direction in get_graph_schema. Two existing entities do not imply an edge. search_graph_fields discovers attributes, not relationship paths. Do not invent an intermediate join or borrow a relationship from a different pair of entities. - If the requested attribute is not listed, call search_graph_fields using its business meaning first. Copy the returned field name exactly onto the alias for its owning entity, preserving capitalization, encoding, and type suffixes. A field on one entity is not evidence that another entity has the same field. - Never guess a property from a familiar concept, a display label, a raw source key, or a conventional spelling. Never run a query to test whether a guessed field exists. Query execution is not schema discovery. - Call get_query_examples for query structure, not for permission to invent or substitute fields. Verify every field you add or change against the schema; an example's aliases and business labels do not establish new attributes. - After a schema error, rediscover the field or path before at most one corrected attempt. If the same relationship or property remains unresolved, stop and report unavailable. A different schema error starts its own discovery step; preserve the original question. - An empty field search permits at most one focused rephrasing for that attribute. An index/compiler mismatch warning requires stopping unresolved lookups; raw value-search property paths and examples do not authorize compiler field names. - If schema discovery cannot resolve the requested attribute, stop that lookup and report it as unavailable. Do not try alternate spellings or silently substitute a different attribute. Continue independent, supported work. - Do not use unsupported relationship-variable syntax such as -[r]->; use a schema-listed relationship type in -[:TYPE]-> form. - Query examples and memory are not value-resolution evidence: before using a literal L1/L2/L3/Theme/Subtheme/Source name in WHERE, resolve it with search_graph_values. If the level is unknown, search relevant types and use the returned object_label/property_path. You MUST follow the Enterpret-specific Cypher rules below. Standard Neo4j Cypher patterns will often fail or return incorrect results due to the KG's structure (relationship fan-out creates duplicate rows). LIMIT Choose LIMIT from what EACH query returns, not keywords anywhere in the request. An aggregate can still be a ranked subset: "biggest complaints and their counts" requires ORDER BY total DESC LIMIT N, even though the request mentions counts. Use a separate uncapped COUNT query if the same request also needs a headline total. No LIMIT — user…

search_graph_fields

ChatGPT
Resolve source/customer-specific metadata field names for Cypher. Purpose: use this tool when the user refers to a source-specific or customer-specific metadata field and the exact graph property is unclear. It is not a general schema search across all graph fields, and it does not validate field values. Use this as the field-name resolver for source/customer metadata. If the source-field index is unavailable or inconsistent with the compiler catalog, the response includes a warning. This does not prove the field is absent. For an ordinary empty search, try at most one focused rephrasing for the same attribute. If still unresolved, stop that lookup and report it unavailable. For an index/catalog warning, do not repeat searches: use an exact property already verified in the active schema, or stop the affected lookup. Never construct encoded names from raw metadata or value-search property paths. Examples show query structure, not evidence that a property is queryable. Do not replace an unresolved requested filter or grouping with content, source, or another attribute. Offer a separately scoped alternative without executing it as the answer. Continue independent work with verified fields. Use for source/customer metadata fields such as: - Zendesk ticket status, tags, queue, or priority. - App Store rating, country, or app version. - Gong call title, account name, or call metadata. - Salesforce churn reason, opportunity fields, or case metadata. - Plan type, bucket, QID/question fields, NPS/CSAT/DSAT score fields, rating fields, or custom segment fields when these are source metadata. Do not use for: - Fixed graph properties such as Theme.display_name, L1.name, NLI.source, language, or sentiment. - General "find any relevant field in schema" discovery. - Value validation. Use search_graph_values for user-provided values. Mandatory pair with value search: - This tool resolves field names only. It does not validate that a user value exists under the field. - If the user asks for a value filter such as "paid teams", "free plan", "spenders", "Qualtrics", "SMB NPS", or "Zendesk", call search_graph_values for that value/source as well. - For questions like "Where can I find NPS score data?", call this tool with a focused field query such as "nps score" or "net promoter". Do not answer from schema absence alone until this field probe has been attempted or the active schema already contains the exact score field. If the field search returns a degraded warning, check already verified schema properties; do not conclude "NPS is not available" from the degraded warning alone. - For mixed asks such as "Qualtrics SMB NPS bucket spenders QID2", split the work: search_graph_fields for field labels like "qualtrics bucket" and "qualtrics QID2"; search_graph_values for values like "Qualtrics", "SMB NPS"/"NPS", and "spenders"/"spender"/"spending". Do not treat a successful field hit as proof that any of those values exists. HOW TO CALL: Include the source name in your query for better matches. Good: "zendesk ticket status and tags" Good: "zendesk satisfaction rating csat" Good: "zendesk tags customer experience" Good: "gong call title and account name" Good: "appstore rating country" Good: "g2 star rating" Good: "nps score" Good: "qualtrics bucket" Good: "qualtrics qid2" Bad: "billing issues" (too vague, may return wrong source's fields) Bad: "qualtrics bucket survey name SMB NPS spenders" (mixes fields and values) HOW TO USE RETURNED FIELDS: - Returned fields are query candidates for source/customer metadata that may be omitted from the compact graph schema. Do not reject a returned field just because it is absent from get_graph_schema/TOON. - Use the exact returned query_name and type for a field matching the requested meaning and entity. A partial catalog warning does not invalidate returned fields. If none matches the requested attribute, stop that lookup; do not search again for withheld fields or infer their names from the warning. - Do not say a returned field is unavailable only because it is absent from compact schema/TOON. - Fo…

search_graph_values

ChatGPT
Search indexed Context Graph field/value suggestions to find candidate entity, source, taxonomy, and filter values before writing Cypher. Purpose: use this as the broad concept locator to discover where a user phrase appears in the graph and resolve exact values for filters. This tool intentionally returns both field/property matches and value matches because user wording can refer to a taxonomy value, source name, metadata value, product/account/status/segment value, or a field whose values need follow-up. TWO PHASES -- the second one is yours to ask for: - WITHOUT entity_types, this searches LITERALLY across every field: metadata, source, and taxonomy. Cheap, broad, and it tells you WHERE a value lives. It cannot match a value worded differently from your term. - WITH entity_types, taxonomy values are additionally searched SEMANTICALLY, which is the only way to reach a reordered, inflected, or paraphrased value ("pin calendar sidebar" -> the stored "Want Pinned Sidebar Calendar"). - So after a phase-1 call, CALL AGAIN with entity_types whenever the concept is a topic, issue, feature, or theme -- EVEN IF phase 1 already returned values. Phase 1 returning something is not evidence that it returned everything: it finds the literal match and misses the paraphrase of the same idea. - Do NOT escalate when the concept is not a topic and phase 1 already resolved it on a metadata or source field -- a person, account, ticket, email, or source name is not a taxonomy label, and semantic search on those fields does not exist. Take the phase-1 value and move on. - Semantic search exists ONLY for: Theme, Subtheme, L1, L2, L3, Competitor, WinLossReason, UseCase, DealFeature, Risk. Nothing else is semantically searchable, so nothing else is worth escalating. WHICH entity_types TO ESCALATE WITH -- a wrong level returns almost nothing: - Type the VALUE being resolved, not the requested output. A named Theme value -> ["Theme"]; a named Subtheme value -> ["Subtheme"]; competitors -> ["Competitor"]. "Top themes about X" asks for Theme output, but does not say which taxonomy level holds X. For product areas/categories/features, use the L1/L2/L3 level the user named or that this org's taxonomy verifies. - If the level is genuinely unknown, pass ALL FIVE: entity_types=["Theme", "Subtheme", "L1", "L2", "L3"]. Measured: this finds exactly as much as naming the right level, and returns ~2.8x as many values to read. That is the correct trade when you are unsure -- it costs reading, never recall. - It is ALL FIVE or the level the user named -- there is no middle option. Two or three levels is still guessing, and it carries the same risk as one while saving almost nothing: the value sits at exactly one level, so a partial guess either includes that level or misses it entirely. - NEVER guess. Measured: the right level recalls ~88% of expected values, a wrong level recalls under 1% -- and it does NOT come back empty. Semantic search ranks neighbours with no relevance floor, so the wrong level hands you plausible-looking values that are not what you asked for. A gibberish term still returns 25 of them. Treat a scoped result as an answer only if a value in it is actually the thing you searched for. - Do NOT pick the level from which levels phase 1 happened to match lexically. Measured: that is worse than naming the level AND noisier, because a common word matches several levels while the semantic answer lives in one. - The response names the levels it did NOT search. Read that list before concluding a value does not exist, and before accepting a value you are not sure about. Mandatory workflow: - Before any run_graph_query WHERE filter using a user-provided value, alias, source/channel name, taxonomy/product term, segment, status, rating, score, account, competitor, or metadata value, call search_graph_values for that concept unless the exact graph value came from tool output earlier in this turn. - For taxonomy/product value searches, use this tool to discover the matching taxonomy field and canonical value. A broad taxonomy search can iden…

share_session

ChatGPT
Share one of your sessions so everyone in your organization can view it Changes data: supply operation_id so a retry cannot duplicate it. Uses this connection's session unless you name another session_id.

unarchive_session

ChatGPT
Restore an archived session Changes data: supply operation_id so a retry cannot duplicate it. Uses this connection's session unless you name another session_id.

unshare_session

ChatGPT
Stop sharing one of your sessions with your organization Changes data: supply operation_id so a retry cannot duplicate it. Uses this connection's session unless you name another session_id.

update_agent_settings_instruction_block

ChatGPT
Edit the name or text of one saved instruction block — read the current settings first for version Changes data: supply operation_id so a retry cannot duplicate it.

update_agent_settings_model_settings

ChatGPT
Choose which models and providers the agent may use, and its default — read the current settings first for version Changes data: supply operation_id so a retry cannot duplicate it.

update_session_settings

ChatGPT
Change one session's model or behaviour settings Changes data: supply operation_id so a retry cannot duplicate it. Uses this connection's session unless you name another session_id.

update_skill

ChatGPT
Replace a skill's instructions Changes data: supply operation_id so a retry cannot duplicate it. Read the skill first for expected_updated_at; the new bundle is built from skill_md (and optional files) and replaces the old one.

upload_session_file

ChatGPT
Give Enterpret Agent a document Changes data: supply operation_id so a retry cannot duplicate it. Uses this connection's session.

find_user_quote

Claude

get_graph_schema

Claude

get_organization_details

Claude

get_query_examples

Claude

resolve_taxonomy_scope

Claude

run_graph_query

Claude

search_graph_fields

Claude

search_graph_values

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/enterpret-wisdom"><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/enterpret-wisdom)