"Understanding Context Memory in Chat Systems" matching MCP tools:

• start_dixy_call_authA

  AgentPayA

  Create or recover the secure Dixy sign-in. Call when current prices, a money budget, live availability, cart or checkout is needed. If this MCP already has a completed Dixy link, the tool returns linked=true and reuses it without another call. Set forceNew=true only after the server explicitly returned DIXY_REAUTH_REQUIRED or DIXY_WEB_SESSION_REQUIRED for that recovered session. It takes no phone number. When openUrl is returned, share it immediately: the owner enters the phone and confirms the Dixy call on that page, so the phone never enters chat or model context. Never ask the owner to type or approve a phone number in chat. Then poll_dixy_call_auth with linkSessionId. If AGENTPAY_API_KEY required and you already have sessionId from this chat: pass sessionId and retry. Never begin_agent_link again. Never ask the owner to edit connector settings or reconnect. Never web-search.

  ConnectorNo auth

• aiA

  Fast.ioA

  Ripley — the MCP delegation surface over Fastio's RAG agent. Ripley is read-only for storage CONTENT: it answers natural-language questions about workspace/share files & folders (with citations) and never creates/edits/deletes your files — for content writes, call the primitive MCP tools directly. It DOES create/manage chat threads (chat-create/chat-update/chat-delete/message-send) and can generate shares (share-generate). Prefer Ripley over issuing many primitive reads: ask one NL question and let the server-side agent search + synthesize. Quick start: action='ask' (question + profile) → returns {answer_text, citations, chat_id, message_id, web_url}; action='status' for an engineered workspace-status summary. Lower-level chat/message actions remain for multi-turn control. Call action='describe' for the full action/param reference. Destructive: chat-delete. Side effects: ask/status/chat-create/message-send consume credits; chat-cancel terminates an in-progress message (partial tokens billed; idempotent). Verbosity (detail param): chat-list/message-list default to terse (compact rows). chat-details/message-details default to full (drill-down). Pass an explicit detail='standard'|'full' to override (best-effort: chat/message/activity endpoints may not yet honor detail server-side).

  Connector

  Destructive

  No auth

• set_agent_memoryA

  Valuein — SEC EDGAR Fundamentals & Smart-Money DataA

  Store or update ONE durable memory entry (key → value) for this user so context survives across sessions — preferences, prior conclusions, working context. Replace semantics per key (reusing a key overwrites it). Do NOT store a number you would later cite as a fact: financial figures come from data tools and carry fact_ids; memory values are never treated as verified figures. Caps: 200 entries / 8000 chars per value. Tier: sp500+ (sample rejected).

  ConnectorNo auth

• forgetA

  memxusA

  Permanently delete one memory by UUID. When to use: user asks to remove outdated or incorrect context, or to free plan storage. When NOT: fix content → update (mode=replace); find the ID first → list_memories or recall. Requires delete OAuth scope. Non-idempotent: deleting the same memory_id twice fails. Errors: Memory not found, Not authorized to delete this memory. Side effects: removes the memory row and vector embedding with no recovery; invalidates plan cache. The target workspace is always the one the memory itself belongs to (echoed in resolved_workspace); optionally pass workspace: <name> as a safety confirmation — the call fails if the memory is not actually in that workspace.

  Connector

  Destructive

  No auth

• fetchA

  Penfield MemoryA

  [ChatGPT Connector compat] Fetch memory by ID. Exists to satisfy ChatGPT Deep Research's required `search`/`fetch` tool contract. Native MCP clients should fetch via `recall` + memory_id, or use the API's GET /memories/{id} endpoint directly. Returns a single memory with citation support (id, title, url, text fields). Args: id: Memory UUID to fetch ctx: MCP context Returns: Dict with id, title, url, text, metadata fields

  ConnectorOAuth

• log_favorite_songA

  Dayze — Life ContextC

  MUTATES the authenticated user favorite tracks list at /music. Use when they favorite or save a song — do not store this as a chat memory or in music_preferences. Example: “Henry Mancini - Piano And Strings (1995 Remastered)” → log_favorite_song({ track: "Henry Mancini - Piano And Strings (1995 Remastered)" }) or title + artist. Optional year_note, source_url. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)

  ConnectorNo auth

