Skip to main content
Glama
space-bacon

Sunstone Weave: Local Semantic Code Search

by space-bacon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Sunstone Weave: Local Semantic Code Search

Related Servers

  • Bismut Vector MCP

    QkartBismuth
    A
    license
    A
    quality
    B
    maintenance
    Enables any MCP client to index files, directories, and arbitrary text into a local SQLite-backed vector database and perform semantic search with language-aware chunking, filters, and context expansion, all offline without network calls.
    10
    MIT

  • local-notes-search-mcp

    Furkiozknn
    A
    license
    A
    quality
    B
    maintenance
    Enables natural-language semantic search over your own local files through an MCP server, fully offline without API keys or a server daemon, with optional LLM-grounded answers and exact file:line sources.
    5
    MIT

  • mcp-local-rag

    roilanrodriguez55
    A
    license
    A
    quality
    B
    maintenance
    Enables developers to index and search their own local PDF, DOCX, Markdown, and text documents from an MCP client or terminal, combining semantic similarity with keyword matching for exact technical terms. Everything runs on the user's machine with no API key, Docker, or external database, so private documents stay private and work offline after the initial model download.
    9
    2,150 npm
    MIT

  • code-search

    amolchanov
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables semantic code search across indexed code folders using vector embeddings, with support for multiple embedding providers and automatic file watching. Provides an admin UI and integrates with MCP clients for natural language code queries.
    1
    MIT

  • rag-mcp

    MasihMoafi
    A
    license
    Not graded
    quality
    B
    maintenance
    A local hybrid-search MCP server that enables coding agents to query files and folders using natural language, returning relevant code chunks with exact source paths. Everything runs on-device with no API keys or network calls.
    7
    MIT
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool maps to a distinct operation in the indexing lifecycle: index (weave_folder), query (weave_search), inspect (weave_list), and remove (weave_forget). There is no meaningful overlap, and the descriptions reinforce when to use each (e.g. search before grep).

Naming Consistency4/5

The weave_ prefix is applied uniformly, giving a clear namespace. Suffixes are mostly verbs (search, list, forget) except weave_folder, which is a noun referring to the resource it indexes, a minor deviation but still readable and predictable.

Tool Count4/5

Four tools is a tight, well-scoped set for a semantic-index server: create, query, enumerate, and delete. It is on the lean side with no configuration or content-retrieval tool, but each tool earns its place and nothing feels redundant.

Completeness4/5

The index lifecycle is fully covered: build/refresh (weave_folder), search (weave_search), list (weave_list), and delete (weave_forget), with re-indexing handled by weave_folder's incremental behavior. Minor gap: no tool to fetch a passage's or file's contents directly, so agents must fall back on other file-reading tools after a search hit.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources