basic-memory 0.8.0__py3-none-any.whl → 0.10.0__py3-none-any.whl

basic_memory/mcp/tools/memory.py

@@ -1,177 +0,0 @@
-"""Discussion context tools for Basic Memory MCP server."""
-
-from typing import Optional, List
-
-from loguru import logger
-import logfire
-
-from basic_memory.mcp.async_client import client
-from basic_memory.mcp.server import mcp
-from basic_memory.mcp.tools.utils import call_get
-from basic_memory.schemas.memory import (
-    GraphContext,
-    MemoryUrl,
-    memory_url_path,
-    normalize_memory_url,
-)
-from basic_memory.schemas.base import TimeFrame
-from basic_memory.schemas.search import SearchItemType
-
-
-@mcp.tool(
-    description="""Build context from a memory:// URI to continue conversations naturally.
-    
-    Use this to follow up on previous discussions or explore related topics.
-    Timeframes support natural language like:
-    - "2 days ago"
-    - "last week" 
-    - "today"
-    - "3 months ago"
-    Or standard formats like "7d", "24h"
-    """,
-)
-async def build_context(
-    url: MemoryUrl,
-    depth: Optional[int] = 1,
-    timeframe: Optional[TimeFrame] = "7d",
-    page: int = 1,
-    page_size: int = 10,
-    max_related: int = 10,
-) -> GraphContext:
-    """Get context needed to continue a discussion.
-
-    This tool enables natural continuation of discussions by loading relevant context
-    from memory:// URIs. It uses pattern matching to find relevant content and builds
-    a rich context graph of related information.
-
-    Args:
-        url: memory:// URI pointing to discussion content (e.g. memory://specs/search)
-        depth: How many relation hops to traverse (1-3 recommended for performance)
-        timeframe: How far back to look. Supports natural language like "2 days ago", "last week"
-        page: Page number of results to return (default: 1)
-        page_size: Number of results to return per page (default: 10)
-        max_related: Maximum number of related results to return (default: 10)
-
-    Returns:
-        GraphContext containing:
-            - primary_results: Content matching the memory:// URI
-            - related_results: Connected content via relations
-            - metadata: Context building details
-
-    Examples:
-        # Continue a specific discussion
-        build_context("memory://specs/search")
-
-        # Get deeper context about a component
-        build_context("memory://components/memory-service", depth=2)
-
-        # Look at recent changes to a specification
-        build_context("memory://specs/document-format", timeframe="today")
-
-        # Research the history of a feature
-        build_context("memory://features/knowledge-graph", timeframe="3 months ago")
-    """
-    with logfire.span("Building context", url=url, depth=depth, timeframe=timeframe):  # pyright: ignore [reportGeneralTypeIssues]
-        logger.info(f"Building context from {url}")
-        url = normalize_memory_url(url)
-        response = await call_get(
-            client,
-            f"/memory/{memory_url_path(url)}",
-            params={
-                "depth": depth,
-                "timeframe": timeframe,
-                "page": page,
-                "page_size": page_size,
-                "max_related": max_related,
-            },
-        )
-        return GraphContext.model_validate(response.json())
-
-
-@mcp.tool(
-    description="""Get recent activity from across the knowledge base.
-    
-    Timeframe supports natural language formats like:
-    - "2 days ago"  
-    - "last week"
-    - "yesterday" 
-    - "today"
-    - "3 weeks ago"
-    Or standard formats like "7d"
-    """,
-)
-async def recent_activity(
-    type: Optional[List[SearchItemType]] = None,
-    depth: Optional[int] = 1,
-    timeframe: Optional[TimeFrame] = "7d",
-    page: int = 1,
-    page_size: int = 10,
-    max_related: int = 10,
-) -> GraphContext:
-    """Get recent activity across the knowledge base.
-
-    Args:
-        type: Filter by content type(s). Valid options:
-            - ["entity"] for knowledge entities
-            - ["relation"] for connections between entities
-            - ["observation"] for notes and observations
-            Multiple types can be combined: ["entity", "relation"]
-        depth: How many relation hops to traverse (1-3 recommended)
-        timeframe: Time window to search. Supports natural language:
-            - Relative: "2 days ago", "last week", "yesterday"
-            - Points in time: "2024-01-01", "January 1st"
-            - Standard format: "7d", "24h"
-        page: Page number of results to return (default: 1)
-        page_size: Number of results to return per page (default: 10)
-        max_related: Maximum number of related results to return (default: 10)
-
-    Returns:
-        GraphContext containing:
-            - primary_results: Latest activities matching the filters
-            - related_results: Connected content via relations
-            - metadata: Query details and statistics
-
-    Examples:
-        # Get all entities for the last 10 days (default)
-        recent_activity()
-
-        # Get all entities from yesterday
-        recent_activity(type=["entity"], timeframe="yesterday")
-
-        # Get recent relations and observations
-        recent_activity(type=["relation", "observation"], timeframe="today")
-
-        # Look back further with more context
-        recent_activity(type=["entity"], depth=2, timeframe="2 weeks ago")
-
-    Notes:
-        - Higher depth values (>3) may impact performance with large result sets
-        - For focused queries, consider using build_context with a specific URI
-        - Max timeframe is 1 year in the past
-    """
-    with logfire.span("Getting recent activity", type=type, depth=depth, timeframe=timeframe):  # pyright: ignore [reportGeneralTypeIssues]
-        logger.info(
-            f"Getting recent activity from {type}, depth={depth}, timeframe={timeframe}, page={page}, page_size={page_size}, max_related={max_related}"
-        )
-        params = {
-            "page": page,
-            "page_size": page_size,
-            "max_related": max_related,
-        }
-        if depth:
-            params["depth"] = depth
-        if timeframe:
-            params["timeframe"] = timeframe  # pyright: ignore
-
-        # send enum values if we have an enum, else send string value
-        if type:
-            params["type"] = [  # pyright: ignore
-                type.value if isinstance(type, SearchItemType) else type for type in type
-            ]
-
-        response = await call_get(
-            client,
-            "/memory/recent",
-            params=params,
-        )
-        return GraphContext.model_validate(response.json())

