Basic Memory MCP Server Extension for Zed Editor

Created By
ossfellowa year ago
Basic Memory MCP server integration, for Zed Editor's Assistant.
Overview

What is Basic Memory MCP Server Extension for Zed?

This extension integrates Basic Memory as a context server for Zed Editor's Assistant, allowing users to build persistent knowledge through natural conversations with Large Language Models while keeping everything in simple Markdown files on their computer.

How to use Basic Memory MCP Server Extension?

To use the extension, install the required dependencies (Python 3.12+ and uv), then install the extension in Zed and configure it in your Zed settings. Once configured, you can interact with Basic Memory through the Zed Assistant using various prompts.

Key features of Basic Memory MCP Server Extension?

  • Integration with Zed Editor's Assistant for enhanced note-taking.
  • Support for multiple projects to manage different knowledge bases.
  • Ability to create and search notes using natural language prompts.

Use cases of Basic Memory MCP Server Extension?

  1. Creating notes on software architecture patterns.
  2. Searching for information about specific programming concepts.
  3. Maintaining separate knowledge bases for different projects or subjects.

FAQ from Basic Memory MCP Server Extension?

  • What are the prerequisites for using this extension?

You need Python 3.12+ and the uv tool installed.

  • Is the extension currently functional?

The extension requires Zed to support MCP tools, which is still in development. Its functionality will be available in a future update.

  • Can I use Basic Memory for multiple projects?

Yes! Basic Memory supports multiple projects to help you organize your notes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ossfellow
Star
0
Language
Rust
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago