Docs

Connect Dasho to ChatGPT or Claude

Score a draft against your brand rules without leaving the chat.

The short version

Dasho runs an MCP server. MCP is the standard way an AI assistant talks to an outside tool, and both ChatGPT and Claude support it. You add one address in your settings, and Dasho's checks appear as tools your assistant can use.

The address

https://api.dasho.ai/mcp

What your assistant can do once connected

Tool	What it does	Needs a key
`score_content`	Scores a draft against a brand and returns the weak dimensions	No
`score_vs_industry`	Compares that score against the industry	No
`check_compliance`	Checks a draft against your own configured rules	Yes
`get_brand_context`	Returns a brand's voice, rules and audience	Yes
`generate_report`	Builds a governance report	Yes
`get_governance_trend`	Scores over recent weeks	Yes
`rewrite_content`	Rewrites a post to fit the brand	Yes
`list_posts`	Lists a brand's posts, newest first, with status and score	Yes
`get_post`	Reads one post: its content, status and latest scorecard	Yes

Two tools work with no account at all, so you can test the connection before you add a key.

Add it in Claude

Open Settings, then Connectors.
Choose Add custom connector.
Name it Dasho and paste the address above.
Save. Claude connects and lists the tools.
Leave Authentication on None. Claude detects this correctly, because Dasho uses an API key rather than a sign-in flow.
The two open tools work right away. For the seven keyed tools, open Request headers, add a header named X-Dasho-Api-Key, and set it to your organisation's Dasho API key. Your organisation also needs API access enabled.

Add it in ChatGPT

Open Settings, then Connectors. On a work account an administrator may need to do this for everyone.
Choose Add custom connector and paste the same address.
If your network restricts outbound traffic, allow api.dasho.ai on port 443.
For the seven keyed tools, add a request header X-Dasho-Api-Key set to your organisation's Dasho API key.

Dasho will not appear in the connector catalogue you can browse. That list is curated and carries a small number of partners. Adding the address by hand is the supported route and gives you exactly the same tools.

Try it without connecting anything

This runs from any terminal and needs no account:

curl -s -X POST https://api.dasho.ai/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"score_content","arguments":{
         "content":"Our revolutionary platform delivers seamless results.",
         "brand_url":"https://www.yourbrand.com"}}}'

A real reply, run on 1 September 2026:

{"score":66,"label":"Needs Work",
 "top_dimensions":[{"dimension":"Regulated Claims","score":100},
                   {"dimension":"Brand Voice","score":85},
                   {"dimension":"Clear CTA","score":40}]}

If the connection fails

What you see	What it means
Cannot resolve api.dasho.ai	Your network is blocking the address, not Dasho. Allow api.dasho.ai on port 443. The address resolves publicly.
Dasho is not in the connector catalogue	Correct, and expected. That catalogue is curated by OpenAI and Anthropic. Use Add custom connector and paste the address.
Your assistant says it cannot install it for you	Also expected. No assistant can add a connector from inside a chat. A person adds it once in settings.
Tools appear, but the seven that need a key fail	The seven keyed tools need your Dasho API key. Add it as a request header, X-Dasho-Api-Key, set to your organisation key, and make sure your organisation has API access enabled.

Security, in plain terms

Your API key grants access to one organisation, the one it belongs to. A connector cannot reach another customer's brands.
Only the Dasho team can issue, rotate, or disable a key, through our admin tools. Ask us and the connector stops working the moment the key is disabled.
The two open tools read only the text you send and the public pages of the brand address you give them.

Questions: get in touch. The example score was read from the live server on 1 September 2026, and the tool list on 3 September 2026.