• connectA

  Penfield MemoryA

  Connect memories to build knowledge graphs. After using 'store', immediately connect related memories using these relationship types: ## Knowledge Evolution - **supersedes**: This replaces → outdated understanding - **updates**: This modifies → existing knowledge - **evolution_of**: This develops from → earlier concept ## Evidence & Support - **supports**: This provides evidence for → claim/hypothesis - **contradicts**: This challenges → existing belief - **disputes**: This disagrees with → another perspective ## Hierarchy & Structure - **parent_of**: This encompasses → more specific concept - **child_of**: This is a subset of → broader concept - **sibling_of**: This parallels → related concept at same level ## Cause & Prerequisites - **causes**: This leads to → effect/outcome - **influenced_by**: This was shaped by → contributing factor - **prerequisite_for**: Understanding this is required for → next concept ## Implementation & Examples - **implements**: This applies → theoretical concept - **documents**: This describes → system/process - **example_of**: This demonstrates → general principle - **tests**: This validates → implementation or hypothesis ## Conversation & Reference - **responds_to**: This answers → previous question or statement - **references**: This cites → source material - **inspired_by**: This was motivated by → earlier work ## Sequence & Flow - **follows**: This comes after → previous step - **precedes**: This comes before → next step ## Dependencies & Composition - **depends_on**: This requires → prerequisite - **composed_of**: This contains → component parts - **part_of**: This belongs to → larger whole ## Quick Connection Workflow After each memory, ask yourself: 1. What previous memory does this update or contradict? → `supersedes` or `contradicts` 2. What evidence does this provide? → `supports` or `disputes` 3. What caused this or what will it cause? → `influenced_by` or `causes` 4. What concrete example is this? → `example_of` or `implements` 5. What sequence is this part of? → `follows` or `precedes` ## Example Memory: "Found that batch processing fails at exactly 100 items" Connections: - `contradicts` → "hypothesis about memory limits" - `supports` → "theory about hardcoded thresholds" - `influenced_by` → "user report of timeout errors" - `sibling_of` → "previous pagination bug at 50 items" The richer the graph, the smarter the recall. No orphan memories! Args: from_memory: Source memory UUID to_memory: Target memory UUID relationship_type: Type from the categories above strength: Connection strength (0.0-1.0, default 0.5) ctx: MCP context (automatically provided) Returns: Dict with success status, relationship_id, and connected memory IDs

  ConnectorOAuth

• get_timelineA

  XMemoA

  Read authorized timeline events newest first. Requires memory:read and makes no memory changes. Use it for recent history or session resumption; use recall_context for semantic multi-memory context. limit is clamped to 1-500; session_id and event_type are exact filters.

  ConnectorOAuth

• upload-fileA

  Fax.PlusA

  Automation-only: upload document bytes as base64 for non-chat integrations, then call send-fax-uploaded with the returned path. NEVER use this in chat — call pipeline_start, list-numbers, list-contacts, then request-file-from-user (UI or curl). File bytes must not pass through the model for chat flows. Never expect a document as a chat attachment. Side effects: stores file for fax delivery.

  Connector

  Destructive

  API key

• agent_memory_appendA

  Robot Actions — Remote Device ControlB

  Append a block to the calling user's persistent agent memory. Use this when the user explicitly says "remember X", "save this", or "note for next time" — DO NOT auto-update on every interaction. Memory is auto-prepended to your system prompt on every chat in this user's account. Cap: 10240 bytes total; over-cap appends return 413. Markdown is encouraged; keep entries terse and factual (preferences, project context, references), not verbose.

  ConnectorOAuth

• wa_get_chatA

  WhatsMCP: MCP for WhatsAppA

  Read the most recent messages for one WhatsApp account, oldest first — or, with chat, one conversation, including older history loaded with wa_load_history. Use this for context before replying; use wa_list_messages to page through everything new.

  ConnectorOAuth

• rememberA

  mcpA

  Save a durable PREFERENCE about how this user wants their bookmark library handled — the themes they organise by, topics to exclude, preferred summary length/format, which account is their main one. It carries across sessions AND into the Tweetsmash web app, which your own client memory cannot reach. Use it for lasting preferences the user states or confirms, not for general chat context, task state, or anything secret.

  ConnectorNo auth

