Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.shingleai.com/llms.txt

Use this file to discover all available pages before exploring further.

This guide covers how to connect AI agents to the ShingleAI MCP server, including the available transports and troubleshooting common issues.

​
Connection URL

The MCP server is available at: 
https://mcp.shingleai.com

​
Authentication

Modern MCP clients (Claude Desktop, Claude Code, Cursor, Windsurf) handle OAuth 2.1 + PKCE automatically — point them at the connection URL above and they walk you through sign-in and consent. See Authentication for the full flow.

​
Transports

The MCP server supports two transports:
  • Streamable HTTP — https://mcp.shingleai.com/mcp. The current MCP transport; recommended for new clients.
  • Server-Sent Events (SSE) — https://mcp.shingleai.com/sse. Kept for compatibility with clients that implement the earlier SSE transport.
Pick whichever your client supports; you do not need to configure both.

​
Health Check

Verify the MCP server is available before connecting: 
curl https://mcp.shingleai.com/health
Response: 
{"status": "ok"}
The health check endpoint doesn’t require authentication. Use it to verify connectivity before attempting to establish an authenticated connection.

​
Troubleshooting

Possible causes:
  • Network connectivity issues
  • Firewall blocking outbound HTTPS
  • Incorrect URL
Solutions:
  1. Verify network connectivity: curl https://mcp.shingleai.com/health
  2. Check firewall rules allow outbound HTTPS (port 443)
  3. Ensure you’re using https:// not http://
A 401 is the canonical signal that your client needs to run (or re-run) the OAuth flow. The WWW-Authenticate header on the response points to a route-scoped protected-resource metadata URL (e.g. /.well-known/oauth-protected-resource/mcp), which a spec-compliant client uses to start discovery.Solutions:
  1. Confirm your client supports OAuth 2.1 + PKCE + Dynamic Client Registration. Most current MCP clients do.
  2. Make sure you completed the consent screen in your browser. If you cancelled it, retry the connection from your client.
  3. If the client looks stuck after a successful consent, remove and re-add the ShingleAI server in the client so it re-registers via DCR.
  4. See Authentication for the full handshake.
Possible causes:
  • Insufficient permissions for the requested tool
  • Monthly call limit exceeded
  • Account suspended
Solutions:
  1. Check the error message for details
  2. Check your usage in the dashboard
  3. Upgrade your plan if you’ve hit the monthly limit
Possible causes:
  • Too many requests in a short period
  • Exceeding 100 requests per 60 seconds per (user, client)
Solutions:
  1. Implement request queuing or throttling
  2. Use exponential backoff when retrying
  3. Wait for the duration in the Retry-After response header before retrying
Possible causes:
  • Network instability
  • Idle timeout
  • Server maintenance
Solutions:
  1. Implement automatic reconnection logic
  2. Send periodic ping messages to keep the connection alive
  3. Check status.shingleai.com for service issues

​
Session Management

MCP connections are stateful. Each connection receives a unique session ID that persists for the duration of the connection.
  • Session IDs are generated automatically on connection
  • Sessions expire after extended idle periods
  • Reconnections create new sessions - previous session state is not preserved
Design your agent to be stateless where possible. Don’t rely on server-side session state persisting between tool calls.

​
Next Steps

Available Tools

Explore the complete list of MCP tools

Integrations

See examples of MCP integrations
Last modified on May 2, 2026