We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/avimunk1/tennis-warehouse-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
# ChatGPT Localhost Workaround Solutions
## π¨ **Problem:**
ChatGPT Custom GPTs cannot access localhost URLs for security reasons.
**Error:** `Server URL http://localhost:8000 is not under the root origin https://localhost`
## π§ **Solutions:**
### **Option 1: Deploy to Public URL (Best)**
Deploy your API to get a public HTTPS URL:
#### **Railway Deployment (Free):**
```bash
# Install Railway CLI (if not installed)
npm install -g @railway/cli
# Login and deploy
railway login
railway deploy
```
#### **Quick Railway Deploy:**
```bash
./deploy.sh
# Choose option 1
```
After deployment, update the OpenAPI schema:
```json
"servers": [
{
"url": "https://your-app.railway.app",
"description": "Production server"
}
]
```
### **Option 2: Use ngrok (Quick Test)**
For quick testing, use ngrok to tunnel your localhost:
```bash
# Install ngrok
brew install ngrok
# Create tunnel to localhost:8000
ngrok http 8000
```
This gives you a public HTTPS URL like `https://abc123.ngrok.io`
Update OpenAPI schema:
```json
"servers": [
{
"url": "https://abc123.ngrok.io",
"description": "Ngrok tunnel"
}
]
```
### **Option 3: Alternative Local Testing**
Since ChatGPT Custom GPTs can't access localhost, you can:
1. **Test with Postman/Insomnia** using the current localhost setup
2. **Use Claude Desktop** (already configured and working)
3. **Deploy for ChatGPT** when ready
## π― **Recommended Approach:**
1. **Continue using Claude Desktop** for local testing (already working)
2. **Deploy to Railway** for ChatGPT Custom GPT
3. **Update OpenAPI schema** with public URL
4. **Create ChatGPT Custom GPT** with public API
## π **Railway Deployment Status:**
Your project is ready to deploy:
- β
`Dockerfile` configured
- β
`requirements-api.txt` ready
- β
`Procfile` for process management
- β
All dependencies installed
**Next Step:** Deploy to Railway to get your public HTTPS URL!