The Navattic MCP server gives AI coding agents — such as Claude Desktop, Cursor, VS Code Copilot, and Windsurf — structured access to your workspace. Agents can read analytics, browse and build demos, and query personalization data, all scoped to your workspace through a Personal Access Token.Documentation Index
Fetch the complete documentation index at: https://docs.navattic.com/llms.txt
Use this file to discover all available pages before exploring further.
The MCP server is available on the Base plan and above.
How it works
You create a Personal Access Token in your workspace settings and provide it to your AI agent’s MCP configuration. The agent connects tohttps://app.navattic.com/api/mcp and discovers only the tools it has permission to use based on the token’s scopes and your workspace role.
All operations are scoped to your workspace — agents cannot access data from other workspaces, even with a valid resource ID from another workspace.
Step 1: Create a Personal Access Token
Go to Access Tokens settings
Navigate to Settings > Workspace > Access Tokens in your Navattic workspace.
Create a new token
Click Create token. Enter a name for the token (for example, “Claude Desktop” or “Cursor agent”).
Select scopes
Choose the scopes your agent needs. Each scope grants access to a specific set of tools:
| Scope | What it allows | Required role |
|---|---|---|
| Analytics | View demo performance, visitor data, and account engagement | Viewer or above |
| Demo Browsing | Browse projects, flows, and share links | Viewer or above |
| Demo Building | Create flows, edit steps, configure CTAs | Builder or above |
| Demo Management | Rename and organize projects; create share links | Builder or above |
| Demo Publishing | Deploy and archive projects | Builder or above |
| Personalization | View custom properties and visitor activity | Viewer or above |
Set an expiration
Choose a token lifetime: 7, 30, 60, 90, or 180 days. Tokens expire automatically; you’ll need to create a new token when one expires.
Step 2: Configure your MCP client
After copying your token, connect your AI agent using the Navattic MCP server URL:- Claude Desktop
- Cursor
- VS Code
- Windsurf
- Claude Code
Add to Restart Claude Desktop after saving.
~/Library/Application Support/Claude/claude_desktop_config.json (macOS):YOUR_TOKEN with the token you copied in Step 1.
Available tools
Once connected, your agent can see and call tools based on its token’s scopes. Tools are only visible to the agent if the token has the corresponding scope — the agent won’t see tools it can’t use.| Tool | Description | Scope |
|---|---|---|
list_demo_analytics | View engagement metrics for all active demos — views, visitors, engaged sessions, duration, CTA clicks, and click-through rate | Analytics |
list_visitors | List visitors who have interacted with demos, with filtering by demo, company, location, device, and custom properties | Analytics |
list_accounts | List company accounts with engagement metrics, with firmographic filtering by industry, employee count, revenue, and more | Analytics |
get_visitor | Get a detailed profile for a specific visitor, including their 25 most recent sessions, conversion events, and demos viewed | Analytics |
get_account | Get a detailed profile for a specific company account, including visitors, demos viewed, and total engagement duration | Analytics |
list_projects | List all projects in the workspace | Demo Browsing |
get_project | Get details, flows, and share links for a specific project | Demo Browsing |
create_flow | Create a new flow within a project | Demo Building |
rename_project | Rename a project | Demo Management |
archive_project | Archive a project (affects live demo URLs) | Demo Publishing |
list_custom_properties | View custom properties configured for personalization | Personalization |
- Workspace overview — current project count, member count, and plan type
- Navattic concepts — a reference guide to the Navattic data model (projects, flows, steps, share links)
Use cases
Analyze demo performance in your coding environment
Analyze demo performance in your coding environment
Ask your AI agent questions about demo engagement and visitor behavior. For example: “Which of our demos got the most engagement last quarter?”, “Who from Acme Corp has viewed our demos recently?”, or “What companies are showing the most interest this month?” The agent uses the analytics tools to query your workspace data and present results directly in your editor.
Build demos programmatically
Build demos programmatically
Use your agent to create new flows within an existing project. Describe the steps you want in natural language and let the agent structure and create them via
create_flow. This is useful when building many similar demos or automating demo creation as part of a deployment workflow.Browse your demo library
Browse your demo library
Ask the agent to list all projects and find specific demos by name or description. The
list_projects and get_project tools give the agent access to your full workspace library, including flow structure and share links.Automate demo maintenance
Automate demo maintenance
Use the agent to rename or archive projects as part of a release workflow. For example, archive old version demos automatically when a new version is deployed.
Managing tokens
You can view all active tokens from Settings > Workspace > Access Tokens. From there you can:- See each token’s name, scopes, creation date, and expiration
- Revoke a token at any time — revocation takes effect immediately
Frequently asked questions
Can I create multiple tokens for different agents?
Can I create multiple tokens for different agents?
Yes. Create a separate token for each agent or environment, and name them to make revocation easier. For example, “Claude Desktop - production” and “Cursor - local dev”.
What happens if my token is compromised?
What happens if my token is compromised?
Revoke the token immediately from Settings > Workspace > Access Tokens. Then create a new token and update your agent configuration. The revoked token stops working as soon as you revoke it.
Can a Viewer-role user create a token with write scopes?
Can a Viewer-role user create a token with write scopes?
No. The scope picker automatically disables write scopes (Demo Building, Demo Management, Demo Publishing) for users with Viewer-only roles.
Does the agent see all my workspace data?
Does the agent see all my workspace data?
The agent can only access data within the scopes you selected when creating the token. All data is also restricted to your workspace — the agent cannot access data from other workspaces.