home / mcp / arcate mcp connect server

Arcate MCP Connect Server

Provides remote access to Arcate signals, roadmaps, and feedback endpoints for AI agents via a remote HTTP MCP server.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "bicavito-arcate-mcp": {
      "url": "https://eshuikffwhaxcvkzaewj.supabase.co/functions/v1/mcp-server"
    }
  }
}

Arcate MCP Connect is a remote HTTP server that gives AI agents direct access to your Arcate product discovery workspace. It lets you read signals, browse your roadmap, and write new feedback back into your system through a simple URL-based connection, without requiring any local installation on your side.

How to use

You connect your MCP client to Arcate using a dedicated HTTP endpoint. Start by generating an API key in your Arcate workspace and then configure your MCP client to point at the remote server URL and include your API key in the Authorization header.

How to install

No installation is required. This server runs remotely and is accessed via your MCP client. To begin, complete these steps:— Generate an API key in your Arcate workspace. — Configure your MCP client with the provided HTTP URL and the Authorization header. — Restart your AI client and test a sample query.

# Example configuration is shown for reference in your MCP client
# Step 1: Generate API Key from Arcate workspace Settings > Integrations
# Step 2: Configure MCP client with the remote HTTP endpoint and header

Additional guidance

The Arcate MCP Connect server is a remote HTTP service that requires an active Evidence subscription. Access keys are generated within your Arcate workspace and used to authorize requests to the MCP server.

Security and architecture

Security is handled through API keys that are validated per request. Keys are stored securely and never exposed in plaintext after initial display. Each request is validated against your workspace context, ensuring cross-tenant isolation and auditability for signals created or enriched via MCP.

Configuration snippets

Configure your Claude Desktop client to connect to Arcate MCP Connect using the following JSON snippet.

{
  "mcpServers": {
    "arcate": {
      "url": "https://eshuikffwhaxcvkzaewj.supabase.co/functions/v1/mcp-server",
      "headers": {
        "Authorization": "Bearer arc_YOUR_KEY_HERE"
      }
    }
  }
}

If you are using Cursor, add the server using the following URL and header.

https://eshuikffwhaxcvkzaewj.supabase.co/functions/v1/mcp-server
Header: Authorization: Bearer arc_YOUR_KEY_HERE

Tools and capabilities

Read capabilities allow you to search and retrieve signals, customers, and initiatives. Write capabilities enable you to ingest new customer feedback, add customer profiles, link signals to initiatives, and enrich initiatives with evidence.

Examples and prompts

Triage a sales call: Log a new signal and link it to a relevant initiative. Enrich an initiative with new evidence before a roadmap review.

Notes on data sources and signals

All MCP-created signals are tagged with ingestion_source: mcp to enable easy auditing in the UI.

Troubleshooting

If you run into authorization issues, verify that your API key is active and that your MCP client is sending the Authorization header with each request.

Available tools

search_signals

Search signals by keyword, type, or severity

search_customers

Look up customer accounts by name

search_initiatives

Find initiatives by keyword

create_signal

Ingest new customer feedback (tagged ingestion_source: mcp)

create_customer

Add a new customer profile (Owner only)

link_to_initiative

Connect signals to an initiative on the product roadmap

enrich_initiative

Update hypothesis, metrics, and outcomes for a roadmap initiative