Faurya MCP

Faurya MCP lets compatible AI assistants analyze your website data, inspect visitor journeys, understand revenue, help configure tracking, manage funnels and perform other approved Faurya actions.

Choose your LLM to connect

Connection options vary by AI platform, account type and workspace permissions. Faurya uses OAuth, so you should never need to paste an API key or access token into an AI conversation.

Prefer manual instructions? Read the installation guide.

The public remote MCP endpoint is:

https://mcp.faurya.com/mcp

Faurya MCP uses OAuth authentication over Streamable HTTP JSON-RPC. Do not paste API keys, OAuth tokens, or private provider credentials into prompts.

What you can do

With the permissions you approve, an AI assistant can help you:

• Compare traffic between periods.
• Investigate conversion drops.
• Analyze visitor and session journeys.
• Inspect goals and revenue.
• Compare attribution models.
• Search events, visitors, sessions, and payments.
• Analyze AI crawler activity.
• Generate tracking code and SDK setup guidance.
• Validate code or configuration supplied in the request.
• Create, update, or delete saved funnels.
• Manage approved site settings.
• Manage approved team access.
• Configure goal alert emails.

Endpoint and transport

Permission model

Users must enable MCP access globally in Faurya before approving clients. Connections are approved through Faurya OAuth. During approval, users can grant access to all eligible sites or only selected sites, then choose permissions per feature.

A feature can have no access, read access, or read and write access when writes are supported. Write access implies read access for that feature.

api-keys exists in the shared feature catalog for CLI/API-key flows but is not exposed as a public OAuth MCP feature in the current MCP tool registry.

Users can edit or revoke a connection later from Faurya settings. Disabling global MCP access blocks existing MCP connections until access is enabled again.

Site selection behavior

Most tools operate on one Faurya site. The optional siteId argument can be omitted when the connection has exactly one permitted site. If the connection has multiple permitted sites, site-specific tools require siteId and return SITE_SCOPE_REQUIRED when it is missing. The MCP server rejects inaccessible site IDs with INSUFFICIENT_SCOPE.

The connection-level tool faurya_list_sites returns only sites available to the current MCP connection.

Connection-level tool

faurya_list_sites

What it does: Returns the Faurya sites currently permitted for this MCP connection.

Permission required: Any approved MCP feature scope. This tool is connection-level rather than feature-level.

Input

Example prompt

List the Faurya sites available to this connection.

Example MCP input

{}

Example output

{
  "success": true,
  "requestId": "req_example",
  "data": {
    "sites": [
      {
        "id": "site_example",
        "domain": "example.com",
        "timezone": "UTC"
      }
    ]
  },
  "meta": {
    "warnings": [],
    "pagination": {
      "nextCursor": null,
      "hasMore": false
    }
  }
}

Standard success response

Tool calls are returned inside an MCP JSON-RPC result. The structuredContent and the JSON string in content[0].text contain the same Faurya response envelope:

{
  "success": true,
  "requestId": "req_example",
  "data": {},
  "meta": {
    "warnings": [],
    "pagination": {
      "nextCursor": null,
      "hasMore": false
    }
  }
}

requestId helps Faurya support debug requests. data contains the tool-specific result. warnings contains non-fatal issues. pagination is populated when a tool returns a nextCursor; not every tool has meaningful pagination.

Standard error response

MCP tool errors are JSON-RPC errors. Public error data includes a code, HTTP-like status, and optional details.

{
  "jsonrpc": "2.0",
  "id": "1",
  "error": {
    "code": -32000,
    "message": "This tool requires a permitted siteId when this MCP connection has multiple sites. Use faurya_list_sites first.",
    "data": {
      "code": "SITE_SCOPE_REQUIRED",
      "status": 400
    }
  }
}

Important public errors include AUTHENTICATION_REQUIRED, INVALID_TOKEN, MCP_DISABLED, NO_ALLOWED_SITES, SITE_SCOPE_REQUIRED, INSUFFICIENT_SCOPE, SITE_NOT_FOUND, owner_access_required, team_permission_required, ROLE_NOT_ALLOWED, VALIDATION_ERROR, INVALID_CURSOR, INVALID_LIMIT, INVALID_DATE_RANGE, INVALID_FILTER, INVALID_FIELD, NOT_FOUND, QUERY_TOO_COMPLEX, QUERY_TIMEOUT, and RATE_LIMITED.

Validation failures use JSON-RPC code -32602 with code: "VALIDATION_ERROR" or an equivalent invalid-arguments response.

Security and privacy

Faurya MCP is designed around explicit OAuth approval and server-side authorization:

• Tools are limited to OAuth-approved sites.
• Tools are limited to approved feature permissions.
• Site IDs are validated server-side.
• Secrets, API keys, provider credentials, webhook signing secrets, and OAuth tokens are not returned.
• Hidden events are filtered from analytics and event tools.
• Write tools validate and sanitize input.
• Destructive tools should be used only after clear user confirmation.
• Connections can be revoked from Faurya settings.

Explore the docs