Clarity MCP (in development)

Ask Clarity from Codex, Claude or MCP Inspector. In development — not yet available.

GIF: StickerGiant via GIPHY

The Clarity MCP server is not released. This page describes the design under review. Tool names, profiles and scopes will change before release, and it will first be enabled only for Motif's own organization.

The Clarity MCP lets an analyst on your team ask Clarity from an MCP client, with the same routing and policies as the admin chat. It is read-only: it cannot change prompts, models, tools, portfolios, cards or notifications.

Photo: John Barkiple on Unsplash

Connection

Item	Value
Endpoint	https://backend.motifapp.ai/api/mcp/clarity
Transport	Streamable HTTP, POST only; long calls stream progress, and disconnecting cancels the run
Auth	OAuth 2.1 with PKCE. Clients register with a Client ID Metadata Document; there is no dynamic client registration.
Scopes	clarity:chat to ask; clarity:debug for single-profile calls and run receipts

Connecting

1. Add the endpoint to your MCP client.

2. Sign in with your admin account.

3. Choose one organization where you are a member and the MCP is enabled.

4. Approve the consent screen, which shows the client, the organization and the scopes.

An organization admin switches the MCP on (it is off by default) and can revoke any connection. Members can revoke their own. Revocation applies on the next request.

Tools

Tool	What it does
get_clarity_roster	Lists the agents and what each may be asked
ask_clarity	Asks a question about the organization or one portfolio you can already access. Returns a cited answer, sources, freshness, the chosen agent and follow-up questions.
ask_clarity_profile	Asks one named agent directly, for diagnosis. Labelled as diagnostic, not the production workflow.
list_clarity_turns	Lists your recent questions
inspect_clarity_turn	A receipt for one answer: tools used, evidence cited and unused, freshness, retries, model, tokens, cost and latency

Boundaries

• No access beyond what the user already has; OAuth never widens portfolio access.

• No raw prompts, hidden reasoning, secrets or internal ids in responses.

• No experiments, promotions or configuration changes.

Tested clients

The design targets Codex and MCP Inspector. Claude Desktop and claude.ai custom connectors are expected to work once they support the same protocol version and client metadata documents; this is not yet verified.