Skip to main content

Overview

Model Context Protocol (MCP) is an open standard developed by Anthropic that enables AI assistants to connect with external tools and data sources. MCP is now generally available across major development platforms including VS Code, JetBrains IDEs, and more. CodeAlive’s MCP server provides your AI assistant with deep, contextual understanding of your entire codebase through semantic search and intelligent code analysis.

Why Use CodeAlive MCP?

Deep Context

AI understands relationships across your entire codebase, not just individual files

Semantic Search

Find code by meaning and intent, not just keywords

Multi-Repository

Work seamlessly across multiple repositories in one session

Real-Time Updates

Always work with the latest indexed version of your code

Deployment Options

CodeAlive MCP can be deployed in three ways, depending on your needs:
  • URL: https://mcp.codealive.ai/api/
  • Best for: Quick setup, no infrastructure management
  • Requirements: CodeAlive API key
  • Supported Clients: All MCP-compatible AI assistants

2. Docker Container

  • Image: ghcr.io/codealive-ai/codealive-mcp:main
  • Best for: Enterprise environments, local development
  • Requirements: Docker, CodeAlive API key
  • Benefits: Network isolation, custom configuration

3. Self-Hosted Instance

  • Repository: CodeAlive MCP Server
  • Best for: Complete control, custom modifications
  • Requirements: Python 3.11+, infrastructure management
  • Benefits: Full customization, on-premise deployment

Getting Started

1

Get Your API Key

  1. Sign up or log in at app.codealive.ai
  2. Navigate to MCP & API
  3. Click ”+ Create API Key”
  4. Copy your key immediately (it won’t be displayed again)
  5. Store your API key securely
2

Index Your Repositories

  1. Go to Repositories in your dashboard
  2. Click Add Repository
  3. Connect your GitHub/GitLab/Bitbucket account
  4. Select repositories to index
  5. Wait for initial indexing (5-15 minutes)

Available MCP Tools

CodeAlive exposes three powerful tools through MCP:

get_data_sources

Lists all indexed repositories and workspaces available for querying. Use cases:
  • Verify repository access
  • Check indexing status
  • List available codebases
Semantic search across your indexed codebase. Find code by meaning and intent, not just keywords. Use cases:
  • Find implementation patterns
  • Locate specific functionality
  • Discover related code
  • Trace data flows

codebase_consultant

AI consultant with full project expertise. Enables contextual conversations about your code with deep understanding. Use cases:
  • Architecture explanations
  • Code reviews
  • Bug analysis
  • Documentation generation

Common Use Cases

You: "Explain how user authentication works in our system"

AI: [Searches for authentication code across repositories]
    [Maps out the complete auth flow]
    [Explains with actual code references]

Security & Privacy

CodeAlive MCP follows security best practices:
  • All connections are encrypted with TLS
  • API keys are never logged or stored in plain text
  • Repository access is controlled at the API key level
  • Self-hosted options available for sensitive codebases

Best Practices

Keep Repos Updated

Regularly sync repositories in your dashboard for accurate context

Use Specific Queries

Be precise with technical terms for better search results

Organize by Project

Use separate API keys for different projects or environments

Monitor Usage

Track API usage in your dashboard to optimize queries

Troubleshooting

Common causes:
  • Invalid or expired API key
  • Network connectivity problems
  • Incorrect MCP server URL
Solutions:
  1. Regenerate API key in dashboard
  2. Check network/firewall settings
  3. Verify URL is https://mcp.codealive.ai/api/
Common causes:
  • Repositories not indexed
  • API key lacks permissions
  • Indexing still in progress
Solutions:
  1. Check indexing status in dashboard
  2. Wait 5-15 minutes for initial indexing
  3. Verify API key has repository access
Common causes:
  • Large codebase searches
  • Broad/vague queries
  • Network latency
Solutions:
  1. Use more specific search queries
  2. Limit search to specific repositories
  3. Consider Docker or self-hosted deployment
For more solutions, see the Troubleshooting Guide.

Next Steps