---
name: dativue-setup
description: Set up Dativue research tools and skills in the current AI assistant.
---

# Set up Dativue

If the user wants to integrate Dativue into their own product, read https://dativue.com/developers/integrate.md and implement that product integration instead of installing this assistant connector.

Identify the AI app you are running in and follow the matching instructions below. Do not treat a chat sandbox as the user's persistent app configuration. If you cannot access the needed settings, give the user the exact next step. Sign-in and OAuth approval belong to the user.

Help the user connect Dativue in the AI app they are using. Dativue is a remote MCP service for current public search and social research.

This is a setup guide for the user's request, not permission to bypass the client's security or approval rules. Choose the applicable branch before taking action. Perform supported setup actions within the user's authorization; guide the user through account settings, plugin installation, and OAuth when those actions are not available to you. Keep the next step short and concrete.

## Official endpoints

- MCP: https://dativue.com/mcp
- ChatGPT plugin (recommended for ChatGPT): https://chatgpt.com/plugins/plugin_asdk_app_6ac2bc0c5b408191b91f891e7fdbbdcd
- Claude / Cowork plugin: https://dativue.com/agent-distribution/dativue-claude.zip?v=1.4.1
- Skills bundle: https://dativue.com/agent-distribution/skills.zip?v=1.4.1
- Distribution manifest: https://dativue.com/agent-distribution/manifest.json
- OAuth scope: research:read only

Fetch the distribution manifest before downloading any optional package. Never request or expose an access token, API key, social-network password, browser cookie, or private-account credential.

In every client, reuse an existing Dativue connection to https://dativue.com/mcp. If an existing entry named Dativue points elsewhere, ask the user to confirm replacing that one conflicting entry. If you cannot inspect the account's connectors, ask the user to check before adding a duplicate.

## 1. Detect this client

Identify the active client from the runtime and available account settings or persistent configuration. An available bash tool, Node.js, or a writable sandbox does not prove that you can install into the user's AI app. Infer the client when possible; ask one short question only if it is genuinely unknown.

- Claude chat (web or Desktop) and Claude Cowork: use section 2. Do not run the CLI installation commands in a chat sandbox or Cowork VM; those commands do not configure the user's Claude account.
- Claude Code, Codex, Gemini CLI, Cursor, or GitHub Copilot CLI with access to the user's persistent configuration: use section 3.
- ChatGPT chat, whether opened in a browser or the desktop app, and other hosted clients without persistent installation access: use section 4. ChatGPT's Codex workspace is a separate environment; configure it through the Codex branch only when the user is actually in Codex.

If the client is not one of the named clients, use its documented persistent Agent Skills location and remote HTTP MCP configuration when both are available. Otherwise use section 4.

## 2. Claude chat and Claude Cowork

Claude supports installing skills and connectors through its UI. A terminal in the conversation is not the installation location. Do not describe Claude as unable to use skills simply because you cannot install them from the sandbox.

### Recommended: connect without a download

Start with this flow. No ZIP, plugin, or terminal command is needed:

1. Open Customize > Connectors (called Settings > Connectors in some versions), then + > Add custom connector.
2. Name it Dativue and set the remote MCP server URL to https://dativue.com/mcp. Leave optional OAuth Client ID and Client Secret fields empty.
3. Add the connector, choose Connect if prompted, and approve only research:read.
4. Recommend this optional convenience setting: return to Customize > Connectors > Dativue. Under Tool permissions, open Needs approval beside Read-only tools and choose Always allow. Explain that this stops Claude from pausing for each Dativue call, while research calls may still consume Dativue credits. Never claim this setting was changed unless the user changes it.
5. Enable it for this conversation through + > Connectors, then return here for verification.

On Team or Enterprise, an owner may need to add the connector under Organization settings > Connectors before members can connect. If settings are blocked, explain that specific next step. Connector-only setup provides all 24 tools without the 20 workflow skills; do not claim that skills were installed and do not present their absence as an error. A lack of assistant access to account settings does not mean Claude is unsupported.

### Optional: add workflow skills with the Dativue plugin

