Docs

MCP

Connect Cursor (or any MCP client) to Trivue. Hosted MCP exposes inspect_remote_url for public URLs. The local Dev inspector (recommended) exposes inspect_remote_url and inspect_local_url. Hosted Streamable HTTP inspects public URLs only. Trivue never fetches your loopback from the cloud.

Auth

Where to get the environment secret

Open Dashboard → Developer, View an environment, and copy its secret. Put it in the local inspector as TRIVUE_API_KEY (sent as x-trivue-api-key). If that env var is unset, trivuedev mcp falls back to credentials.json after trivuedev login <secret>. You must be signed in to open that page.

Choose a transport

Local Dev vs hosted HTTP

Use local stdio (recommended) when the agent should inspect both public URLs and your app on http://localhost, 127.0.0.0/8, or ::1. The Dev inspector runs on your laptop. For localhost it fetches HTML and social images locally, then sends them to Trivue. Name the server trivue-url-metadata-dev-inspector.

Use hosted Streamable HTTP when the agent only needs public production URLs. Point the client at /api/mcp and name the server trivue-url-metadata-remote-inspector. Hosted MCP cannot inspect localhost.

Private LAN and cloud metadata hosts stay blocked on both transports.

Recommended

Add local Dev inspector

This is the setup to use for day-to-day development: public URLs and localhost. Point Cursor at trivuedev mcp if you have the trivuedev CLI. Prefer TRIVUE_API_KEY in the MCP config (the environment secret from Dashboard → Developer).

Install the CLI from trivuedev install docs, then use the snippet below. Local inspect requires the CLI.

mcp.json · trivuedev

{
  "mcpServers": {
    "trivue-url-metadata-dev-inspector": {
      "command": "trivuedev",
      "args": ["mcp"],
      "env": {
        "TRIVUE_API_KEY": "YOUR_ENVIRONMENT_SECRET"
      }
    }
  }
}

Public URLs only

Add hosted Streamable HTTP

In Cursor MCP settings (or .cursor/mcp.json), add a server whose URL is https://trivue.orashus.com/api/mcp. Hosted MCP is still public (no environment secret) until Extra 047. Config keys vary slightly by Cursor version; keep this shape. See Cursor MCP docs.

Hosted MCP cannot inspect localhost

Streamable HTTP runs on Trivue's servers. Loopback targets (localhost, 127.0.0.0/8, ::1, *.localhost) are rejected as BLOCKED_HOST / BLOCKED_ADDRESS. Use inspect_local_url on the local Dev inspector for those URLs.

mcp.json · hosted

{
  "mcpServers": {
    "trivue-url-metadata-remote-inspector": {
      "url": "https://trivue.orashus.com/api/mcp"
    }
  }
}

After the server is connected, paste a prompt like this so the agent calls inspect_remote_url:

Example prompt

Use the Trivue inspect_remote_url tool on https://example.com. Summarize the Trivue Score, the top Fix First issues, whether the social image is reachable, and how X and Facebook are likely to preview the link.

Tools

inspect_remote_url and inspect_local_url

Hosted MCP has one tool: inspect_remote_url with { "url": "https://…" } (same URL rules as the inspect API). Success is a text part containing full inspection JSON (metadata, diagnostics, Trivue Score, platform previews, image analysis).

The local Dev inspector registers the same inspect_remote_url for public URLs, plus inspect_local_url for localhost. For loopback it fetches HTML and social images on your machine, then posts them to Trivue with your environment secret. Hosted MCP has no local tool. Public image URLs stay as URLs in JSON.

Errors are { "code", "message" } using the same codes as POST /api/inspect. Messages never include resolved IPs.