Skip to content

Developers

Agents that sign in properly.

Agents are users of your product too. Synq signs people in to them with the standards MCP and OAuth expect, and every token says which agent acts for whom.

Built

An authorization server for your MCP servers

MCP hosts register themselves with client ID metadata documents or dynamic registration, sign the person in with PKCE, ask for consent, and get tokens for your MCP server alone.

The device flow for CLIs and agents

An agent shows a short code, the person approves it on any device, and the agent is named in its tokens and in your audit log.

Synq’s own MCP server

Your org’s admins can set Synq up and run it from an MCP host: orgs, brands, apps, users, webhooks and the audit log. An ordinary change is made at once and says how to undo it. Changes to money, people or sign-in security, and any that makes a secret, wait for the person to approve them in the Synq dashboard.

Markdown for every page

Every page of this site answers in markdown to an agent that asks for it, and /llms.txt lists them.

Read next

Ready to try it in your app?

Tell us what you are building and which sign-in your users need.