11
min read
Server URL: https://apps.gomarble.ai/mcp-api/sse
Authentication: OAuth 2.0 with account authorization required
Protocol: SSE-based (Server-Sent Events) - not Streamable HTTP
Sample Implementation
Here's a complete example using the FastMCP client library to connect to the Marble MCP server:
For more details on FastMCP OAuth implementation, see: https://gofastmcp.com/clients/auth/oauth
Client Implementation Requirements
Technical Prerequisites
SSE Support: Your MCP client must support Server-Sent Events (SSE) based servers
OAuth 2.0 Flow: Implement OAuth authentication handling
HTTPS: All communications must use encrypted HTTPS connections
Rate Limiting: Implement client-side rate limiting (25 requests per minute per user)
Authentication Implementation
The server uses OAuth 2.0 for secure authentication. Your client must:
Handle OAuth authentication flows
Manage access tokens with limited lifetime and scope
Implement token refresh mechanisms
Handle authentication errors gracefully
Connection Configuration
Development Best Practices
Error Handling
Authentication Errors: Implement graceful handling for auth failures
API Calls: Use proper error handling for all API interactions
Connection Issues: Handle network connectivity problems
Rate Limiting: Implement exponential backoff for rate limit hits
Performance Optimization
Caching: Cache responses when appropriate to improve performance
Rate Limiting: Use client-side rate limiting to prevent API abuse
Connection Management: Maintain stable SSE connections
Debugging and Troubleshooting
Common Development Issues
Connection Issues
Symptoms:
Failed SSE connections
Timeout errors
Protocol mismatches
Solutions:
Verify SSE protocol support in your client
Check network connectivity to
https://apps.gomarble.ai/mcp-api/sse
Ensure HTTPS handling is correct
Validate connection parameters
Rate Limiting Issues
Symptoms:
HTTP 429 responses
Request throttling
Performance degradation
Solutions:
Implement proper rate limiting (25 requests/minute)
Add exponential backoff
Cache responses to reduce API calls
Monitor request frequency
Security Considerations for Developers
Implementation Requirements
OAuth 2.0: Proper implementation of OAuth authentication flow
HTTPS Only: All communications must use encrypted connections
Token Management: Secure storage and handling of access tokens
Scope Validation: Respect user permission boundaries
Support Resources
Developer Support
When seeking technical support, provide:
Client Implementation Details: Programming language, framework, version
Error Messages: Complete error logs and stack traces
Connection Configuration: Your client's MCP server configuration
Reproduction Steps: Detailed steps to reproduce the issue
Expected vs Actual Behavior: Clear description of the problem
Technical Support Channels
Email Support: Contact technical support with implementation questions at admin@gomarble.ai
Documentation: Reference this guide for implementation details