Constellation

Created By
ShiftinBitsa month ago
Your AI agents don't understand your codebase. Upgrade from text search to code understanding. AI coding agents waste most of their context window grepping files and guessing at code structure. Constellation gives them a persistent, team-wide knowledge graph of your codebase (symbol search, dependency graphs, impact analysis) delivered via MCP so every token goes toward reasoning, not discovery.
Overview

Graph-backed code intelligence for your AI assistant.

Constellation turns your codebase into a queryable knowledge graph, giving AI assistants the structural understanding they need to reason about real software — not just the plain text.

Why Constellation?

Text search tells you where a string appears, everywhere that string appears. Constellation tells you the exact location of the symbol in question, what it means, what calls it, and what breaks if you change it. Before your assistant edits a function, it can ask:

  • Where is this defined, and where is it used across the codebase?
  • What's the blast radius of this change?
  • Which modules have circular dependencies or dead code?
  • How does data flow through the call graph?

Answers come from a semantic graph, not a grep loop.

One Tool, Countless Capabilities

A single code_intel tool exposes a rich JavaScript API as a "Code Mode" tool. Your assistant composes queries like code:

const { symbols } = await api.searchSymbols({ query: "AuthService" });
const [impact, deps] = await Promise.all([
  api.impactAnalysis({ symbolId: symbols[0].id }),
  api.getDependents({ filePath: symbols[0].filePath })
]);

Built for Real Codebases

  • Multi-language: TypeScript, JavaScript, Python, and more coming soon.
  • Multi-project: Auto-resolves per-project config by git root with LRU caching.
  • Fast: Parallel API calls, rich source snippets returned inline, no follow-up file reads needed.
  • Safe: Hardened sandbox mode runs queries in an isolated child process with hard memory limits.

Privacy by Design

Your source code never leaves your machine. Constellation parses to a compressed AST locally; only structural metadata reaches the service. Access keys scope each project to its own namespace.

Server Config

{
  "mcpServers": {
    "constellation": {
      "command": "npx",
      "args": [
        "-y",
        "@constellationdev/mcp@latest"
      ],
      "env": {
        "CONSTELLATION_ACCESS_KEY": "${CONSTELLATION_ACCESS_KEY}"
      }
    }
  }
}
Project Info
Created At
a month ago
Updated At
a month ago
Author Name
ShiftinBits
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago