# Synota MCP

Synota supports MCP. This dashboard is not the MCP server.

- MCP endpoint: https://zfd3a4eca-z5ff1934f-gtw.zc58ad147.prm.sh/mcp
- Authorization server metadata: https://zfd3a4eca-z5ff1934f-gtw.zc58ad147.prm.sh/.well-known/oauth-authorization-server
- Protected resource metadata: https://zfd3a4eca-z5ff1934f-gtw.zc58ad147.prm.sh/.well-known/oauth-protected-resource/mcp
- Manage/revoke connections: https://zfd3a4eca-z5ff1934f-gtw.zc58ad147.prm.sh/oauth/connections
- Setup guide on this dashboard: /mcp

Use a client compatible with MCP protocol 2026-07-28. Older clients may be
incompatible; that does not mean Synota has no MCP. Configure the endpoint above,
then use OAuth authorization code with PKCE S256 and public HTTPS Client ID
Metadata Documents (CIMD). Follow the server's OAuth metadata and 401 challenge.
The API accepts MCP requests via POST; a GET probe is not a capability check.
This is stateless MCP: use server/discover or tools directly, without initialize.
The resource audience is the exact MCP endpoint. Request mcp:read, or
mcp:read mcp:write. Complete login, MFA and consent in the browser; do not ask
users to paste passwords, MFA codes or tokens into chat. Consent defaults to read.
Account permissions still apply. Follow browser approval URLs for private inputs,
uploads or required MFA and resume the pending request as instructed.
The connections page manages existing grants; it does not connect an MCP client.