Turn internal code libraries into AI-accessible knowledge sources via MCP server with semantic search
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"simplecode-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# SimpleCodeMCP **Turn your internal code libraries into AI-accessible knowledge sources.** SimpleCodeMCP is an open-source tool that indexes internal code libraries and exposes them through a Model Context Protocol (MCP) server. This enables AI coding agents (Claude, GitHub Copilot, etc.) to provide precise, context-aware assistance for company-internal libraries—even when documentation is sparse or outdated. ## The Problem In many organizations: - **Team A** builds internal libraries (e.g., `pythonpackage1`) - **Team B** uses these libraries to implement new software - Documentation is often incomplete, outdated, or missing - This leads to frequent misuse, implementation errors, and repeated questions ## The Solution SimpleCodeMCP scans and indexes your internal library's: - Public and internal APIs - Function/class signatures and type hints - Docstrings and comments - Tests (as usage examples) - Code structure and relationships It then exposes this knowledge through an MCP server that AI agents can query to: - List available functions and classes - Inspect signatures and behavior - Retrieve real usage examples from tests - Search relevant parts of the codebase semantically ## Architecture ``` ┌─────────────────────────────────────────────────────────┐ │ Your Library Repository │ │ ├── src/ (source code) │ │ ├── tests/ (usage examples) │ │ └── examples/ (additional examples) │ └────────────────────┬────────────────────────────────────┘ │ ▼ ┌──────────────────────┐ │ Indexer Component │ │ ───────────────── │ │ • AST Parser │ Extract structure │ • Docstring Parser │ Extract documentation │ • Test Parser │ Find usage patterns │ • Static Analyzer │ Infer types & relationships └──────────┬──────────…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.