ctx: The missing link between your codebase and your LLM. Context as Code (CaC) tool with MCP server inside.

Created By
context-huba year ago
CTX: The missing link between your codebase and your LLM. Context as Code (CaC) tool with MCP server inside.
Overview

What is ctx?

ctx is a Context as Code (CaC) tool designed to bridge the gap between your codebase and large language models (LLMs) like ChatGPT and Claude by providing them with the necessary context about your project.

How to use ctx?

To use ctx, install the tool via a simple command, initialize a configuration file, describe your project structure, and then generate context files that can be shared with LLMs for better assistance.

Key features of ctx?

  • Automatically builds organized context files from various sources including code files, GitHub repositories, and web pages.
  • Supports seamless integration with AI models through a built-in MCP server.
  • Facilitates documentation generation and code refactoring assistance.

Use cases of ctx?

  1. Providing context for AI-assisted code refactoring.
  2. Generating comprehensive documentation from codebases.
  3. Enabling real-time AI assistance by connecting directly to LLMs.

FAQ from ctx?

  • Can ctx work with any programming language?

While ctx is primarily designed for PHP, it can be adapted for other languages by modifying the configuration.

  • Is ctx free to use?

Yes! ctx is open-source and free to use.

  • How does ctx improve AI interactions?

By providing structured context, ctx allows LLMs to give more accurate and relevant responses based on your specific codebase.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
context-hub
Star
95
Language
PHP
License
MIT license
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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