Connect IMAccelerator

IMAccelerator is an MCP server that lets Claude read this dashboard directly. It sees the same numbers you see here, with the same rules applied. Ask it “which webinar made the most money?” and it answers from live data instead of guessing.

Server URL

https://track.tijarahinstitute.com/mcp

Read-only. Nothing Claude does here can change or delete anything.

Which method should I use?

Recommended Sign in with Google

You’re using Claude Desktop or claude.ai. This is the normal way.

Needs nothing but your work account.

Fallback Access token

Claude Code, scripts, or if the first method fails.

Needs Node.js and the token below.

Sign in with Google Recommended

No token, no config file. You approve it once with your work account.

In Claude, open Settings → Connectors.
Click Add custom connector.
Paste the URL: https://track.tijarahinstitute.com/mcp
Leave “OAuth Client ID” and “OAuth Client Secret” empty. They look required. They are not: Claude registers itself automatically.
Click Add, then Connect.
Sign in with your @imaccelerator.com Google account if asked, then click Connect on the approval screen.

Only @imaccelerator.com accounts can approve this. That’s stricter than dashboard login on purpose. The MCP can read revenue, buyer journeys and registrant contact details, so guest accounts can’t grant themselves access.

Access token Fallback

A small local program (mcp-remote) sits between Claude and the server and attaches your token. Use this for Claude Code, or if the first method doesn’t work.

Your token

Visible to admins only. If you’re signed in and still can’t see it, ask an admin for it.

Claude Desktop

Open Settings → Developer → Edit Config, then paste this. If the file already lists other servers, add the IMAccelerator block alongside them rather than replacing everything.

claude_desktop_config.json

{
  "mcpServers": {
    "IMAccelerator": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://track.tijarahinstitute.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Don’t tidy up that missing space after Authorization:. Windows mangles spaces inside args, so the space lives in the env value instead, where it’s safe.

Then fully quit and reopen Claude Desktop. Closing the window isn’t enough (⌘Q on Mac, quit from the system tray on Windows). The first start takes 10–20 seconds while it downloads mcp-remote.

Claude Code

Terminal

claude mcp add --transport http imaccelerator \
  https://track.tijarahinstitute.com/mcp \
  --header "Authorization: Bearer YOUR_TOKEN_HERE"

Check it worked

Open the connector menu in Claude. IMAccelerator should be listed with nine tools. Then ask it something only this dashboard knows:

Ask Claude

Why are WhatsApp joins low compared to previous webinars?

It should come back with every show’s join rate, not a general answer.

What you can ask it

Ask about	Examples
Comparing shows	“Has attendance been sliding?” · “Which show had the best ROAS?”
One show	“How did Aug 2 do?” · “Which landing page converted best?”
Ads	“Which ad was cheapest?” · “Which creative hooks best?”
Sales team	“Who’s the best closer?” · “Who rings bookings fastest?”
Revenue	“Where did revenue come from last month?”
Data health	“Is the data up to date?”
Anything else	It can run read-only SQL against the database for one-off questions.

It knows the house rules. The tools carry the same definitions the dashboard uses: that a blank attendance means “Zoom told us nothing” rather than “nobody came”, that costs divide by ad-sourced leads only, that a small sample can’t win a ranking. So its answers should match what you see here.

If it doesn’t connect

No “Connect” button, or it fails immediately Try the access token method.
“Not permitted” You’re signed in with a non-work account. Sign out of Google and back in with @imaccelerator.com.
The token method shows nothing in Claude Check Node.js is installed (node -v in a terminal), then check Settings → Developer for the error.
Still stuck The server logs say what happened: journalctl -u ima-mcp -f on the VPS.