You can connect Perspective to Claude using the Model Context Protocol (MCP), and once it’s connected, Claude can pull mobile funnel numbers, lead data, and campaign stats straight into a conversation instead of you opening a dashboard to check them yourself. This guide covers what Perspective’s MCP server does, how to connect it directly or through a gateway, and why gate currently tracks its OAuth as restricted rather than one-click.

What the Perspective MCP server actually does

Perspective publishes a remote MCP server at api.perspective.co/mcp that exposes mobile funnels, leads, and campaign stats as tools Claude can call directly. See the Perspective server page in gate’s directory for its current tool list and connectivity status. Prompts like these fit the shape of what the server is for:

  • “What’s the install-to-signup drop-off for this week’s campaign?”
  • “Pull the lead list from the funnel we launched last month.”
  • “Compare this campaign’s stats to the one before it.”

Like most servers in gate’s catalog that act on a real account, Perspective’s MCP server sits behind OAuth. Marketing data like this doesn’t read as sensitive the way a bank account or a password manager does, but a lead list is still real contact information collected from real people who filled out a form, not a number a teammate would mind you checking — which is worth keeping in mind for what you let an AI client do with it once it’s in context.

The catch: Perspective’s OAuth isn’t open to every client yet

Some servers in gate’s directory — Notion, Todoist, Airtable — let any AI client register itself and go straight through a one-click OAuth consent screen. Perspective is one of a handful where that isn’t the case today: gate’s catalog currently tracks its connectivity as restricted, meaning the vendor’s OAuth only admits clients it has allow-listed in advance rather than opening registration to any client that shows up. In practice, that can mean a connection attempt from a new or less-common client fails at the authorization step, even though the server itself is real and documented.

This is the same gap covered in MCP OAuth scopes explained: a server supporting OAuth in principle isn’t the same claim as every client being able to walk through it today. If you hit an “unauthorized client” error connecting Perspective, that’s the most likely reason — not a mistake in your setup. See the unauthorized client error explained for the general pattern and workarounds. Whether a given client can connect changes as vendors expand their allow-list over time, so it’s worth checking again later if it doesn’t work on your first attempt.

Option 1: Connect Perspective to Claude directly

If the client you’re using is one Perspective currently admits, the setup is:

  • Open Claude’s connector or MCP settings.
  • Add a remote server pointing at Perspective’s MCP endpoint at api.perspective.co/mcp.
  • Sign in with your Perspective account when prompted and approve the requested scopes.

That’s enough if Claude is the only AI client you use with Perspective. The tradeoff shows up once you add a second client — ChatGPT for a quick check, Cursor for pulling numbers into a build — or a second person on the marketing team: each one needs its own attempt at the same OAuth step, with the same chance of hitting the allow-list wall independently.

Option 2: Connect it once, through a gateway

If you’re already juggling more than one MCP server or more than one AI client, wiring each pair directly gets old fast — that’s the connection sprawl covered in what an MCP gateway is. The idea is to connect Perspective (and everything else) to one gateway URL, then point every AI client at that single URL instead of reconfiguring each one and re-running the OAuth step per client.

With gate specifically, connecting Perspective looks like this: add gate’s gateway URL to Claude once, then pick Perspective from the Perspective server page in the directory and sign in the same way you would directly. gate’s catalog tracks each server’s currently verified connectivity — including cases like this one, where a vendor’s OAuth is still allow-listed — so you know what to expect before you start, instead of finding out mid-flow. See the full list of servers on the MCP servers page.

What to check before you connect your campaign data

A funnel and lead tool is lower-stakes than one that touches money or production systems, but it’s still real data about real people, and worth a quick check before you hand it to an AI client:

  • Read, or read and export? A tool that reports funnel stats back into the conversation is low-risk. A tool that can export or forward a full lead list somewhere else is a different category — check the actual tool list rather than assuming it’s read-only. gate’s free MCP security scanner lists every tool a server exposes, no signup required.
  • Who else on the team sees the output? Lead data pasted into a chat transcript can end up somewhere it wasn’t meant to — shared with a client, copied into a doc, logged by whatever client you’re using. Treat an AI client’s output the same way you’d treat an export from the dashboard itself.
  • Could a campaign name or lead note carry text that steers Claude? Free-text fields from a form — a lead’s own note, a campaign description someone typed in a hurry — are the kind of untrusted content covered in the confused deputy problem in MCP: if Claude reads text containing embedded instructions and acts on them, the tool call is still fully authorized — it’s just doing something you didn’t intend.
  • One grant per team, not one per teammate. If more than one person on marketing connects Perspective to their own client, a shared, revocable setup beats everyone holding their own grant — the same question covered in MCP access control for teams.

Troubleshooting the connection

  • “Unauthorized client” or the OAuth screen never appears. Most likely the allow-list issue above — the client you’re using may not be one Perspective currently admits for this endpoint.
  • Sign-in succeeds but a funnel or lead you expect doesn’t show up. Perspective’s tools respect your account’s own permissions; a funnel you don’t have access to in the dashboard won’t show up here either.
  • Tools disappear after a Perspective update. Remote servers can change their tool list without warning. If you’re connected through a gateway, that kind of change is exactly what drift detection is meant to catch — see how MCP rug pulls work for why a one-time review isn’t enough.
Where gate fits: gate’s directory lists each server’s currently verified connectivity — one-click OAuth, key-based, or allow-listed like Perspective — so you know what kind of setup to expect before you start. Every server is scanned for prompt injection before it goes live, and every call goes into a plain-language log, which matters for marketing and lead data the same way it does for anything else connected to your AI client. See the full gateway at /mcp-gateway.

The bottom line

Connecting Perspective to Claude with MCP is a normal OAuth flow when the client you’re using is one Perspective currently allows — direct if it’s your only client, or once through a gateway if you want the same funnel and lead data shared and governed across every AI client on the team. If the connection fails at the authorization step, that’s worth reading as “not allow-listed yet” rather than a broken setup. Either way, know whether the tool only reports numbers back or can export a lead list elsewhere — that distinction matters more here than the dashboard surface suggests.