Koncept Mcp Server

io.github.yourtechtribe-labsPublished by GitHub account yourtechtribe-labsv0.2.0-alpha.7Updated Oct 24, 2026

Query a curated YAML semantic concept graph for codebase invariants and cross-cutting facts.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A local MCP server that lets an assistant query a curated YAML concept graph of a codebase's semantic invariants and cross-cutting facts.

What you can do
Query the curated YAML concept graph for semantic invariants and cross-cutting facts about a codebase, such as rules that span files not linked by imports. Surface concepts relevant to a given file so an assistant can read them before editing. The README describes four MCP tools and a companion CLI for initializing, verifying, listing and linking concepts, including enforced invariant checks.
When to use it
Useful when a codebase has cross-cutting rules or conventions that structural code graphs miss and you want an assistant to consult them before making changes. Best suited to teams willing to maintain concept files in YAML.
Requirements
Runs as a local stdio process started via npx from the npm package, with the project path passed as an argument. The README's setup also uses a companion CLI package and a .koncept/concepts directory of YAML files. No authentication, environment variables or headers are declared.
Before you install
The README labels the project pre-alpha and warns that the schema and tool surface may break before a final release. Concept files are read from the project directory, so review them before relying on them. The README mentions a shell command check kind that runs only through the CLI, not the MCP server.

Installation

In SourceWeft

  1. Open Koncept Mcp Server 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

koncepto

Semantic concept graph MCP server for codebases — what your code means, not just what it does.

[Status] [License] [pnpm] [OpenSSF Scorecard]

What

Code graphs (Aider repomap, GitNexus, Sourcegraph) capture structural relations: who imports who, who calls who. They miss semantic invariants — the cross-cutting concepts that live in code not related by imports:

  • "Fix B" lives in 7 files but isn't a function or a class
  • "All UI counting workload must exclude manual-override participants"
  • "Sector value strings must match SectorAssignment.sector keys exactly"

koncepto is the curated semantic layer. Concepts in YAML, queryable via MCP tools, read at Step 0 before editing.

Status

Pre-alpha (v0.1.0-alpha.3 on npm). Schema and tool surface may break before 0.1.0 final. See roadmap.

Dogfooded against this repo itself: 5 concepts in .koncept/concepts/ cover the schema, the registry, the MCP tool contract, the monorepo shape, and the kebab-id naming convention. pnpm dogfood = koncepto verify against its own registry.

Quickstart

bash
# Install in your projectpnpm add -D @yourtechtribe-labs/koncept-cli@alpha
# Bootstrapnpx koncepto init
# Write a concept (YAML)$EDITOR .koncept/concepts/my-concept.yaml
# Verifynpx koncepto verify
# Register MCP server (Claude Code)claude mcp add --scope user koncepto -- \  npx -y @yourtechtribe-labs/koncept-mcp-server@alpha "$PWD"

Enforced invariants

An invariant is advisory by default — surfaced to agents via koncept_for_file, but never evaluated. Give it a check and it becomes an enforced gate that koncepto verify fails on:

yaml
invariants:  - id: invalidate-projection-cache    description: A standalone sync that invalidates the banking cache must also      invalidate the projection cache, or the /cashflow opening balance goes stale.    severity: high    check:      kind: implication        # per participant file: if it matches `if`, it must also match `then`      over: { role: writer }      if: "BankingCacheService"      then: "CacheInvalidationService|on_full_sync"

Static kinds (implication, symbol_present, forbidden, grep) run on koncepto verify by default (fast, read-only; --no-checks to skip). The shell escape hatch (kind: command) runs only on koncepto check. This turns a "completion-contract" concept into both the checklist and its enforcement gate — the loose end can't be skipped under momentum.

Architecture

3 packages under pnpm workspace:

  • @yourtechtribe-labs/koncept-core — Zod schema, YAML parser, indexer
  • @yourtechtribe-labs/koncept-mcp-server — MCP stdio server (4 tools)
  • @yourtechtribe-labs/koncept-cli — init, verify, list, link

License

MIT — see LICENSE.

Source: README.md at commit 6c804a1

Tools

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

Version history

1
  1. v0.2.0-alpha.7LatestSep 16, 2026

Score

50% 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
  • License10 pts