Codealive Mcp
Connect CodeAlive semantic code search so your agent navigates large repos by meaning, not just filename greps.
Overview
io.github.CodeAlive-AI/codealive-mcp is an MCP server for the Build phase that brings CodeAlive semantic code search and analysis into AI coding agents via a stdio Docker-backed MCP package.
What is this MCP server?
- Semantic code search and analysis surfaced for AI assistants via MCP
- Docker OCI distribution ghcr.io/codealive-ai/codealive-mcp:2.0.5 with stdio transport
- Requires CODEALIVE_API_KEY from https://app.codealive.ai/ (MCP & API section)
- Version 2.0.5 from CodeAlive-AI/codealive-mcp GitHub repository
- runtimeHint docker for consistent agent host setup
- Server version 2.0.5
- OCI image ghcr.io/codealive-ai/codealive-mcp:2.0.5
- Required secret environment variable CODEALIVE_API_KEY
Community signal: 81 GitHub stars.
What problem does it solve?
Large repos overwhelm agents with shallow text search, so you waste sessions opening irrelevant files instead of finding the logic you need to change.
Who is it for?
Solo developers using CodeAlive who want MCP-native semantic navigation while building features in multi-service or monorepo projects.
Skip if: Builders without a CodeAlive account or those who only need public web search, not repository-aware analysis.
What do I get? / Deliverables
After you add the server with a CodeAlive API key, your agent can run semantic search and analysis aligned with CodeAlive’s index of your codebase.
- stdio MCP server wired to CodeAlive search and analysis APIs
- Agent sessions grounded in semantic matches across your codebase
- Reduced time lost to blind file grepping during feature work
Recommended MCP Servers
Journey fit
Build is canonical because the payoff is day-to-day implementation speed in real codebases, not growth analytics or launch distribution. Agent-tooling captures an MCP whose primary job is augmenting how coding agents explore and analyze repository structure.
How it compares
Semantic repo intelligence MCP, not a RedM docs server or warehouse pipeline controller.
Common Questions / FAQ
Who is io.github.CodeAlive-AI/codealive-mcp for?
It is for indie builders and agent-first developers who already use CodeAlive and want semantic code search exposed as MCP tools in their editor or CLI agent.
When should I use io.github.CodeAlive-AI/codealive-mcp?
Use it during Build agent-tooling sessions when you are exploring unfamiliar modules, tracing behavior, or planning edits across a large indexed repository.
How do I add io.github.CodeAlive-AI/codealive-mcp to my agent?
Create a CODEALIVE_API_KEY at app.codealive.ai, run ghcr.io/codealive-ai/codealive-mcp:2.0.5 with stdio (Docker runtimeHint), and register that MCP server in Claude Code, Cursor, or another compatible client.