Assay MCP
All of Assay, in the AI tools you already use.
Full parity with the webapp over one connection. 48 tools, all four agents. Approved truth comes in. Writes go out through the firewall.
Remote server · HTTPS · Streamable HTTP · OAuth 2.1Full parity
One pipe. The whole platform.
Everything the webapp can do, a supported AI tool can ask for. Full reads, drafts, checks, and governed writes.
Task-sized approved truth.
Positioning, proof, voice, and rules scoped to the job at hand. Pending and restricted material stays out.
The same 48 tools.
Research, drafts, claim checks, plans, and writes from AI CMO, SEO & GEO, Product Marketer, and Content & Social.
Sources, verdicts, receipts.
Every answer carries its sources. Every claim check returns a verdict. Every write leaves a receipt.
Governed writes
The firewall travels with the connection.
Every write previews as a dry-run plan and commits only with an approved plan token. And some things no AI writes at all. Pricing, policy, proof, and identity stay with people.
One real catch: a draft claims “Start in 5 days.” The claim check finds no source, the plan stops, and you see exactly why.
Setup
Connect once.
The scope stays explicit at every step. You see the person, workspace, data, tools, and actions before anything runs.
Tool support and confirmation flows vary by host.
Start
Connect one tool to one clear job.
We scope the OAuth grant, run the first read, and walk the first dry-run with you.