Other MCP clients

Any client that supports Streamable HTTP with a static Authorization header can connect.

Setting	Value
URL	https://api.inside.chat/mcp, or http://localhost:8787/mcp locally
Transport	Streamable HTTP, POST only, plain JSON responses, no session
Authentication	Authorization: Bearer igw_live_...: an installation token, or an OAuth token requested with resource=<origin>/mcp
Protocol versions	2025-11-25, 2025-06-18, 2025-03-26

Server behaviour

• Accepts only POST /mcp with Content-Type: application/json and Accept: application/json, text/event-stream.
• Returns plain JSON, never an event stream, and issues no Mcp-Session-Id. GET and DELETE return 405.
• Expects initialize first, and the negotiated MCP-Protocol-Version header on later requests.
• Rejects JSON-RPC batches, request bodies over 64 KiB and query strings.
• Rejects browser requests from other origins, so run the client on a server or desktop.
• Needs authentication on every request, including initialize.

Test with curl

curl -s https://api.inside.chat/mcp \
  -H "Authorization: Bearer $INSIDE_GATEWAY_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"curl","version":"1.0"}}}'

curl -s https://api.inside.chat/mcp \
  -H "Authorization: Bearer $INSIDE_GATEWAY_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-11-25" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

See the MCP reference for result shapes and errors.