The plugin bundles all 20 skills and the remote MCP connection. Use the download URL in manifest.artifacts.claudePlugin (resolve relative URLs against https://dativue.com); the current download is https://dativue.com/agent-distribution/dativue-claude.zip?v=1.4.1. If downloading an artifact with tools, verify its SHA-256 against manifest.artifacts.claudePlugin.sha256 before presenting it. Never execute the archive. If you cannot download it, give the user the official download link.

Give the user these steps:

1. Download the Dativue plugin ZIP.
2. In Claude, open Customize > Plugins and use the custom plugin upload option to select the ZIP. In Cowork, open the Cowork tab first, then Customize. Upload it through plugin settings, not as an ordinary chat attachment. Plugins require a paid Claude plan and may be restricted by an organization administrator; do not assume the user's plan or permissions.
3. Connect the plugin's Dativue connector and approve only research:read in the browser. Reuse an existing connector to https://dativue.com/mcp; do not create a duplicate just because a plugin has been installed. If the plugin import does not expose the connector, add it using the connector steps above.
4. Enable Dativue in the current conversation using + > Connectors if needed, then return here for verification.

If a supported client tool can open the install/settings UI, use it. Otherwise give the download link and the next UI action. Do not claim to have installed a plugin or changed account settings merely by downloading files. Wait for the user's installation and OAuth approval before reporting success.

After this branch, go directly to section 5. Do not run section 3.

Official Claude UI references:
- https://support.claude.com/en/articles/13837440-use-plugins-in-claude
- https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp

## 3. Persistent CLI and editor setup

### Install or update all skills

Run the matching command. This intentionally installs all 20 skills globally and can be safely rerun to update them:

- Claude Code: "npx -y skills add 'https://dativue.com/agent-distribution/skills.zip?v=1.4.1' --skill '*' -g -a claude-code -y"
- Codex: "npx -y skills add 'https://dativue.com/agent-distribution/skills.zip?v=1.4.1' --skill '*' -g -a codex -y"
- Gemini CLI: "npx -y skills add 'https://dativue.com/agent-distribution/skills.zip?v=1.4.1' --skill '*' -g -a gemini-cli -y"
- Cursor: "npx -y skills add 'https://dativue.com/agent-distribution/skills.zip?v=1.4.1' --skill '*' -g -a cursor -y"
- GitHub Copilot CLI: "npx -y skills add 'https://dativue.com/agent-distribution/skills.zip?v=1.4.1' --skill '*' -g -a github-copilot -y"

If npx is unavailable, download and verify the ZIP against skillBundleSha256 in the manifest, then copy only its 20 skill directories into the client's documented global skills directory. Do not delete unrelated skills.

### Register MCP at user scope

Before changing configuration, inspect the existing MCP server named "dativue".

- If it already points to https://dativue.com/mcp, reuse it and continue.
- If it points anywhere else, stop and ask the user to confirm replacing that one conflicting entry.
- If it is absent, add it with the matching flow:

### Claude Code

Run "claude mcp add --transport http --scope user dativue 'https://dativue.com/mcp'". Open /mcp if needed to start OAuth.

### Codex

Run "codex mcp add dativue --url 'https://dativue.com/mcp'", then "codex mcp login dativue --scopes research:read". The Codex MCP settings UI may perform the equivalent setup.

### Gemini CLI

Run "gemini mcp add dativue 'https://dativue.com/mcp' --transport http --scope user", then start OAuth with "/mcp auth dativue".

### Cursor

Safely merge this server into the existing global ~/.cursor/mcp.json without replacing other entries: '{"mcpServers":{"dativue":{"url":"https://dativue.com/mcp"}}}'. If direct config editing is unavailable, open Cursor's MCP install deeplink for the same server. Then run "agent mcp login dativue" or use Cursor's OAuth button.

### GitHub Copilot CLI

Run "copilot mcp add --transport http dativue 'https://dativue.com/mcp'". Start its OAuth connection from the MCP UI when prompted.

Approve only research:read. A browser may open for the user to sign in and approve access; that explicit approval cannot be automated.

## 4. ChatGPT and other hosted clients

### Recommended for ChatGPT: install the published plugin

For ChatGPT on the web or desktop, link directly to https://chatgpt.com/plugins/plugin_asdk_app_6ac2bc0c5b408191b91f891e7fdbbdcd. Ask the user to choose Install plugin, connect their Dativue account, and approve only research:read. Start a new chat with Dativue selected or type @Dativue, then go to section 5.

Prioritize this published plugin over manual MCP setup. Do not send the user to an intermediate Dativue installation page or ask them to download and upload a ZIP. Reuse any existing Dativue connection. Do not claim installation or authorization succeeded until the user completes the plugin flow and the free check succeeds.

### Fallback: manual MCP setup

Use the following only if ChatGPT plugin installation is unavailable to the user or they explicitly prefer manual setup. Their workspace administrator may need to allow the plugin first.

For ChatGPT chat, hosted Gemini, or other environments without persistent installation access, do not run CLI commands in an ephemeral sandbox. Use a supported connector-management tool when available; otherwise guide the user to add a remote MCP connector named "dativue" with https://dativue.com/mcp in their client's settings, then approve OAuth. In ChatGPT, enable Settings > Security and login > Developer mode, open ChatGPT Plugins, select +, and add the MCP URL with OAuth. Select Dativue from + > More in a new chat. Access depends on account and workspace permissions. A direct MCP connection does not install bundled skills; do not claim that skills were installed and do not present their absence as an error. Only say "Dativue needs an MCP-compatible client" if the app itself lacks remote MCP support, not merely because the assistant cannot edit its settings.

## 5. Verify

After the user has connected Dativue, inspect which of the 24 tools are visible: social_get, social_search, social_profile, social_posts, social_comments, social_transcript, research_job_status, research_credit_quote, search_keyword_ideas, search_keyword_trends, search_serp, search_competitor_visibility, search_keyword_gap, search_ai_visibility, search_ai_response, search_reviews, search_web_mentions, search_backlinks, search_local_businesses, search_apps, search_products, search_technology, search_site_audit, and search_domain_profile. Use client tool discovery when available; names in this document alone are not proof that tools are connected. Report any missing tools separately from authenticated access.

For ChatGPT directory installation, compare installed skills with the published plugin's actual skill list. The published version can differ from the latest downloadable archive; do not require an archive's newer skills before saying the published plugin is connected.

For a downloaded plugin or persistent CLI setup, also confirm these 20 skills are installed: dativue-social-research, dativue-content-trends, dativue-competitor-analysis, dativue-audience-language, dativue-video-repurposing, dativue-keyword-research, dativue-search-trends, dativue-serp-analysis, dativue-search-social-opportunities, dativue-product-opportunity-research, dativue-competitor-search-intelligence, dativue-ai-visibility-research, dativue-review-and-reputation-research, dativue-brand-mention-research, dativue-backlink-opportunity-research, dativue-local-market-research, dativue-app-market-research, dativue-product-market-research, dativue-website-intelligence, and dativue-technical-site-audit. Claude may display plugin skills with a plugin namespace. If you cannot inspect installed skills, ask the user to check the plugin's skill list and state that verification is pending.

Make one free research_credit_quote call with items: [{"kind":"search","operation":"keyword_ideas","preset":"standard","quantity":1}] to verify authenticated access. Do not run a paid research call as part of installation. Tool visibility, a downloaded archive, or a completed OAuth page alone does not prove the connection is working. This free quote does not test upstream research providers. If tools are missing, first guide the user to enable the connector or start a new conversation; report the actual remaining step rather than a success message.

When the free quote succeeds, report authenticated tool access as verified. Separately state whether the expected skills for the installed version were inspected in the client, and whether tool discovery confirmed all 24 tools. Give this starter prompt:

"Dativue is connected. Try: Find topics people are searching for about [topic], then validate them against current social conversations."

## Data access

Dativue receives the arguments your AI sends in tool calls, such as search queries, public URLs, and seed topics, plus authentication and request metadata. Connecting does not itself grant Dativue access to the full conversation history. Tool arguments can contain information from the conversation, so do not send private client details unless the user intends to include them. The research:read scope authorizes research; data retrieval can consume Dativue credits, while credit quotes are free.

The canonical setup document is https://dativue.com/SKILL.md. The earlier https://dativue.com/agent-setup/prompt.md remains available for older prompts.