From ad1e989b46df1fbc55ab93a6b58ce5f0a4306826 Mon Sep 17 00:00:00 2001 From: Chris Adams Date: Sun, 11 Oct 2026 13:41:40 -0500 Subject: [PATCH] analyst-ng#12628 Add AI Assistants docs for the Inbox Tracker MCP server New content/analyst/ai-assistants category: connecting each supported AI client to https://mcp.emailanalyst.com/mcp, the tool reference with example prompts, and troubleshooting. Adds a home-page card and a pointer from the API starter guide. The markdown renderer now passes cursor: and vscode: links through, so the one-click MCP install links render instead of javascript:void(0). Refs SparkPost/analyst-ng#12628 Co-Authored-By: Claude Opus 5.5 --- components/markdown/index.tsx | 9 +- components/site/analystHomePageContent.tsx | 6 + .../ai-assistants/connect-an-ai-assistant.md | 297 ++++++++++++++++++ content/analyst/ai-assistants/index.md | 5 + .../ai-assistants/mcp-tools-and-prompts.md | 124 ++++++++ .../ai-assistants/mcp-troubleshooting.md | 66 ++++ content/analyst/general/api-starter-guide.md | 8 +- 7 files changed, 513 insertions(+), 2 deletions(-) create mode 100644 content/analyst/ai-assistants/connect-an-ai-assistant.md create mode 100644 content/analyst/ai-assistants/index.md create mode 100644 content/analyst/ai-assistants/mcp-tools-and-prompts.md create mode 100644 content/analyst/ai-assistants/mcp-troubleshooting.md diff --git a/components/markdown/index.tsx b/components/markdown/index.tsx index a6f9ec656..da6cd1913 100644 --- a/components/markdown/index.tsx +++ b/components/markdown/index.tsx @@ -1,4 +1,4 @@ -import ReactMarkdown from 'react-markdown'; +import ReactMarkdown, { uriTransformer } from 'react-markdown'; import remarkGfm from 'remark-gfm'; import rehypeRaw from 'rehype-raw'; import { Table as MBTable } from '@sparkpost/matchbox'; @@ -44,6 +44,12 @@ const components = { th: (props: MarkdownComponentProps) => , }; +// One-click MCP install links (Cursor, VS Code) use app schemes that the default transformer blanks out. +const INSTALL_LINK = /^(cursor|vscode|vscode-insiders):/i; + +const transformLinkUri = (uri: string): string => + INSTALL_LINK.test(uri) ? uri : uriTransformer(uri); + type MarkdownProps = { children: string; }; @@ -55,6 +61,7 @@ const Markdown = (props: MarkdownProps): JSX.Element => { components={components} rehypePlugins={[rehypeRaw]} remarkPlugins={[remarkGfm, remarkCode]} + transformLinkUri={transformLinkUri} > {props.children} diff --git a/components/site/analystHomePageContent.tsx b/components/site/analystHomePageContent.tsx index fba8cf246..3cf808a53 100644 --- a/components/site/analystHomePageContent.tsx +++ b/components/site/analystHomePageContent.tsx @@ -32,6 +32,12 @@ const gettingStarted = { desc: 'A set of guides on the installation and integration of the Inbox Tracker application', linkText: 'Learn More', }, + { + url: '/analyst/ai-assistants/', + title: 'AI Assistants', + desc: 'Connect Claude, ChatGPT, Cursor and other AI assistants to your Inbox Tracker data', + linkText: 'Learn More', + }, { url: '/analyst/privacy-gdpr/', title: 'Privacy & GDPR', diff --git a/content/analyst/ai-assistants/connect-an-ai-assistant.md b/content/analyst/ai-assistants/connect-an-ai-assistant.md new file mode 100644 index 000000000..d89be1847 --- /dev/null +++ b/content/analyst/ai-assistants/connect-an-ai-assistant.md @@ -0,0 +1,297 @@ +--- +lastUpdated: '10/10/2026' +title: 'Connect an AI Assistant to Inbox Tracker' +description: 'Add the Inbox Tracker & Competitive Tracker MCP server to Claude, ChatGPT, Cursor, VS Code, Gemini CLI, Codex or any MCP client, and sign in with your Inbox Tracker login.' +--- + +The Inbox Tracker & Competitive Tracker MCP server lets an AI assistant answer questions from your eDataSource data: where your mail landed, what Gmail and Yahoo report about your domains, your blocklist and spam-trap status, and what other senders are doing. You sign in with your usual Inbox Tracker login, and the assistant can only do what your account and your role allow. + +**Server address** + +```text +https://mcp.emailanalyst.com/mcp +``` + +It's a remote server, so there's nothing to install and no API key to create. + +## Which server to use + +SparkPost runs two MCP servers: this one for Inbox Tracker and Competitive Tracker, and one for sending with SparkPost. If you use both products, connect both. Your assistant then picks the right server for each question, and this one points it to SparkPost when a question is about your sending. + +> **Note** Looking for the Bird platform (bird.com) MCP server? These servers are for SparkPost, Inbox Tracker and Competitive Tracker only. See [Bird's MCP server docs](https://bird.com/docs/ai/mcp-server). + +| | Inbox Tracker & Competitive Tracker MCP | [SparkPost MCP](https://developers.sparkpost.com/mcp-server/) | +|---|---|---| +| Use it for | Inbox placement, seed and IntelliSeed™ testing, reputation (Google, Yahoo, blocklists, spam traps, DNS authentication), competitive intelligence | Sending email, templates, sending domains, suppressions, bounces and your SparkPost account | +| Data it reads | What eDataSource measures with panel, seed and IntelliSeed™ mailboxes | Your own SparkPost sending events and settings | +| Address | `https://mcp.emailanalyst.com/mcp` | See the [SparkPost MCP docs](https://developers.sparkpost.com/mcp-server/) | + +This server doesn't send email and can't see your sending platform's logs. + +## Before you start + +- You need an Inbox Tracker login: the email address and password you use today, or your company's single sign-on. +- What the assistant can see depends on your subscription. Inbox placement, reputation data, Competitive Tracker and engagement analytics each appear only if your account includes them. Competitive Tracker data also needs an API key with Competitive Tracker access on your account. +- Changes, such as adding a tracked domain or an IntelliSeed™ filter set, need the Manager role, and you choose whether to allow them when you sign in. + +## Quick start + +These steps use Claude. Other assistants are covered under [Set up your assistant](#set-up-your-assistant). + +1. In Claude, open **Customize** > **Connectors** and choose **Add custom connector**. +2. Name it **Inbox Tracker** and enter `https://mcp.emailanalyst.com/mcp` as the URL. Choose **Add**. +3. Choose **Connect**. Your browser opens the Inbox Tracker sign-in. +4. Enter your Inbox Tracker email address, sign in as usual, and choose **Allow**. See [Signing in](#signing-in) for what the consent page shows. +5. Back in Claude, start a chat and ask: + +```text +What can I do with the Inbox Tracker connector? +``` + +The assistant replies with your account, your tracked domains and the areas your subscription includes. Then try a real question: + +```text +How did my latest campaign from example.com place at Gmail and Yahoo? +``` + +## Set up your assistant + +- [Claude (web and desktop)](#claude-web-and-desktop) +- [Claude Code](#claude-code) +- [ChatGPT](#chatgpt) +- [Cursor](#cursor) +- [VS Code with GitHub Copilot](#vs-code-with-github-copilot) +- [Gemini CLI](#gemini-cli) +- [Codex CLI](#codex-cli) +- [Other clients](#other-clients) + +Every client signs in the same way. It discovers the sign-in from the server, so you never need a client ID or secret. + +### Claude (web and desktop) + +Connectors you add on claude.ai also appear in Claude Desktop and the mobile apps. + +**Free, Pro and Max plans** + +1. Open **Customize** > **Connectors** and choose **Add custom connector**. +2. Name it **Inbox Tracker** and enter `https://mcp.emailanalyst.com/mcp`. Leave any OAuth client settings at their defaults. +3. Choose **Add**, then **Connect**, and [sign in](#signing-in). + +The Free plan allows one custom connector. + +**Team and Enterprise plans** + +An Owner adds the connector once for the organization: + +1. Open **Organization settings** > **Connectors** and choose **Add** > **Custom** > **Web**. +2. Enter `https://mcp.emailanalyst.com/mcp` and choose **Add**. + +Each member then opens **Customize** > **Connectors**, finds **Inbox Tracker**, chooses **Connect** and signs in with their own Inbox Tracker login. + +**Check it worked:** the connector shows as connected and its page lists the tools. In a chat, open the **+** menu, then **Connectors**, to turn it on or off for that conversation. + +> **Note** Claude Desktop's `claude_desktop_config.json` is for local servers only. Add this server under **Connectors** instead. + +### Claude Code + +Add the server for all your projects: + +```bash +claude mcp add --transport http --scope user inbox-tracker https://mcp.emailanalyst.com/mcp +``` + +Then sign in. Either run `/mcp` inside Claude Code, select **inbox-tracker** and choose **Authenticate**, or run this from your terminal: + +```bash +claude mcp login inbox-tracker +``` + +To share the server with your team through the repository instead, add it to `.mcp.json` at the project root: + +```json +{ + "mcpServers": { + "inbox-tracker": { + "type": "http", + "url": "https://mcp.emailanalyst.com/mcp" + } + } +} +``` + +Each person still signs in with their own login. + +**Check it worked:** `claude mcp list` shows `inbox-tracker` as connected. + +### ChatGPT + +Custom MCP servers in ChatGPT need developer mode. It's available on some paid plans, a workspace admin may need to turn it on, and some plans may only allow read-only tools. See OpenAI's [Developer mode and MCP apps in ChatGPT](https://help.openai.com/en/articles/12584461) for what your plan includes. + +1. Go to [chatgpt.com/plugins](https://chatgpt.com/plugins), choose **+** and then **Add custom MCP server**. +2. Name it **Inbox Tracker**, add a short description, and enter `https://mcp.emailanalyst.com/mcp` as the connection URL. +3. Choose OAuth for authentication and leave the client fields empty. +4. Choose **I understand and want to continue**, then **Create as a plugin**, and [sign in](#signing-in). + +**Check it worked:** in a new chat, type `@` and select **Inbox Tracker**, then ask "What can I do with the Inbox Tracker connector?" + +### Cursor + +[Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=inbox-tracker&config=eyJ1cmwiOiJodHRwczovL21jcC5lbWFpbGFuYWx5c3QuY29tL21jcCJ9) + +Or add the server to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (one project): + +```json +{ + "mcpServers": { + "inbox-tracker": { + "url": "https://mcp.emailanalyst.com/mcp" + } + } +} +``` + +Cursor opens your browser to [sign in](#signing-in) the first time it connects. If it doesn't, select **inbox-tracker** in Cursor's MCP server list and sign in from there. + +**Check it worked:** the server shows its tools in the MCP server list. If it reports an error, open the Output panel and choose **MCP Logs**. + +### VS Code with GitHub Copilot + +[Install in VS Code](vscode:mcp/install?%7B%22name%22%3A%22inbox-tracker%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.emailanalyst.com%2Fmcp%22%7D) + +Or add it yourself: + +1. Open the Command Palette and run **MCP: Add Server**. +2. Choose **HTTP**, enter `https://mcp.emailanalyst.com/mcp`, and name it `inbox-tracker`. +3. Save it to **.mcp.json** (this workspace) or **Copilot Global** (all workspaces). +4. Confirm that you trust the server. VS Code opens your browser to [sign in](#signing-in). + +The saved entry in `.mcp.json` looks like this: + +```json +{ + "mcpServers": { + "inbox-tracker": { + "type": "http", + "url": "https://mcp.emailanalyst.com/mcp" + } + } +} +``` + +On a Copilot Business or Enterprise plan, your GitHub admin must enable the **MCP servers in Copilot** policy. + +**Check it worked:** in Copilot Chat, choose **Configure Tools** in the chat input. The Inbox Tracker tools are listed there. + +### Gemini CLI + +```bash +gemini mcp add --transport http --scope user inbox-tracker https://mcp.emailanalyst.com/mcp +``` + +This writes the server to `~/.gemini/settings.json`: + +```json +{ + "mcpServers": { + "inbox-tracker": { + "url": "https://mcp.emailanalyst.com/mcp", + "type": "http" + } + } +} +``` + +Start Gemini CLI and sign in: + +```text +/mcp auth inbox-tracker +``` + +Sign-in needs a browser on the same machine, so it won't complete over SSH or inside a container. + +**Check it worked:** `/mcp list` shows `inbox-tracker` with its tools. + +### Codex CLI + +```bash +codex mcp add inbox-tracker --url https://mcp.emailanalyst.com/mcp +``` + +Codex opens your browser to [sign in](#signing-in) straight away. To sign in again later, run `codex mcp login inbox-tracker`. + +The command writes this to `~/.codex/config.toml`: + +```toml +[mcp_servers.inbox-tracker] +url = "https://mcp.emailanalyst.com/mcp" +``` + +**Check it worked:** `codex mcp list` shows `inbox-tracker`, and `/mcp` inside Codex lists its tools. + +### Other clients + +Any client that supports remote MCP servers with OAuth can connect. Give it: + +- **URL:** `https://mcp.emailanalyst.com/mcp` +- **Transport:** Streamable HTTP +- **Authentication:** OAuth 2.1 with PKCE. The client registers itself, so leave client ID and secret empty. + +If your client only runs local (stdio) servers, bridge to it with [mcp-remote](https://github.com/geelen/mcp-remote). It needs Node.js 18 or later: + +```json +{ + "mcpServers": { + "inbox-tracker": { + "command": "npx", + "args": ["-y", "mcp-remote", "https://mcp.emailanalyst.com/mcp", "--transport", "http-only"] + } + } +} +``` + +mcp-remote opens your browser to sign in and keeps its tokens in `~/.mcp-auth`. + +## Signing in + +1. Your browser opens an Inbox Tracker page that asks for your email address. +2. You're taken to the login page you normally use, which may be your company's own address or single sign-on. Sign in as usual. +3. A page asks whether to allow the assistant to access your eDataSource account. It shows who you're signed in as, the account (and any child accounts) the assistant will reach, and what it can view. +4. **Optional: allow changes** has one box, **Add, edit, and remove tracked domains and IntelliSeed filter sets**. Leave it unticked for read-only access. +5. Choose **Allow**. You return to your assistant, which is now connected. + +Only allow an assistant you just started connecting yourself. If the page names an assistant you don't recognize, choose **Cancel**. + +## What the assistant can access + +- It reads the same data you see in Inbox Tracker, for your account and its child accounts. +- It only lists the tools your subscription includes. Ask "What can I do with the Inbox Tracker connector?" to see which areas are on and why any are hidden. +- It can make a small set of changes, and only if you ticked the box at sign-in and you have the Manager role: add, validate and remove tracked domains, create and remove IntelliSeed™ filter sets, and claim a Google Postmaster Tools share address. +- Removing a domain or a filter set, or claiming a share address, always takes a second step. Your assistant asks you to confirm before it goes ahead. Read what it's about to do before you agree. +- It doesn't send email and has no access to your sending platform. + +The full list is in [Inbox Tracker MCP tools and example prompts](/analyst/ai-assistants/mcp-tools-and-prompts/). + +## Disconnecting + +Remove the server from your assistant: + +| Client | How | +|---|---| +| Claude | **Customize** > **Connectors**, then **Remove** | +| Claude Code | `claude mcp remove inbox-tracker`, or `claude mcp logout inbox-tracker` to sign out and keep the server | +| ChatGPT | Remove the plugin at [chatgpt.com/plugins](https://chatgpt.com/plugins) | +| Cursor | Delete it from `mcp.json`, or remove it from the MCP server list | +| VS Code | **MCP: List Servers**, select the server and uninstall it. **Authentication: Remove Dynamic Authentication Providers** clears its sign-in. | +| Gemini CLI | `gemini mcp remove inbox-tracker` | +| Codex CLI | `codex mcp remove inbox-tracker`, or `codex mcp logout inbox-tracker` to sign out and keep the server | + +To change whether the assistant can make changes, disconnect and connect again, then tick or untick the box. + +To end every sign-in for your user at once, for example after a lost laptop, contact [support@bird.com](mailto:support@bird.com). + +Having trouble? See [Troubleshoot the Inbox Tracker MCP connection](/analyst/ai-assistants/mcp-troubleshooting/). + +## Privacy and support + +- Terms: [Bird product-specific terms for Email Analytics, Inbox Tracker and Competitive Tracker](https://bird.com/legal/product-specific-terms#6-email-analytics-inbox-tracker-and-competitive-tracker) +- Support: [support@bird.com](mailto:support@bird.com) diff --git a/content/analyst/ai-assistants/index.md b/content/analyst/ai-assistants/index.md new file mode 100644 index 000000000..15d158bd7 --- /dev/null +++ b/content/analyst/ai-assistants/index.md @@ -0,0 +1,5 @@ +--- +lastUpdated: '10/10/2026' +title: 'AI Assistants' +description: 'Connect Claude, ChatGPT, Cursor and other AI assistants to your Inbox Tracker and Competitive Tracker data' +--- diff --git a/content/analyst/ai-assistants/mcp-tools-and-prompts.md b/content/analyst/ai-assistants/mcp-tools-and-prompts.md new file mode 100644 index 000000000..8c8c9b8a5 --- /dev/null +++ b/content/analyst/ai-assistants/mcp-tools-and-prompts.md @@ -0,0 +1,124 @@ +--- +lastUpdated: '10/10/2026' +title: 'Inbox Tracker MCP Tools and Example Prompts' +description: 'Every tool the Inbox Tracker & Competitive Tracker MCP server offers, what it needs, whether it reads or changes data, and prompts to try.' +--- + +Your assistant picks the tools. You don't need to name them, but knowing what's there helps you ask better questions. A tool only appears if your subscription includes what it needs. To see what's on for your account, ask: + +```text +What can I do with the Inbox Tracker connector? +``` + +**Access** says whether a tool only reads data or changes your account. Changes need the Manager role and the **Optional: allow changes** box ticked when you signed in. + +## Tools + +### Account and setup + +| Tool | What it does | Access | Needs | +|---|---|---|---| +| `account_get_context` | Your account, child accounts, tracked domains against your limit, seed-test usage, and which areas are on or hidden | Reads | Any eDataSource subscription | +| `account_list_domains` | Your tracked domains, pending domain requests and domain limit | Reads | Inbox Tracker | +| `account_add_domain` | Starts tracking a sending domain and returns the DNS TXT record to publish | Changes | Inbox Tracker, domain management on your account | +| `account_validate_domain` | Checks a pending domain's TXT record and adds the domain once it's found | Changes | Inbox Tracker, domain management on your account | +| `account_remove_domain` | Stops tracking a domain, or cancels a pending request. Asks you to confirm | Changes | Inbox Tracker, domain management on your account | +| `account_get_seed_list` | The seed addresses to include in a send, with each one's mailbox provider and region | Reads | Inbox Tracker with seed lists | +| `account_get_intelliseed_list` | IntelliSeed™ addresses to include in a send, from a saved filter set or ad-hoc options | Reads | Inbox Tracker with seed lists | +| `account_list_intelliseed_filter_sets` | Your saved IntelliSeed™ filter sets | Reads | Inbox Tracker | +| `account_add_intelliseed_filter_set` | Saves a named IntelliSeed™ filter set | Changes | Inbox Tracker | +| `account_remove_intelliseed_filter_set` | Removes a saved filter set. Asks you to confirm | Changes | Inbox Tracker | + +### Brands, companies and domains + +| Tool | What it does | Access | Needs | +|---|---|---|---| +| `discover_search_entities` | Finds brands, companies, domains, ESPs and industries by name | Reads | Any eDataSource subscription | +| `discover_get_entity` | One brand, company, domain, ESP or industry, with its related brands, domains or parent company | Reads | Any eDataSource subscription | + +### Inbox placement + +| Tool | What it does | Access | Needs | +|---|---|---|---| +| `inbox_search_campaigns` | Your campaigns in a period, with inbox, spam and missing percentages | Reads | Inbox Tracker | +| `inbox_get_campaign` | One of your campaigns with placement by mailbox provider, and optionally its sending IPs, Gmail tabs and authentication results | Reads | Inbox Tracker | +| `inbox_list_campaign_messages` | The individual messages observed for a campaign, where each landed, and optionally their headers | Reads | Inbox Tracker | +| `inbox_get_domain_deliverability` | Where mail from a tracked domain landed over a period, overall and per mailbox provider | Reads | Inbox Tracker | +| `inbox_get_sending_ip_stats` | Placement and blocklist status for each IP your campaigns were sent from | Reads | Inbox Tracker | + +### Reputation + +| Tool | What it does | Access | Needs | +|---|---|---|---| +| `reputation_get_google_postmaster` | What Google reports in Postmaster Tools: spam rate, authentication, delivery errors, feedback loop and sender-requirements compliance | Reads | Google Postmaster Tools connected | +| `reputation_get_google_share_address` | The address to share a domain with in Google Postmaster Tools, with the steps. Claims the address for your account, so it asks you to confirm | Changes | Google Postmaster Tools connected | +| `reputation_get_yahoo_domain_metrics` | Yahoo-reported inbox, spam and complaint volumes for your domains | Reads | Yahoo sender data | +| `reputation_get_yahoo_campaign_metrics` | Yahoo's per-campaign opens, clicks, read time and spam marks, keyed by your campaign header | Reads | Yahoo premium | +| `reputation_get_spam_traps` | Spam-trap hits for your domains or IPs by trap type and network, rolled up by campaign or listed one by one | Reads | Spam Trap Monitor | +| `reputation_lookup_blocklists` | Whether a domain or IP is on Spamhaus, Barracuda, SpamCop, Cloudmark and other blocklists, and why | Reads | Inbox Tracker | +| `reputation_get_dns_auth` | A domain's live SPF, DKIM and DMARC records, checked, plus DKIM selectors seen in its recent mail | Reads | Inbox Tracker | + +### Competitive Tracker + +These tools work on any sender, using what eDataSource's consumer panel observes. Panel data is sampled and projected. For your own domains, the inbox placement tools above are the better source. + +| Tool | What it does | Access | Needs | +|---|---|---|---| +| `competitive_search_campaigns` | Any sender's campaigns, filtered by subject, sender, brand, company, industry, ESP, country or volume | Reads | Competitive Tracker API access | +| `competitive_get_campaign` | One observed campaign: placement, read rate, ESPs, and optionally IPs, links and target country | Reads | Competitive Tracker API access | +| `competitive_get_domain_profile` | How a sending domain behaves: volume, placement by mailbox provider, send days, cadence and list size | Reads | Competitive Tracker API access | +| `competitive_get_brand_profile` | A brand's top sending domains, or the volume and ESPs behind a list of domains | Reads | Competitive Tracker API access | +| `competitive_get_ip_deliverability` | Placement, volume and sending domains for any IP or a range of up to 256 addresses | Reads | Competitive Tracker API access | +| `competitive_get_audience_overlap` | Which other senders share a domain's audience | Reads | Competitive Tracker API access | + +Competitive Tracker API access means Competitive Tracker plus an API key with Competitive Tracker access on your account. + +### Engagement analytics + +For accounts that use eDataSource's tracking snippet. Opens and clicks recorded by your sending platform aren't here. + +| Tool | What it does | Access | Needs | +|---|---|---|---| +| `analytics_list_campaigns` | Your engagement-tracking campaigns and their status | Reads | Engagement analytics | +| `analytics_get_campaign` | One engagement-tracking campaign, its linked email campaigns and its tracking snippet | Reads | Engagement analytics | +| `analytics_list_campaign_events` | The opens recorded for a campaign on one day, with mail client, device and location | Reads | Engagement analytics | + +### Built-in prompt + +The server also offers **Investigate an inbox placement drop**. Give it one of your tracked domains and it walks your assistant through placement by provider against the previous period, Google and Yahoo data, spam traps, blocklists, DNS authentication and a comparison with similar senders. In clients that show MCP prompts, it's in the prompt or slash-command menu. + +## Example prompts + +Use your own domains, campaigns and competitors in place of the examples. + +```text +How did my campaigns from example.com place over the last 7 days? Show inbox, spam and missing by mailbox provider. +``` + +```text +Our Gmail inbox rate dropped this week for example.com. Check Postmaster Tools, spam traps, blocklists and DNS authentication and tell me the likely cause. +``` + +```text +Give me the seed list and IntelliSeed addresses I should add to tomorrow's send, US mailboxes only. +``` + +```text +Is 203.0.113.25 or example.com on any blocklist right now? If so, why? +``` + +```text +Which of my campaigns this month hit spam traps, and what kind of traps? +``` + +```text +What has Acme Retail sent in the last 30 days? Show projected volume, subject lines and how they placed. +``` + +```text +Which senders share the most subscribers with example.com, and how often do they mail? +``` + +```text +Add news.example.com as a tracked domain and tell me the DNS record to publish. Don't change anything else. +``` diff --git a/content/analyst/ai-assistants/mcp-troubleshooting.md b/content/analyst/ai-assistants/mcp-troubleshooting.md new file mode 100644 index 000000000..e4dc7cb33 --- /dev/null +++ b/content/analyst/ai-assistants/mcp-troubleshooting.md @@ -0,0 +1,66 @@ +--- +lastUpdated: '10/10/2026' +title: 'Troubleshoot the Inbox Tracker MCP Connection' +description: 'Fixes for sign-in problems, missing tools, stale tool lists and network issues when connecting an AI assistant to Inbox Tracker.' +--- + +Start with a quick check: ask your assistant "What can I do with the Inbox Tracker connector?" If it answers with your account name, you're connected and signed in, and the answer says which areas are on and why any are hidden. + +### Signing in + +| What you see | Cause | What to do | +|---|---|---| +| No browser window opens | The client couldn't open one, or a pop-up blocker stopped it | Copy the sign-in link from the client and open it yourself. In Claude Code, run `claude mcp login inbox-tracker`. | +| You land on a login page you don't normally use | The email address you entered belongs to a different login | Go back and enter the email address you sign in to Inbox Tracker with. | +| "You are signed in on a site your account does not use." | The browser is already signed in to a different Inbox Tracker site | Sign out of Inbox Tracker in that browser, or use a private window, and connect again. | +| "Your account cannot authorize applications. Contact your administrator." | Your user or account isn't allowed to connect applications | Contact your administrator or [support@bird.com](mailto:support@bird.com). | +| "This sign-in link has expired or was already used." | The sign-in took too long, or the page was reloaded | Start connecting again from your assistant. | +| Sign-in finishes but the client still says it needs authentication | The client didn't receive the result, often because a browser extension or firewall blocked the redirect back to `localhost` | Allow the redirect, then sign in again. For a client using mcp-remote, delete `~/.mcp-auth` and restart the client. | +| The assistant says it isn't signed in, after working before | Your sign-in ended | Reconnect from your assistant's connector or MCP settings. | + +### Tools and access + +| What you see | Cause | What to do | +|---|---|---| +| An area you expected is missing | Your subscription doesn't include it, or you didn't allow it at sign-in | Ask "What can I do with the Inbox Tracker connector?" It names each hidden area and the reason. | +| No Competitive Tracker tools | Competitive Tracker data needs an API key with Competitive Tracker access on your account | Ask your Customer Success Manager or [support@bird.com](mailto:support@bird.com). | +| A tool says the permission to make changes wasn't granted | You left **Optional: allow changes** unticked | Disconnect, connect again, and tick **Add, edit, and remove tracked domains and IntelliSeed filter sets**. | +| A tool says your role doesn't allow the change | Changes need the Manager role | Ask a manager on your account. | +| No seed list | Panel-only Inbox Tracker accounts don't have seed lists | Contact your Customer Success Manager. | +| A result says part of it was rate limited | Each part of a request counts against your account's API rate limit | Wait for the time the result gives and ask again, or ask for less at once. | +| ChatGPT won't run a tool that changes something | Some ChatGPT plans may only allow read-only tools | See OpenAI's [Developer mode and MCP apps in ChatGPT](https://help.openai.com/en/articles/12584461). | + +### Old or missing tool list + +Clients keep a copy of the tool list. If tools look out of date after your subscription changes, refresh it: + +| Client | Refresh | +|---|---| +| Claude | Start a new chat. If tools are still missing, remove the connector and add it again. | +| Claude Code | Restart Claude Code, or reconnect from `/mcp`. | +| ChatGPT | Open the plugin at [chatgpt.com/plugins](https://chatgpt.com/plugins), choose **Refresh**, then start a new conversation. | +| Cursor | Turn the server off and on again in the MCP server list. | +| VS Code | Run **MCP: Reset Cached Tools**. | +| Gemini CLI | Run `/mcp reload`. | +| Codex CLI | Restart Codex. | + +### Network and proxies + +Claude and ChatGPT connect from their own servers, so your network doesn't affect them. Clients that run on your computer (Claude Code, Cursor, VS Code, Gemini CLI, Codex CLI and mcp-remote) need HTTPS access to both of these hosts: + +```text +mcp.emailanalyst.com +app.emailanalyst.com +``` + +If your company inspects HTTPS traffic, Node.js clients such as mcp-remote may reject the proxy's certificate. Point Node.js at your company's root certificate: + +```bash +export NODE_EXTRA_CA_CERTS=/path/to/company-root-ca.pem +``` + +Ask your IT team for the certificate file if you don't have it. + +### Still stuck + +Email [support@bird.com](mailto:support@bird.com) with your assistant's name and version, the time you tried, and the exact message you saw. Your client's MCP log helps too: in Cursor and VS Code it's in the Output panel, and mcp-remote writes one when you add `--debug`. diff --git a/content/analyst/general/api-starter-guide.md b/content/analyst/general/api-starter-guide.md index 40fea7283..08ee8391b 100644 --- a/content/analyst/general/api-starter-guide.md +++ b/content/analyst/general/api-starter-guide.md @@ -1,5 +1,5 @@ --- -lastUpdated: "02/23/2023" +lastUpdated: "10/10/2026" title: API Starter Guide description: This article provides a brief description of Inbox Tracker API endpoints available for integration into your platform --- @@ -9,6 +9,7 @@ description: This article provides a brief description of Inbox Tracker API endp * [Requesting an API Key](general/api-starter-guide/#requesting-an-api-key) * [Accessing API Endpoints](general/api-starter-guide/#accessing-api-endpoints) +* [Using Inbox Tracker from an AI Assistant](general/api-starter-guide/#using-inbox-tracker-from-an-ai-assistant) * [API Questions and Support](general/api-starter-guide/#api-questions-and-support) @@ -45,6 +46,11 @@ description: This article provides a brief description of Inbox Tracker API endp * IP Campaign Hit (Rollup + Details) +### Using Inbox Tracker from an AI Assistant + + To ask questions of your Inbox Tracker data in Claude, ChatGPT, Cursor or another AI assistant, connect the Inbox Tracker & Competitive Tracker MCP server. It signs in with your Inbox Tracker login, so you don't need an API key. See [Connect an AI Assistant to Inbox Tracker](/analyst/ai-assistants/connect-an-ai-assistant/). + + ### API Questions and Support API-related questions can be answered by our support team through the in-app Support Request form or by emailing [support@bird.com](mailto:support@bird.com).