Typetone isn’t just a web app: you can plug its audits, compliance checks and content tools into your own systems and into the AI assistants your team already uses. There are two ways in: the API and the MCP server.
The API
The API lets your own code talk to Typetone. Use it to build content and compliance checks into your existing workflows, for example auditing a page automatically before it goes live, or pulling audit results into your own dashboard.
To get started:
- Generate an API key from your organization settings.
- Store it securely as an environment variable: never commit it to code or share it in plain text.
- Call Typetone from your app or automation using that key.
The developer docs list every endpoint with examples, starting with a quickstart. If you’re planning a bigger integration, get in touch and we’ll help you scope it.
MCP: use Typetone inside AI assistants
MCP (the Model Context Protocol) is an open standard that lets AI assistants connect to outside tools. Typetone runs an MCP server, so you can give your AI assistant direct access to Typetone and then just ask it, in plain language, to do things like “audit this page against our brand rules” or “check this ad for compliance issues.”
Because MCP is a shared standard, it works with a growing list of tools, including:
- Claude (desktop, Claude Code and other MCP-enabled clients)
- Cursor and Codex for developers
- Assistants like ChatGPT, Google Gemini and Microsoft Copilot
The general pattern is the same everywhere: add Typetone as a connector/MCP server in your tool, authenticate with your Typetone account or key, and the assistant can then run Typetone actions for you.
Setup differs slightly per tool. The MCP server docs have the server URL, the sign-in options and every available tool. Still stuck? Contact us and we’ll get you connected.
Which should I use?
- Building it into your own product or automation? Use the API.
- Want to drive Typetone from an AI assistant in plain language? Use MCP.
Plenty of teams use both together.