• message_agentsA

  Vilix AIA

  Post a message to the user's OWN running agents. Vilix delivers it inside the `inbox` field of every matching Vilix read call (get_context, searches, recent_messages, get_project, get_skill, list tools) those agents make — a push channel that rides their next memory read, from any connected client including a phone. `body` (required) — the message, markdown, max 2000 chars. `urgency` — "normal" (default: delivered once per chat, then done) or "urgent" (redelivered on EVERY read in every chat until the receiving agent calls ack_message, or the message expires). `scope_type` — who should receive it: "global" (default, all of the user's agents), "project" / "task" (only chats whose context touches that project — pass the project/task id you OWN in `scope_value`), or "source" (only agents running on one platform label, e.g. "Claude Code" — pass the label in `scope_value`). `ttl_hours` — expiry, default 24, max 168 (7 days). Max 20 unexpired messages per user.

  ConnectorOAuth

• chat_with_influencerA

  VidGuyA

  Have a live conversation with the influencer's agent brain — the SAME persistent thread and memory as the dashboard Chat tab, so anything discussed here carries into its future posting. Advice-only toolset: it can discuss strategy, its vault, and its plans, but cannot publish from chat. SYNCHRONOUS and slow (typically 15–90s per reply; can approach 4 min) — send ONE message per call and wait. For fire-and-forget direction, prefer send_influencer_message.

  ConnectorOAuth

• structured_extractionA

  Shoon A2A Trust Services (pilot)A

  Turn messy text or a web page into structured data — headings, links, tables, word counts — without spending your own context window on parsing. Deterministic heuristics only: no LLM, no semantic understanding, fully reproducible output, plainly labeled as heuristic. It extracts structure, not meaning. Pass raw text (up to 100,000 characters) or a URL. FREE during the pilot — no API key, no payment header, no signup: just call this tool with arguments.input and the task runs immediately. Every deliverable is Ed25519-signed, so you can verify it offline and show your principal proof the check ran. Privacy: your input is processed in server memory only — never written to disk, never logged, never sold, never used for training; only event metadata (task queued/completed) is kept. In-memory state is wiped on restart; the event-metadata ledger and usage counters are on ephemeral disk and wiped only on redeploy. Fair use: 20 free tasks per service per day shared across pilot users — check GET /v1/slots for live availability.

  ConnectorNo auth

• list_26_systemsA

  mythsensus-mcpA

  Return the canonical list of 26 ancient divination systems Mythsensus implements (slug, English + Thai name, region, required inputs). Use first when asked "what systems do you support?".

  ConnectorNo auth

• propose_contextA

  Forge EngineA

  Propose a new/updated Idea note → Inbox. Title-match to update; send the COMPLETE revised text. Set resync:true ONLY when you rewrote the note FROM the current systems (get_stale lists notes the systems have moved past) — it stops the adopted note from immediately nagging to re-generate the systems it was just written from.

  ConnectorNo auth

• get_knowledge_statsA

  mcp-klever-vmA

  Get summary statistics of the Klever VM knowledge base. Returns total entry count, counts broken down by context type (code_example, best_practice, security_tip, etc.), and a sample entry title for each type. Useful for understanding what knowledge is available before querying.

  ConnectorNo auth

• thinkneo_read_memoryA

  ThinkNEO Control PlaneC

  Read Claude Code project memory files. Without arguments, returns the MEMORY.md index listing all available memories. With a filename argument, returns the full content of that specific memory file. Use this to access project context, user preferences, feedback, and reference notes persisted across Claude Code sessions.

  ConnectorNo auth

• get_messagesA

  Fast MCP TelegramA

  Read or search messages in one chat: browse latest, search text, fetch by ids, or load replies to a message (comments, forum topics, threads). Use from_user to filter by sender (server-side, per-chat only). Use context to include neighboring messages and reply chains around each result. Use include_replies to fetch up to 5 direct replies per result. Do not combine message_ids with query or reply_to_id. Success: messages, has_more, optional total_count and discussion fields. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md

  ConnectorNo auth

• get_messagesA

  fast-mcp-telegramA

  Read or search messages in one chat: browse latest, search text, fetch by ids, or load replies to a message (comments, forum topics, threads). Use from_user to filter by sender (server-side, per-chat only). Use context to include neighboring messages and reply chains around each result. Use include_replies to fetch up to 5 direct replies per result. Do not combine message_ids with query or reply_to_id. Success: messages, has_more, optional total_count and discussion fields. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md

  ConnectorNo auth