Configure Model Context Protocol servers on native mobile. OAuth, API tokens, and advanced MCP client settings for iOS and Android devices.

MCP Server Setup and Authentication

The Server Configuration screen provides comprehensive control over MCP server settings, from basic connectivity to advanced authentication flows and contextual hints. Master these configuration options to optimize your server connections.

Overview

Each MCP server can be customized with specific settings that control how it connects, authenticates, and operates within systemprompt. The configuration screen adapts dynamically based on server type and requirements.

Configuration Levels

Basic Setup: Name, URL, and transport type
Authentication: Various auth methods supported
Server Hints: Contextual key-value pairs
Advanced Settings: Timeouts, headers, and more

Basic Configuration

Essential Settings

Every server requires:

Server Name

Display name in the app
Used in voice commands
Should be unique and descriptive
Can be changed anytime

Server URL

Full endpoint URL (https://...)
Must be accessible from device
Supports both public and private endpoints
Validated on save

Transport Type

SSE (Server-Sent Events): Default, widely supported
WebSocket: For bidirectional communication
Auto-detected when possible

URL Formats

Common MCP server URL patterns:

Official servers:
https://api.githubcopilot.com/mcp/

systemprompt servers:
https://mcp.systemprompt.io/reddit/mcp
https://mcp.systemprompt.io/sentry/sse

Custom servers:
https://your-domain.com/mcp
http://localhost:3000/mcp (development)

Authentication Methods

No Authentication

For open or local servers:

No credentials required
Immediate connection
Common for development
Internal network servers

Bearer Token

Static token authentication:

Authorization: Bearer <your-token-here>

Configuration:

Generate token from service
Paste in token field
Token stored securely
Sent with every request

API Key

Key-based authentication:

Header: X-API-Key: <your-key>
Query: ?api_key=<your-key>

Options:

Header name customizable
Query parameter support
Multiple key formats

OAuth 2.0

Full OAuth flow support:

Auto-Discovery

Enter base domain
System finds OAuth endpoints
Automatic configuration
Guided authorization flow

Manual Configuration

Authorization URL
Token URL
Client ID
Client Secret (optional)
Scopes
Redirect URI handling

OAuth Flow

Tap "Authorize"
Browser opens for login
Approve permissions
Return to app
Token stored securely

Server Hints

Understanding Hints

Server hints provide context to MCP servers:

{
  "repository": "myorg/main-app",
  "environment": "production",
  "user_role": "developer",
  "preferred_language": "en",
  "timezone": "America/New_York"
}

Common Hint Patterns

Development Context

project: "mobile-app"
branch: "feature/dark-mode"
environment: "staging"

User Preferences

language: "en"
timezone: "UTC-5"
date_format: "MM/DD/YYYY"

Access Control

team: "frontend"
role: "lead"
permissions: "read,write"

Dynamic Hints

Some hints can use variables:

{user.name}: Current user's name
{device.id}: Unique device identifier
{app.version}: systemprompt version
{date.today}: Current date

Advanced Settings

Connection Options

Timeout Settings

Connection timeout: Time to establish connection
Request timeout: Time for server responses
Idle timeout: Keep-alive duration
Retry delay: Time between retries

Retry Policy

Max retries: Number of attempts
Backoff strategy: Linear or exponential
Retry conditions: Which errors to retry

Custom Headers

Add additional HTTP headers:

X-Custom-Header: value
X-Client-Version: 1.0.0
X-Request-ID: {unique-id}

Use cases:

API versioning
Client identification
Request tracking
Custom authentication

Security Settings

Certificate Validation

Strict: Verify all certificates
Relaxed: Allow self-signed (dev only)
Pinning: Specific certificate required

Token Management

Auto-refresh: For expiring tokens
Rotation schedule: Regular updates
Secure storage: Keychain/keystore

Predefined Configurations

GitHub Configuration

Name: GitHub
URL: https://api.githubcopilot.com/mcp/
Transport: SSE
Auth: OAuth 2.0
Scopes: repo, issues, pull_requests

Special features:

Automatic repo detection
Personal/Org token support
Fine-grained permissions

Reddit Configuration

Name: Reddit  
URL: https://mcp.systemprompt.io/reddit/mcp
Transport: SSE
Auth: Bearer Token
Hints: {
  "subreddits": "programming,webdev",
  "sort": "hot"
}

Sentry Configuration

Name: Sentry
URL: https://mcp.systemprompt.io/sentry/sse
Transport: SSE
Auth: API Key
Headers: {
  "X-Sentry-Org": "your-org"
}

Make Configuration

Name: Make Automation
URL: https://mcp.systemprompt.io/make/{zone}
Transport: SSE
Auth: Bearer Token
URL Variables: {
  "zone": "us1"
}

Configuration Workflows

Initial Setup

Choose server type (predefined or custom)
Enter basic details (name, URL)
Configure authentication
Add server hints (optional)
Test connection
Save configuration

Editing Existing

Select server from list
Tap edit button
Modify settings
Test changes
Save updates

Cloning Configuration

Long-press server
Select "Duplicate"
Modify for new purpose
Save as new server

Testing & Validation

Connection Test

Tests performed:

URL accessibility
Transport compatibility
Authentication validity
Tool enumeration
Response time check

Test Results

Success indicators:

✅ Connection established
✅ Authentication successful
✅ Found X tools
✅ Average response: Xms

Error handling:

❌ Connection failed: Reason
❌ Auth error: Details
❌ No tools found
🔄 Retry options

Troubleshooting

Common Issues

Invalid URL

Check URL format
Ensure HTTPS for remote
Verify server is running
Test in browser first

Authentication Failures

Regenerate tokens
Check token permissions
Verify OAuth scopes
Review server requirements

Connection Timeouts

Increase timeout values
Check network connectivity
Verify firewall rules
Try different transport

Debug Mode

Enable for detailed logging:

Toggle "Debug Mode"
Attempt connection
View detailed logs
Share with support

Best Practices

Security

Use HTTPS for remote servers
Rotate tokens regularly
Minimal permissions only what's needed
Unique tokens per server
Review access periodically

Performance

Optimal timeouts: Balance speed/reliability
Efficient hints: Only necessary context
Connection pooling: Reuse when possible
Error handling: Graceful degradation

Organization

Naming convention: Consistent scheme
Group by function: Related servers together
Document purpose: In server notes
Regular cleanup: Remove unused

Advanced Patterns

Multi-Environment

GitHub (Dev)
- URL: Same
- Token: Dev-specific
- Hints: {"env": "development"}

GitHub (Prod)
- URL: Same  
- Token: Prod-specific
- Hints: {"env": "production"}

Load Balancing

Service (Primary)
- URL: https://primary.example.com/mcp

Service (Backup)
- URL: https://backup.example.com/mcp
- Auto-failover configured

Conditional Configuration

Use server hints for dynamic behavior:

{
  "mode": "{user.preference}",
  "filter": "{active.project}",
  "limit": "{performance.mode}"
}

Master server configuration to unlock the full potential of MCP integrations!

Server Configuration

On this page