About local-llm-obsidian-knowledge-base
A template repository for a dev container that runs a local LLM alongside an included knowledge base. It is intended for users who want to add a Git repository with `git subtree` or `git submodule` and update it through an MCP client/server setup.
Key features
- 01Dev container template
- 02Local LLM and included knowledge base
- 03Git subtree or submodule support
- 04MCP-based content updates
Use cases
- 01Starting a local LLM and knowledge base environment
- 02Adding a separate Git repository as knowledge-base content
- 03Updating repository content through an MCP client
MCP support
Describes updating the included knowledge base through an MCP client/server relationship, citing the `Filesystem` and `Obsidian-MCP` servers.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMElocal-llm-obsidian-knowledge-base
A template repository that includes a dev container for running a local LLM and included knowledge base. Add a git repo using git subtree or git submodule and update it using an MCP Client/Server relationship i.e. VS Code extension like Cline and the Filesystem/Obsidian-MCP MCP server.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.