FRAMNOVA FIELD GUIDE · UPDATED JULY 2026

Connect the frame.
Keep the context.

01

BEFORE YOU START

Keep two values safe.

Framnova Pro gives you a Direct MCP URL and a Pro token after checkout. The URL identifies the service; the token authorizes access to your synced capture sets. Save the token in a password manager as soon as it is shown.

WHAT YOUR DESKTOP CLIENT NEEDS

https://mcp.framnova.com/mcpPlus your fr_pro_… token. The token is displayed once on the purchase activation page.
Token hygiene
  • Treat the token like a password.
  • Never paste it into a chat, issue, public screenshot, or source repository.
  • If it is lost or exposed, contact Framnova support with your payment receipt so the old token can be revoked.
02

FRAMNOVA EXTENSION

Sync only the capture set you choose.

Direct MCP is deliberately not an ambient browser feed. Connect the extension first, then explicitly sync the capture set you want your AI client to use.

  1. Open Framnova SettingsIn the extension, go to Settings → Direct MCP.
  2. Use the endpoint originEnter https://mcp.framnova.com in the extension. Do not add /mcp in this field.
  3. Paste your Pro tokenPaste the saved fr_pro_… value, then select Save connection.
  4. Sync a selected capture setAfter capturing, choose Sync to Direct MCP. Only then can your AI client retrieve it.

The extension verifies access before syncing. A successful connection means its endpoint and token agree.

03

DESKTOP AI CLIENTS

Use the route your client speaks.

All ready clients use the same URL: https://mcp.framnova.com/mcp. The difference is only where each client keeps the authorization header.

04

CODEX

Set it once in PowerShell.

Save your token in a local environment variable, register the remote server, and restart Codex.

PowerShell
$env:FRAMNOVA_MCP_TOKEN = "PASTE_YOUR_PRO_TOKEN"
codex mcp add framnova --url https://mcp.framnova.com/mcp --bearer-token-env-var FRAMNOVA_MCP_TOKEN
codex mcp get framnova

Codex references the local environment variable instead of storing the token in the MCP server definition.

TRY THIS IN CODEX

“Use Framnova to list my recent capture sets, then inspect the selected page context and summarize the layout issue.”

05

CLAUDE CODE

Attach the local authorization header.

Claude Code can use the same remote HTTP endpoint. Run this in PowerShell with your own token value.

PowerShell
$env:FRAMNOVA_MCP_TOKEN = "PASTE_YOUR_PRO_TOKEN"
claude mcp add --transport http framnova https://mcp.framnova.com/mcp --header "Authorization: Bearer $env:FRAMNOVA_MCP_TOKEN"
TRY THIS IN CLAUDE CODE

“Use the latest Framnova set as evidence. Compare the mobile and desktop states, then propose the smallest implementation change.”

06

VISUAL STUDIO CODE

Prompt for the token; do not commit it.

Create or edit .vscode/mcp.json in a private workspace configuration. This version asks for the token as a password input.

.vscode/mcp.json
{
  "servers": {
    "framnova": {
      "type": "http",
      "url": "https://mcp.framnova.com/mcp",
      "headers": { "Authorization": "Bearer ${input:framnova-token}" }
    }
  },
  "inputs": [{
    "id": "framnova-token",
    "type": "promptString",
    "description": "Framnova Pro token",
    "password": true
  }]
}
Do not commit the secret

If your workspace configuration is shared, make the MCP configuration local to your machine or exclude it from version control.

07

CURSOR

Use remote MCP in Cursor's configuration.

Add a remote HTTP MCP server in Cursor's MCP settings. Keep the token in its local secret or user-level configuration when your version supports it.

mcp.json
{
  "mcpServers": {
    "framnova": {
      "url": "https://mcp.framnova.com/mcp",
      "headers": { "Authorization": "Bearer PASTE_YOUR_PRO_TOKEN" }
    }
  }
}

If your Cursor version uses a different configuration surface, keep the same URL and Authorization: Bearer … header. Do not save a real token in a committed project file.

08

SUPPORT MATRIX

Clear support status beats false confidence.

ClientDirect MCP todayNotes
CodexReady

Remote HTTP with a bearer-token environment variable.

Claude CodeReady

Remote HTTP with a local authorization header.

VS CodeReady

Remote HTTP configuration with a private prompt input.

CursorReady

Remote MCP configuration with a local authorization header.

Claude Desktop / Claude.aiOAuth next

Not direct today: Framnova must add OAuth for Claude's remote connector model.

“Ready” means the current bearer-token endpoint matches the client connection model. OAuth is a distinct implementation, not a CSS or documentation change.

TROUBLESHOOTING

When a connection does not appear.

I entered the URL but my client cannot connect.

Desktop clients must use https://mcp.framnova.com/mcp. The extension uses the shorter origin without /mcp. Check that the header is exactly Authorization: Bearer YOUR_TOKEN.

The extension says the token is invalid.

Check that you copied the complete token and that your extension endpoint is https://mcp.framnova.com. Do not add spaces before or after either value.

My client connects but no capture sets are visible.

Capture first, then explicitly choose Sync to Direct MCP in the extension. The service does not upload or expose every browser capture by default.

Can I connect a web chat instead?

Web AI attachment remains a separate free extension workflow. Direct MCP is for compatible desktop AI clients that can call MCP tools and retrieve visual context.