Semantic code search and analysis from CodeAlive for AI assistants and agents.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Connect your AI assistant to CodeAlive's powerful code understanding platform in seconds!
This MCP (Model Context Protocol) server enables AI clients like Claude Code, Cursor, Claude Desktop, Continue, VS Code (GitHub Copilot), Cline, Codex, OpenCode, SourceCraft Code Assistant, SourceCraft CLI, Zed, KodaCode, GigaCode, Qwen Code, Gemini CLI, Roo Code, Goose, Kilo Code, Windsurf, Kiro, Qoder, n8n, and Amazon Q Developer to access CodeAlive's advanced semantic code search and codebase interaction features.
CodeAlive is a Context Engine for large codebases, powered by graph-based retrieval and exposed through MCP. It gives AI agents like Cursor, Claude Code, Codex, and other MCP-compatible tools precise repository context instead of forcing them to read files blindly. In our RepoQA benchmark, CodeAlive + Qwen3.6 deep reached frontier-agent quality at ~25x lower model cost, and semantic search reduced captured tokens by 45%.
It's like Context7, but for your (large) codebases.
It allows AI-Coding Agents to:
Once connected, you'll have access to these powerful tools:
get_data_sources - List your indexed repositories and workspacessemantic_search - Canonical semantic search across indexed artifactsgrep_search - Exact literal or regex text search inside file content, plus literal file-name/path matching (returns files like Form.xml even when their content never mentions the name), with line-level previews for content matchesget_repository_ontology - Get repository-level orientation for one selected repositoryget_file_tree - Inspect a bounded file tree for one repositoryread_file - Read a repository-relative file path, optionally with a line rangefetch_artifacts - Load the full source for relevant search hits (missing or inaccessible identifiers are reported back, not silently dropped)get_artifact_relationships - Expand call graph, inheritance, and reference relationships for one artifactget_artifact_query_schema - Inspect supported ArtifactQuery entities, fields, and examplesquery_artifact_metadata - Run read-only metadata analytics across selected repositorieschat - Stateless, slower synthesized codebase Q&A; call only when explicitly requestedAfter setup, try these commands with your AI assistant:
get_data_sourcessemantic_searchgrep_searchsemantic_search/grep_search, then optionally uses chatsemantic_search and grep_search should be the default tools for most agents. chat is a slower stateless synthesis fallback that can take substantially longer than retrieval, and is usually unnecessary when an agent can run a multi-step workflow with ontology, search, fetch/read, relationships, ArtifactQuery, and local file reads. If your agent supports subagents, the highest-confidence path is to delegate a focused subagent that orchestrates semantic_search and grep_search first.
For an even better experience, install the CodeAlive Agent Skill alongside the MCP server. The MCP server gives your agent access to CodeAlive's tools; the skill teaches it the best workflows and query patterns to use them effectively.
For most agents (Cursor, Copilot, Gemini CLI, Codex, and 30+ others) β install the skill:
For Claude Code β install the plugin (recommended), which includes the skill plus Claude-specific enhancements:
The fastest way to get started - no installation required! Our remote MCP server at https://mcp.codealive.ai/api provides instant access to CodeAlive's capabilities.
Choose your client in the MCP integration guides and follow the current setup instructions there.
You may ask your AI agent to install the CodeAlive MCP server for you.
Then allow execution.
Client-specific configuration is maintained in the CodeAlive documentation so file paths, transports, and authentication guidance stay current.
Start here: MCP integration guides
| Client | Setup guide |
|---|---|
| Claude Code | Claude Code |
| Claude Desktop | Claude Desktop |
| Cursor | Cursor |
| Visual Studio Code | VS Code |
| Windsurf | Windsurf |
| Cline | Cline |
| Continue | Continue |
| Codex | Codex |
| Gemini CLI | Gemini CLI |
| Amazon Q Developer | Amazon Q |
| OpenCode | OpenCode |
| SourceCraft Code Assistant and SourceCraft CLI | SourceCraft |
| Zed | Zed |
| ChatGPT | ChatGPT |
| OpenClaw | OpenClaw |
| KodaCode, GigaCode, Roo Code, Goose, Kilo Code, Qwen Code, Kiro, Qoder, JetBrains AI Assistant, n8n, and more | Other agents |
For an unlisted client, use these generic connection details and adapt them to the client's MCP configuration format:
https://mcp.codealive.ai/apiAuthorization: Bearer YOUR_API_KEY_HEREFor a private deployment, replace the endpoint with your server's /api URL. See Self-Hosting for deployment guidance.
Connecting the server is half the setup. Coding agents may continue using their built-in search unless project instructions tell them to prefer CodeAlive. Ready-made rules for
AGENTS.md,CLAUDE.md, and client-specific instruction files are in Instructing Coding Agents.
For developers who want to customize or contribute to the MCP server.
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/codealive-mcp)<a href="https://allmcps.com/mcp/codealive-mcp"><img src="https://allmcps.com/api/badge/codealive-mcp?style=directory" alt="Codealive MCP on AllMCPs" /></a>