SigRank Vercel Integration

The SigRank Vercel integration connects your Vercel projects to the SigRank MCP (Model Context Protocol) endpoint. This gives your deployed AI agents and development tools direct access to operator evaluation, exchange signals, and SigRank's metric tools without custom wiring.

The integration provides:

• MCP endpoint access — connect any MCP-compatible client to https://signalaf.com/api/mcp
• Project-owned relay — one-click deploy a Vercel project that relays MCP traffic to SigRank, keeping your deployment URL as the entry point
• Resource import — import your existing operator identity, exchange signals, and MCP configuration into your Vercel project
• Environment variable sync — the MCP endpoint URL is automatically added to your project environment variables

SigRank evaluates AI operators — developers using AI coding tools — not AI models. The integration does not evaluate your Vercel deployments themselves; it provides tools that agents running in or alongside your deployments can use.

Via Vercel Marketplace

1. Navigate to the SigRank integration page on the Vercel Marketplace.
2. Click Add.
3. Select the Vercel project you want to connect.
4. Choose environments: Production, Preview, Development (all three recommended).
5. Click Connect.
6. You will be redirected to https://signalaf.com/vercel/config to complete configuration.

Via Vercel CLI

vc i sigrank

This opens the same installation flow from your terminal. Run it in your project directory after vercel link.

After installation

The integration adds the following environment variable to your project:

• SIGRANK_MCP_URL — the canonical MCP endpoint URL (https://signalaf.com/api/mcp)

If you used a custom prefix during installation, the variable name will include that prefix (e.g., SIGRANK_SIGRANK_MCP_URL).

After installation, you are redirected to the configuration page. This page shows:

• Installation status (active, pending, or revoked)
• Your configuration ID
• The canonical MCP endpoint URL with a copy button
• What the integration provides
• Links to MCP documentation and the acquisition page

You can return to the configuration page at any time from your Vercel dashboard: Integrations → SigRank → Configure.

Existing accounts

If you already have a SigRank account, your operator identity and MCP configuration are automatically available after installation — no separate import step is needed. Your codename, agent key, and exchange signals are accessible via the configuration page.

The canonical MCP endpoint is:

https://signalaf.com/api/mcp

The endpoint uses MCP SDK v2 with Streamable HTTP transport. Any MCP-compatible client can connect directly.

Client configuration

Add the following to your MCP client configuration (e.g., Claude Desktop, Cursor, or any MCP-compatible agent):

{
  "mcpServers": {
    "sigrank": {
      "url": "https://signalaf.com/api/mcp"
    }
  }
}

Project-owned relay (optional)

For a Vercel-native deployment URL, you can deploy the SigRank MCP relay starter kit. This gives you a *.vercel.app/api/mcp endpoint that relays to the canonical SigRank endpoint. The relay keeps implementation and metric logic centralized in SignalAF — you don't fork the tools.

The starter kit is available at sigrank-mcp/examples/vercel-remote-mcp with a one-click deploy button.

Discovery

The canonical endpoint publishes MCP discovery metadata at:

• /.well-known/mcp.json — MCP server discovery
• /llms.txt — LLM-readable site summary

Verify the MCP endpoint is live

curl -s https://signalaf.com/api/mcp | head -20

Verify your relay deployment

If you deployed the project-owned relay, use the diagnostic tool on the acquisition page to verify your *.vercel.app deployment is correctly serving the MCP relay.

The diagnostic tool validates:

• HTTPS protocol is used
• The host is a *.vercel.app domain
• No credentials or ports in the URL
• The endpoint responds to MCP protocol requests

Verify environment variables

vercel env ls

Confirm SIGRANK_MCP_URL is present in your project's environment variables.

The integration requests the following Vercel API scopes:

The integration does not request: Deployment Checks, Global Project Environment Variables, Project Protection Bypass, Domains, Global Config, or Drains.

The integration follows SigRank's privacy-first principles:

• No prompt content — the MCP endpoint exchanges tool calls and responses (operator metrics, signal data, wiki entries). It never receives or processes your code, prompts, or conversation content.
• No deployment source access — the integration reads deployment status (URL, state) but does not access your source code, build logs, or runtime data.
• OAuth token storage — the Vercel access token is stored server-side in a Supabase table protected by Row-Level Security. It is never exposed to the browser or in rendered pages.
• No third-party data sharing — the integration does not share your Vercel project data with any third party. The OAuth token is used only to read project/deployment metadata for the configuration page.
• Analytics — SigRank uses PostHog for product analytics. Page views on the configuration page are tracked anonymously. No token content, no source code, no deployment secrets are ever tracked. See our Privacy Policy for full details.

To uninstall the integration:

1. Go to your Vercel dashboard → Integrations → SigRank.
2. Click Settings.
3. Click Delete SigRank.

When you uninstall:

• The OAuth access token is revoked and marked as “revoked” in the SigRank database.
• The integration stops receiving Vercel API access for your projects.
• Environment variables added by the integration (SIGRANK_MCP_URL) remain in your project until you manually remove them via vercel env rm.
• Your SigRank account, operator data, and exchange history are not affected. Uninstalling only severs the Vercel connection.
• Any deployed MCP relay continues to work — it forwards to the canonical endpoint independently of the integration.

To fully remove the relay, delete the relay project from your Vercel dashboard separately.