Logo

Custom Integration

Universal compatibility with any HTTPS streamable MCP server

Custom MCP Server Integration

systemprompt guarantees compatibility with any HTTPS streamable MCP server that works with the official MCP inspector. This is our commitment to universal MCP support.

Our Compatibility Promise

🛡️ 100% MCP Standard Compliance

If your server works with the official MCP inspector, it will work with systemprompt. We guarantee it.

Rapid Compatibility Updates

Found an issue? We commit to making your MCP server compatible as soon as possible. Our team prioritizes compatibility fixes to ensure you're never blocked.

🔧 No Vendor Lock-in

Build your own MCP servers or use third-party implementations. systemprompt works with any standard-compliant MCP server over HTTPS.

Requirements

Your custom MCP server needs:

  1. HTTPS Endpoint: Secure connection required
  2. Streamable HTTP Transport: SSE support
  3. MCP Protocol Compliance: Standard MCP message format
  4. Valid SSL Certificate: For production servers

Quick Setup Guide

1. Verify Your Server

First, ensure your server works with the official MCP inspector:

# Test with MCP inspector
npx @modelcontextprotocol/inspector your-server-url

2. Add to systemprompt

  1. Open MCP Servers screen
  2. Tap "Add Server"
  3. Select "Custom Server"
  4. Enter your server details:
    • Name: Your descriptive name
    • URL: https://your-domain.com/mcp
    • Transport: SSE
    • Authentication: As required

3. Test Connection

systemprompt will:

  • Validate the connection
  • Enumerate available tools
  • Confirm MCP compliance
  • Ready for voice control!

Common Configurations

Basic SSE Server

Name: My Custom Server
URL: https://api.mycompany.com/mcp
Transport: SSE
Auth: Bearer Token

SSE with API Key

Name: Real-time Service
URL: https://realtime.example.com/mcp
Transport: SSE
Auth: API Key
Headers:
  X-API-Key: your-key

Development Server

Name: Local Dev
URL: https://localhost:3000/mcp
Transport: SSE
Auth: None
Note: Requires valid certificate

Compatibility Checklist

Ensure your server:

  • ✅ Responds to MCP initialize request
  • ✅ Returns valid tool definitions
  • ✅ Handles tool execution requests
  • ✅ Supports streaming responses
  • ✅ Implements error handling
  • ✅ Uses standard MCP message format

Getting Support

Compatibility Issues?

If your MCP-compliant server doesn't work with systemprompt:

  1. Test with MCP Inspector first
  2. Contact Support with:
    • Server URL (sanitized)
    • MCP inspector results
    • Error messages from systemprompt
  3. We'll fix it ASAP - usually within 48 hours

Support Channels

Building MCP Servers

Resources

Best Practices

  1. Use Standard SDKs: Ensures compatibility
  2. Test Thoroughly: With MCP inspector first
  3. Implement Error Handling: Clear error messages
  4. Document Tools: Provide clear descriptions
  5. Version Your API: For backward compatibility

Examples of Custom Integrations

Internal Tools

Corporate databases, proprietary APIs, internal services

Industry-Specific

Medical records, financial systems, IoT platforms

Personal Projects

Home automation, personal databases, hobby projects

Third-Party Services

Any service with MCP wrapper, community servers

Why Choose Custom Integration?

Complete Control

  • Define your own tools
  • Custom authentication
  • Proprietary protocols wrapped in MCP
  • Full data sovereignty

Seamless Integration

  • Works identically to pre-built integrations
  • Same voice control capabilities
  • Full systemprompt feature support
  • No limitations

Future-Proof

  • MCP is an open standard
  • Your investment is protected
  • Community-driven evolution
  • Vendor-independent

Troubleshooting

Common Issues

"Connection refused"

  • Verify HTTPS certificate
  • Check server is running
  • Confirm URL is accessible

"Invalid MCP response"

  • Ensure MCP compliance
  • Check response format
  • Verify with inspector

"No tools found"

  • Implement tool listing
  • Check tool definitions
  • Verify permissions

Debug Mode

Enable detailed logging:

  1. Settings → Advanced
  2. Toggle "Debug Mode"
  3. Try connection again
  4. Share logs with support

Our Commitment

systemprompt is built on the principle of universal MCP compatibility. We believe in:

  • 🌐 Open standards over proprietary protocols
  • 🤝 Community collaboration for better tooling
  • 🚀 Rapid iteration to support new use cases
  • 💪 Developer empowerment through flexibility

🎯 Compatibility Guarantee

If your HTTPS streamable MCP server works with the official inspector but not with systemprompt, we'll fix it within 48 hours or your subscription is free until we do.

Contact Support →

On this page