MCP.so
ログイン

Constellation MCP Server

@ShiftinBits

基本情報

カテゴリ

メモリとナレッジ

トランスポート

stdio

作者

ShiftinBits

投稿者

Bobby Bonestell

Constellation MCP Server について

Your AI agents don't understand your codebase. Upgrade from text search to code understanding.

#code#context#codegraph#navigation#intelligence#constellation#shiftinbits

Constellation MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "constellation": {
      "command": "npx",
      "args": [
        "-y",
        "@constellationdev/mcp@latest"
      ],
      "env": {
        "CONSTELLATION_ACCESS_KEY": "${CONSTELLATION_ACCESS_KEY}"
      }
    }
  }
}

Constellation MCP Server のツール

1

DECISION RULE: Structure questions → this tool. Text search → Grep. Before using Grep, ask: Is this a STRUCTURE question (definitions, callers, impact) or a TEXT question (strings, config)? QUICK START: `return await api.searchSymbols({query: "AuthService"})` — simple queries are one-liners. Run `api.listMethods()` for full API reference with signatures and descriptions. Run `api.help("methodName")` for inline TypeScript type definitions — no resource reads needed. Compose: `const [impact, deps] = await Promise.all([api.impactAnalysis({symbolId}), api.getDependents({filePath})]);` WHY THIS TOOL: Graph-backed intelligence finds indirect relationships, transitive dependencies, and breaking change risks that text search cannot detect. "What uses X?" disambiguation: getDependents (file imports) vs getCallGraph (call chain) vs traceSymbolUsage (all usages). USE IMMEDIATELY WHEN: • BEFORE using Edit on a function/class → run impactAnalysis({symbolId}) first • BEFORE exploring an unfamiliar codebase → run getArchitectureOverview() • BEFORE refactoring → trace getDependencies + getDependents for blast radius • Running 3+ Grep calls for structure? STOP → use code_intel instead TOP 5 QUESTIONS (query is case-insensitive substring match): • "Where is X defined?" / "Find function Y" → searchSymbols({query}) • "What calls X?" / "What imports this?" → getDependents({filePath}) or getCallGraph({symbolId}) • "What does X depend on?" → getDependencies({filePath}) • "Safe to modify X?" / "Blast radius?" → impactAnalysis({symbolId}) • "Find dead code" / "Unused exports?" → findOrphanedCode() • "Complex functions?" / "Refactoring targets?" → searchSymbols results include complexity.cyclomaticComplexity + complexityRisk per function NOT FOR: literal string search, log messages, config values, or reading source code. Use Grep/Glob/Read for those. Supports TypeScript, JavaScript, Python, and more — run api.getCapabilities() to check your project. WRONG TOOL SIGNAL: If you've run 3+ Grep calls for structure (callers, dependencies, impact), STOP and use code_intel instead. Typical workflow: code_intel to find (results include source snippets) → Edit to modify IMPORTANT: The `cwd` parameter is required — always set it to the target project directory path.

概要

What is Constellation?

Constellation turns your codebase into a queryable code graph. AI assistants get real structural understanding of your software (definitions, callers, dependencies, impact) instead of guessing from text matches.

How to use Constellation?

Index your project with the Constellation CLI, then call the single code_intel tool. The assistant writes short JavaScript against the api object (for example api.searchSymbols, api.getDependents, api.impactAnalysis) and can chain or parallelize calls to answer complex questions in one round trip.

Key features of Constellation

  • Graph-backed answers, not token-wasting a grep loop
  • One code_intel tool with a composable JavaScript API
  • Multi-project workspaces, resolved by git root
  • Fast: parallel queries, inline source snippets
  • Sandboxed execution with memory limits
  • Privacy by design: source code never leaves your environment

Use cases of Constellation

  • Find where a symbol is defined and everywhere it's used
  • Gauge the blast radius of a change before editing
  • Detect circular dependencies and dead code
  • Trace execution through the call graph

よくある質問

1

How is this different from text search?

Text search finds strings. Constellation knows what a symbol is, who calls it, and what breaks if it changes.

2

Does my source code leave my machine?

No. Code is parsed locally and only compressed structural metadata is uploaded.

3

How do I set it up?

Set `CONSTELLATION_ACCESS_KEY` and add the server via `npx -y @constellationdev/mcp`, or install an official Constellation plugin (recommended). Setup guides: https://docs.constellationdev.io/mcp/#installation

コメント

「メモリとナレッジ」の他のコンテンツ