"Connecting MCP Servers to a Local Project" matching MCP servers:

Two self-hosted MCP servers: manage a local model machine (Ollama pull/switch, LoRA training) and bridge to local Ollama/vLLM for pure language processing tasks (writing, summarizing, classifying, extraction) without giving the calling agent tools or file access.

A Model Context Protocol (MCP) server that enables AI applications to access and analyze local code repositories without manual uploads, providing file listing, content reading, code searching, and project structure analysis capabilities.

Enables local web crawling and scraping through MCP, providing tools to fetch pages as Markdown, extract structured data with CSS selectors, and capture full-page screenshots while managing a shared browser instance.

MCP server enabling Claude Code to capture screenshots of Windows applications through WSL2, allowing AI to diagnose UI errors and verify layouts.

Enables MCP-compatible AI clients to connect to a Windows machine for file operations, PowerShell execution, Git inspection, task management, memory, and skills.

Enables delegating mechanical or high-volume subtasks to a local LLM through an MCP tool, letting the assistant query the local model without using its own output tokens for content.

Project Memory stores decisions, evidence, outcomes and reviewed lessons in local SQLite. Assistants retrieve bounded context through three MCP tools. People follow and plan work in a live workspace with an overview, sprint board, decision history, readable documents, skills and project maps. Offline exports remain available.

A local-first Model Context Protocol server that provides LLM agents with structured access to e-commerce data (products, inventory, orders, sales analytics) using a realistic mock dataset, zero configuration, and a swappable DataProvider interface for live APIs.

Intent-based project documentation server that automatically maps natural language queries to the right sources (plans, todos, roadmap, docs) and provides comprehensive task management with dependency tracking, backlog promotion, and archival workflows.

A stateful MCP server that remembers what your AI agent has already seen.

A FastMCP server that exposes predefined artifacts as Resources and project lifecycle operations as Tools for creating, updating, deploying, debugging, testing, monitoring, and configuring projects with minimal token usage.

Provides a minimal MCP server with safe tools for AI assistants to search project files, read files, search local documentation, and run pre-approved checks within a single project directory.

A workspace of six MCP servers—grounded-cv (hybrid RAG with citations), repo-intel (GitHub repo intelligence), web-research (safe web search/extraction), ats-jobs (unified ATS job boards), outcome-ledger (durable task ledger), and coding-workflows (code review & planning)—purpose-built for agentic hiring evaluations.

A self-contained Claude Code plugin that profiles a project by running a fixed DAG to emit agent-facing context pages, a human/developer guide, and a queryable vectorstore.

Enables AI agents to operate an isolated local Chromium browser through MCP, with semantic snapshots, ref-based actions, search, research, crawling, and CDP access.

Enables coding agents in different editors and MCP clients to share messages, project context, notes, task ownership, handoffs, and advisory file claims through a local SQLite-backed coordination server. Supports MCP stdio, MCP Streamable HTTP, a JSON HTTP API, and a local CLI for multi-project agent collaboration.

Enables AI agents to query a repository's verified semantic model, including capabilities, ownership, contracts, constraints, impact, health, and verification status, without re-deriving project facts. It exposes read-only tools for inspecting, reasoning about, and verifying the provenance-tracked surface.

Enables multi-project workspaces to share structured notes, API contracts, and handoff messages via a local SQLite database, with versioning and read tracking.

Enables a small local LLM to build and maintain a project map by offloading event ID/date generation, batching, synchronization, recovery, and finalization to the server, so the model only decides what to read and how to classify.

A-MEM is a self-evolving memory system for coding agents that automatically organizes knowledge into a Zettelkasten-style graph with dynamic relationships, enabling semantic and structural search.