Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Arcate MCP ConnectSearch for recent customer signals about the dashboard performance."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Arcate MCP Connect — Server
The official MCP server for Arcate. Gives AI agents like Claude direct access to your product discovery workspace — reading signals, browsing your roadmap, and writing new feedback back in.
This is a remote HTTP server — no installation required. Configure a URL in your MCP client and connect instantly.
Requires an active Evidence subscription (€129/mo). API keys are generated in
/settings/integrationsinside your Arcate workspace.
Quick Start
1. Generate an API Key
Log in → Settings → Integrations → Generate API Key. Copy the key — shown only once.
2. Configure your MCP client
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"arcate": {
"serverUrl": "https://eshuikffwhaxcvkzaewj.supabase.co/functions/v1/mcp-server",
"headers": {
"Authorization": "Bearer [YOUR API KEY]"
}
}
}
}
Cursor → Settings → MCP → Add Server → Type: HTTP → URL:
https://mcp.arcate.ioHeader: Authorization: Bearer arc_YOUR_KEY_HERE
3. Restart your AI client and test
"What are my top 5 unlinked customer signals from the last 30 days?"
Resources (Read-Only)
URI | Description |
| Unified Signal Inbox — all customer feedback |
| Product Roadmap — active initiatives with evidence |
Tools
Read
Tool | Description |
| Search signals by keyword, type, or severity |
| Look up customer accounts by name |
| Find initiatives by keyword |
Write
Tool | Description |
| Create a new roadmap initiative (optionally link signals atomically) |
| Ingest new customer feedback (tagged |
| Add a new customer profile (Owner only) |
| Connect signals to a roadmap initiative |
| Update hypothesis, metrics, and outcomes |
Guided Prompts
Prompt | Description |
| Welcome — get workspace overview and available commands |
| Log feedback from a call or interview |
| Find unlinked signals with no initiative assigned |
| Strengthen a roadmap initiative with evidence |
Example Prompts
Triage a sales call:
"I just spoke with Acme Corp. They said bulk export times out on datasets over 100k rows. Log this as a signal."
Review initiative evidence:
"Does our Mobile Revamp initiative have enough signal coverage to proceed to active?"
Batch ingest:
"Here are notes from 3 customer calls this week. Create signals for each and link them to relevant initiatives."
Security
Keys are stored as SHA-256 hashes. The plaintext is shown only once and never stored.
Every request is re-validated against
billing_statusanduse_mcpcapability.All queries are hard-scoped to your
organization_id. Cross-tenant access is impossible.MCP-created signals are tagged with
ingestion_source: mcpfor audit filtering in the UI.
Architecture
The server is deployed as a Supabase Edge Function implementing JSON-RPC 2.0 over HTTP (the MCP Streamable HTTP transport). A GET request to the server URL returns a human-readable info card — no MCP client needed to inspect it.
Source: src/ — TypeScript reference implementation
Deployment: Supabase Edge Functions (Deno)
Database Setup
Apply the migration in supabase/migrations/add_mcp_tables.sql to bootstrap the api_keys table.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.