Open a site's Settings → MCP to copy your instance's MCP endpoint. Connect it in an OAuth-capable client. Evumi uses Better Auth for browser sign-in and consent; review the client, callback, read-only permissions, and selected sites before authorizing.
API keys and MCP access tokens are separate credentials. Do not paste a Stats key into the OAuth client-secret field. Revoke an AI client's access from the site's authorized-applications section when it is no longer needed.
The AI integration setting downloads a site-specific SKILL.md explaining tracker installation, event/property naming, framework integration, MCP querying, and geographic interpretation. Give that skill to your coding agent. The skill contains configuration examples, not account credentials, and downloading it does not grant access.
For repo use, see skills/evumi-integration/SKILL.md and its linked references. Read the site's actual supported tools through MCP discovery rather than constructing raw SQL.