Overview
Connect ChatGPT to CodeAlive’s remote MCP server with browser OAuth. The older Custom GPT Actions integration remains available as an API-key fallback.Prerequisites
- ChatGPT Business, Enterprise, or Edu workspace with custom MCP apps enabled
- CodeAlive account (Sign up here)
- Indexed repositories in your CodeAlive dashboard
Integration Methods
- Custom MCP app (Recommended)
- Custom GPT Action (API key)
- Direct API Calls
Create a CodeAlive app in ChatGPT
1
Enable developer mode
A workspace admin enables Developer mode / Create custom MCP connectors under Workspace Settings → Permissions & Roles → Connected Data. Enterprise and Edu workspaces can grant this through RBAC.
2
Create the app
In Settings → Apps → Create, enter the CodeAlive MCP endpoint:Choose OAuth when ChatGPT asks for the authentication mechanism.
3
Authenticate and scan tools
Click Scan Tools, complete the CodeAlive browser sign-in and consent screen, then wait for ChatGPT to finish scanning. The app exposes read-only CodeAlive tools such as
get_data_sources, semantic_search, grep_search, and read_file.4
Test and publish
Select the draft app in a new chat and ask, “What CodeAlive repositories are available?” Workspace admins can publish the tested app and control access through ChatGPT’s app settings.
Each user authorizes their own CodeAlive access. Do not configure a shared API key for the MCP app.
Usage Examples
Code Search
Architecture Analysis
Code Generation
Advanced Configuration
Custom GPT Capabilities
Configure your GPT with specific capabilities:Rate Limiting
Be aware of rate limits:- ChatGPT has limits on Actions calls per conversation
- CodeAlive API has rate limits based on your plan
- Use specific queries to minimize API calls
Privacy Settings
For team/enterprise accounts:- Control data sharing in GPT settings
- Set action permissions (private, team, public)
- Configure audit logging if required
Sharing Your GPT
Make it Public
- Go to GPT settings
- Click “Publish” → “Public”
- Share the GPT link with others
- Users will need their own CodeAlive API key
Team Sharing
For ChatGPT Team/Enterprise:- Set visibility to “Anyone at [Your Organization]”
- Team members can use shared authentication
- Centrally manage API keys
Best Practices
Specific Queries
Use precise search terms to get relevant results
Context Windows
Be mindful of token limits when searching large codebases
Caching
Reuse search results within the same conversation
Security
Never share API keys in conversation
Troubleshooting
Action fails with authentication error
Action fails with authentication error
Solutions:
- Verify API key is correct
- Check key hasn’t expired
- Ensure Bearer prefix is included
- Regenerate key if needed
No results from searches
No results from searches
Solutions:
- Verify repositories are indexed
- Check search query syntax
- Test API directly with curl
- Check rate limits
GPT not using CodeAlive action
GPT not using CodeAlive action
Solutions:
- Explicitly ask to “use CodeAlive”
- Check action is enabled
- Verify OpenAPI schema is valid
- Review GPT instructions
Rate limit exceeded
Rate limit exceeded
Solutions:
- Reduce frequency of searches
- Use more specific queries
- Upgrade CodeAlive plan
- Cache results when possible
Limitations
Alternatives
If ChatGPT doesn’t meet your needs, consider:Claude Code
Native MCP support with real-time updates
Cursor
IDE-integrated AI with MCP
Continue
Open-source alternative with MCP
API Direct
Build custom integration
Related Resources
Instruct Your Agent
Connecting CodeAlive makes its tools available, but the agent may still default to its built-in search. For reliable results, add a short instruction in the agent’s native format telling it to prefersemantic_search and grep_search when exploring indexed code. See Instructing Coding Agents.