basic_memory/mcp/tools/notes.py

@@ -1,201 +0,0 @@
-"""Note management tools for Basic Memory MCP server.
-
-These tools provide a natural interface for working with markdown notes
-while leveraging the underlying knowledge graph structure.
-"""
-
-from typing import Optional, List
-
-from loguru import logger
-import logfire
-
-from basic_memory.mcp.server import mcp
-from basic_memory.mcp.async_client import client
-from basic_memory.schemas import EntityResponse, DeleteEntitiesResponse
-from basic_memory.schemas.base import Entity
-from basic_memory.mcp.tools.utils import call_get, call_put, call_delete
-from basic_memory.schemas.memory import memory_url_path
-
-
-@mcp.tool(
-    description="Create or update a markdown note. Returns a markdown formatted summary of the semantic content.",
-)
-async def write_note(
-    title: str,
-    content: str,
-    folder: str,
-    tags: Optional[List[str]] = None,
-) -> str:
-    """Write a markdown note to the knowledge base.
-
-    The content can include semantic observations and relations using markdown syntax.
-    Relations can be specified either explicitly or through inline wiki-style links:
-
-    Observations format:
-        `- [category] Observation text #tag1 #tag2 (optional context)`
-
-        Examples:
-        `- [design] Files are the source of truth #architecture (All state comes from files)`
-        `- [tech] Using SQLite for storage #implementation`
-        `- [note] Need to add error handling #todo`
-
-    Relations format:
-        - Explicit: `- relation_type [[Entity]] (optional context)`
-        - Inline: Any `[[Entity]]` reference creates a relation
-
-        Examples:
-        `- depends_on [[Content Parser]] (Need for semantic extraction)`
-        `- implements [[Search Spec]] (Initial implementation)`
-        `- This feature extends [[Base Design]] and uses [[Core Utils]]`
-
-    Args:
-        title: The title of the note
-        content: Markdown content for the note, can include observations and relations
-        folder: the folder where the file should be saved
-        tags: Optional list of tags to categorize the note
-
-    Returns:
-        A markdown formatted summary of the semantic content, including:
-        - Creation/update status
-        - File path and checksum
-        - Observation counts by category
-        - Relation counts (resolved/unresolved)
-        - Tags if present
-    """
-    with logfire.span("Writing note", title=title, folder=folder):  # pyright: ignore [reportGeneralTypeIssues]
-        logger.info(f"Writing note folder:'{folder}' title: '{title}'")
-
-        # Create the entity request
-        metadata = {"tags": [f"#{tag}" for tag in tags]} if tags else None
-        entity = Entity(
-            title=title,
-            folder=folder,
-            entity_type="note",
-            content_type="text/markdown",
-            content=content,
-            entity_metadata=metadata,
-        )
-
-        # Create or update via knowledge API
-        logger.info(f"Creating {entity.permalink}")
-        url = f"/knowledge/entities/{entity.permalink}"
-        response = await call_put(client, url, json=entity.model_dump())
-        result = EntityResponse.model_validate(response.json())
-
-        # Format semantic summary based on status code
-        action = "Created" if response.status_code == 201 else "Updated"
-        summary = [
-            f"# {action} {result.file_path} ({result.checksum[:8] if result.checksum else 'unknown'})",
-            f"permalink: {result.permalink}",
-        ]
-
-        if result.observations:
-            categories = {}
-            for obs in result.observations:
-                categories[obs.category] = categories.get(obs.category, 0) + 1
-
-            summary.append("\n## Observations")
-            for category, count in sorted(categories.items()):
-                summary.append(f"- {category}: {count}")
-
-        if result.relations:
-            unresolved = sum(1 for r in result.relations if not r.to_id)
-            resolved = len(result.relations) - unresolved
-
-            summary.append("\n## Relations")
-            summary.append(f"- Resolved: {resolved}")
-            if unresolved:
-                summary.append(f"- Unresolved: {unresolved}")
-                summary.append("\nUnresolved relations will be retried on next sync.")
-
-        if tags:
-            summary.append(f"\n## Tags\n- {', '.join(tags)}")
-
-        return "\n".join(summary)
-
-
-@mcp.tool(description="Read note content by title, permalink, relation, or pattern")
-async def read_note(identifier: str, page: int = 1, page_size: int = 10) -> str:
-    """Get note content in unified diff format.
-
-    The content is returned in a unified diff inspired format:
-    ```
-    --- memory://docs/example 2025-01-31T19:32:49 7d9f1c8b
-    <document content>
-    ```
-
-    Multiple documents (from relations or pattern matches) are separated by
-    additional headers.
-
-    Args:
-        identifier: Can be one of:
-            - Note title ("Project Planning")
-            - Note permalink ("docs/example")
-            - Relation path ("docs/example/depends-on/other-doc")
-            - Pattern match ("docs/*-architecture")
-        page: the page number of results to return (default 1)
-        page_size: the number of results to return per page (default 10)
-
-    Returns:
-        Document content in unified diff format. For single documents, returns
-        just that document's content. For relations or pattern matches, returns
-        multiple documents separated by unified diff headers.
-
-    Examples:
-        # Single document
-        content = await read_note("Project Planning")
-
-        # Read by permalink
-        content = await read_note("docs/architecture/file-first")
-
-        # Follow relation
-        content = await read_note("docs/architecture/depends-on/docs/content-parser")
-
-        # Pattern matching
-        content = await read_note("docs/*-architecture")  # All architecture docs
-        content = await read_note("docs/*/implements/*")  # Find implementations
-
-    Output format:
-        ```
-        --- memory://docs/example 2025-01-31T19:32:49 7d9f1c8b
-        <first document content>
-
-        --- memory://docs/other 2025-01-30T15:45:22 a1b2c3d4
-        <second document content>
-        ```
-
-    The headers include:
-    - Full memory:// URI for the document
-    - Last modified timestamp
-    - Content checksum
-    """
-    with logfire.span("Reading note", identifier=identifier):  # pyright: ignore [reportGeneralTypeIssues]
-        logger.info(f"Reading note {identifier}")
-        url = memory_url_path(identifier)
-        response = await call_get(
-            client, f"/resource/{url}", params={"page": page, "page_size": page_size}
-        )
-        return response.text
-
-
-@mcp.tool(description="Delete a note by title or permalink")
-async def delete_note(identifier: str) -> bool:
-    """Delete a note from the knowledge base.
-
-    Args:
-        identifier: Note title or permalink
-
-    Returns:
-        True if note was deleted, False otherwise
-
-    Examples:
-        # Delete by title
-        delete_note("Meeting Notes: Project Planning")
-
-        # Delete by permalink
-        delete_note("notes/project-planning")
-    """
-    with logfire.span("Deleting note", identifier=identifier):  # pyright: ignore [reportGeneralTypeIssues]
-        response = await call_delete(client, f"/knowledge/entities/{identifier}")
-        result = DeleteEntitiesResponse.model_validate(response.json())
-        return result.deleted