Remote Connection
Connect to cloud-hosted and remote MCP servers
Remote Connection
The app needs a remote HTTPS streamable transport endpoint (usually ending with /mcp
) in order to connect to remote MCP servers. This includes cloud-hosted services, production endpoints, and third-party MCP providers.
1. Enter Remote URL
Enter the full HTTPS URL to your MCP endpoint:
Examples:
Requirements:
- Must use HTTPS (not HTTP)
- Must support streamable transport
- Usually ends with
/mcp
or similar MCP endpoint path
2. Configure OAuth (if required)
If your server requires OAuth authentication, the app will guide you through the in-device OAuth flow:
- Tap Configure OAuth
- Follow in-app browser authentication
- Grant required permissions
- Return to app automatically
3. Add Custom Headers (if required)
Add authentication headers or custom configuration:
API Key Authentication:
Basic Authentication:
Custom Headers:
Connection Setup
- Open Systemprompt app
- Navigate to Settings → MCP Servers
- Tap Add Server
- Select Remote Server
- Enter your HTTPS MCP endpoint URL
- Configure authentication if required
- Add custom headers if needed
- Test connection
Testing Connection
Verify your connection with basic commands:
Common Issues
SSL Certificate Errors
- Ensure server has valid SSL certificate
- Check certificate chain is complete
- Verify domain matches certificate
Authentication Failures
- Verify API keys are correct and active
- Check authentication method matches server requirements
- Ensure headers are properly formatted
Connection Timeout
- Check server URL is accessible
- Verify firewall rules allow HTTPS traffic
- Test endpoint in browser first
Streamable Transport Issues
- Ensure server supports MCP streamable transport
- Verify endpoint path is correct (usually
/mcp
) - Check server logs for connection attempts