local-llm-obsidian-knowledge-base

What is local-llm-obsidian-knowledge-base?

A template repository with a dev container for running a local LLM and an included knowledge base. It enables updating the knowledge base via an MCP Client/Server relationship, for example using the VS Code extension Cline and the Filesystem or Obsidian-MCP MCP servers.

How to use local-llm-obsidian-knowledge-base?

Clone the repository, add a git repo using git subtree or git submodule, and update the knowledge base through an MCP client like Cline.

Key features of local-llm-obsidian-knowledge-base

• Dev container preconfigured for local LLM
• Bundled knowledge base template
• Updates knowledge via MCP Client/Server
• Works with Cline VS Code extension
• Supports Filesystem and Obsidian-MCP MCP servers

Use cases of local-llm-obsidian-knowledge-base

• Running a local LLM with a custom knowledge base
• Iteratively updating knowledge from a git repository using MCP
• Developing and interacting with a local LLM inside VS Code with Cline

FAQ from local-llm-obsidian-knowledge-base

What is the purpose of this template?

It provides a ready-to-use dev container for running a local LLM alongside a knowledge base that can be updated via MCP.

How do I add my own knowledge source?

Add a git repository to the template using git subtree or git submodule.

Which MCP servers are supported?

The template specifically mentions the Filesystem and Obsidian-MCP MCP servers.

Which client is recommended for updating the knowledge base?

The Cline extension for VS Code is given as an example of an MCP client that can interact with the servers.

Does this template include a specific local LLM?

The README states it includes a dev container for "running a local LLM" but does not name a specific model or provider.