Codeweaver

com.knitliPublished by knitli.comv0.1.0-alpha.3Updated Oct 24, 2026

Semantic code search built for AI agents. Hybrid, AST-aware, context for 166 languages.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Codeweaver is a local MCP server that gives an AI assistant semantic, AST-aware code search across a project, covering 166 languages.

What you can do
Search a codebase semantically rather than by exact text, using hybrid retrieval over code structure and meaning. Work across 166 languages with AST-aware indexing that understands code structure. Configure embedding, reranking, sparse-embedding and vector-store providers to tune how results are retrieved. Point it at a specific project path or name so the assistant searches the right codebase.
When to use it
Useful when an assistant needs to find relevant code in a large or unfamiliar repository where keyword search falls short, and you want retrieval quality improved with embeddings and reranking.
Requirements
Runs locally as a stdio process, launched with uvx from the code-weaver PyPI package or from the Docker image. Needs a project path and a chosen embedding, reranking and vector-store provider; API keys for those providers are supplied through environment variables such as CODEWEAVER_EMBEDDING_API_KEY, CODEWEAVER_RERANKING_API_KEY and CODEWEAVER_VECTOR_STORE_API_KEY, or through cloud provider credentials for AWS Bedrock, Azure OpenAI, Azure Cohere or Vercel AI Gateway.
Before you install
Several secret environment variables are requested, including cloud credentials such as AWS_SECRET_ACCESS_KEY and provider keys for Azure OpenAI, Azure Cohere, Vercel and the embedding, reranking and vector-store services. Code and queries may be sent to whichever embedding, reranking or vector-store provider you configure, so check that provider's data handling before indexing private repositories.

Installation

In SourceWeft

  1. Open Codeweaver in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0-alpha.3LatestSep 16, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts