JustAI MCP

The JustAI MCP server lets AI assistants inspect your JustAI account and compose calls against dashboard-backed JustAI API paths. It is designed for reporting, troubleshooting, and account exploration workflows where a marketer can ask natural-language questions like:

• “List my running templates and summarize which ones have metrics.”
• “Show the variants for this template and include sends, opens, and clicks for the last 30 days.”
• “Find uploaded resources, then run the saved audience view for this campaign.”
• “Pull the copy for this template so I can draft a weekly performance report.”

Server URL

Use the JustAI worker origin plus /mcp:

https://worker.justwords.ai/mcp

If your JustAI team gives you a different worker origin, keep the same /mcp path.

Authentication

Claude Desktop and other OAuth-capable MCP clients use browser-based OAuth:

1. The MCP client opens a JustAI authorization page.
2. You sign in with your JustAI account.
3. JustAI stores the resolved user and account scope for the MCP grant.
4. The MCP client receives an OAuth token scoped to that account.

Note

You do not need to create or paste a JustAI API key for Claude Desktop. Leave OAuth Client ID and OAuth Client Secret blank unless JustAI explicitly gives you values for a custom deployment.

Install in Claude Desktop

In Claude Desktop, go to Settings -> Connectors -> Add custom connector.

Field	Value
Name	justai
Remote MCP server URL	https://worker.justwords.ai/mcp
OAuth Client ID	Leave blank
OAuth Client Secret	Leave blank

Click Add, then complete the browser sign-in flow. After authorization, Claude can call the JustAI MCP tools for the account you selected.

Install in Other MCP Clients

Claude Code

Claude Code can connect through mcp-remote:

{
  "mcpServers": {
    "justai": {
      "command": "npx",
      "args": ["mcp-remote", "https://worker.justwords.ai/mcp"]
    }
  }
}

Remote URL clients

For clients with native remote MCP support, use the remote server URL directly:

{
  "mcpServers": {
    "justai": {
      "type": "url",
      "url": "https://worker.justwords.ai/mcp"
    }
  }
}

If the client supports OAuth, follow the browser sign-in flow.

Header auth clients

Some local tools support custom headers. For those clients, you can use a JustAI API key instead of OAuth:

claude mcp add --transport http justai \
  https://worker.justwords.ai/mcp \
  --header "X-Api-Key: $JUSTAI_API_KEY"

Header-based auth is useful for local automation and clients that do not support MCP OAuth. For Claude Desktop, use OAuth instead.

What the MCP Server Can Do

The JustAI MCP server exposes a compact API surface through two agent-facing tools:

Tool	Purpose
Search	Discover the available JustAI API paths and parameters before making a request.
Execute	Run a sandboxed request against the supported JustAI API paths.

The assistant can compose small sandboxed snippets to call the API, but auth, account scoping, database access, and network restrictions stay server-side. The sandbox does not receive your API keys or database credentials.

The supported MCP API paths delegate to the same /web handlers used by the JustAI dashboard. When an MCP workflow needs more data or flexibility, JustAI expands the underlying /web endpoint first so dashboard and MCP behavior stay in parity.

Available Surfaces

Surface	Current capabilities
Templates	List templates, fetch one template, filter by date, inspect dashboard row metrics, and optionally include variant vars for a single template.
Template metrics	Use the same dashboard-backed metric fields returned by the template list and template detail /web paths. The MCP layer does not reimplement analytics calculations.
Resources	List uploaded resources, fetch a resource summary, inspect columns and saved views.
Resource queries	Run paginated SELECT queries against an uploaded resource.
Saved views	List saved views, fetch a saved view, and execute a saved view with parameters and pagination.

Template responses are summary-first. Lists do not return full variant vars, because vars can contain large HTML bodies. To inspect full copy or HTML for a single template, ask the assistant to fetch that template with include_variant_vars=true.

Example Prompts

Try prompts that ask the assistant to discover the API first, then compose the right calls:

Use the justai MCP server. List my first 20 templates with template id, name, status, variant count, and whether metrics are available.

Use the justai MCP server. Find templates with metrics from the last 30 days, then summarize the top opportunities for a weekly performance report.

Use the justai MCP server. Fetch template <template_id> for the last 14 days. Use the returned dashboard metric fields to summarize sends, opens, clicks, and any meaningful variant differences.

Use the justai MCP server. List uploaded resources, find saved views for each resource, and tell me which views look useful for audience reporting.

Use the justai MCP server. Fetch template <template_id> with variant vars included, then show me the subject lines and HTML body for each variant.

Troubleshooting

Issue	Fix
Claude asks for OAuth Client ID or Secret	Leave both fields blank. The JustAI MCP server supports dynamic public client registration.
You see an API-key authorization page	The worker is misconfigured or outdated. Use the /mcp URL for the current deployment and ask your JustAI contact to confirm the OAuth console redirect is configured.
The client cannot send custom headers	Use OAuth. Claude Desktop custom connectors do not require custom headers.
Responses are too large	Ask for summaries first. Fetch one template at a time before setting include_variant_vars=true.
You need the docs MCP instead	Use the separate documentation MCP server at https://docs.justwords.ai/mcp.