Logo

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:

https://api.example.com/mcp
https://mcp-server.herokuapp.com/mcp
https://your-domain.com/mcp-endpoint

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:

  1. Tap Configure OAuth
  2. Follow in-app browser authentication
  3. Grant required permissions
  4. Return to app automatically

3. Add Custom Headers (if required)

Add authentication headers or custom configuration:

API Key Authentication:

Header: Authorization
Value: Bearer YOUR_API_KEY

Basic Authentication:

Header: Authorization  
Value: Basic [base64-encoded credentials]

Custom Headers:

Header: X-API-Key
Value: your-api-key

Header: X-Client-ID
Value: your-client-id

Connection Setup

  1. Open Systemprompt app
  2. Navigate to SettingsMCP Servers
  3. Tap Add Server
  4. Select Remote Server
  5. Enter your HTTPS MCP endpoint URL
  6. Configure authentication if required
  7. Add custom headers if needed
  8. Test connection

Testing Connection

Verify your connection with basic commands:

"ping remote server"
"list available tools"
"check server health"

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

On this page