Skip to content
Docs
Docs / AI & Connectors / Sign in

Developer tools

MD View as MarkdownPlain text version of this page
Open in ClaudeAsk questions about this page Open in ChatGPTAsk questions about this page

Connect Claude Code, Cursor, Codex and other coding tools to FranchiseSEE by signing in.

On this page

Coding tools connect to the same reporting server as Claude and ChatGPT, using the same sign-in. The connection is read-only.

Text 
https://app.franchisesee.com/mcp/reporting

If your browser is already signed in to FranchiseSEE as someone else, sign out first. Otherwise the connection lands on the other account, and FranchiseSEE refuses it.

Claude Code

  1. In a terminal, run:

    Shell 
    claude mcp add --transport http franchisesee https://app.franchisesee.com/mcp/reporting

  2. Start Claude Code, type /mcp, choose franchisesee, then Authenticate.

  3. Your browser opens FranchiseSEE's sign-in. Sign in with your usual FranchiseSEE login.

Add --scope user to the first command to make the server available in every project rather than just the current one.

Cursor

Add the server to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):

JSON 
{
  "mcpServers": {
    "franchisesee": {
      "url": "https://app.franchisesee.com/mcp/reporting"
    }
  }
}

Open Cursor's MCP settings, where FranchiseSEE shows as needing sign-in. Choose to connect, and sign in with your usual FranchiseSEE login in the browser window that opens.

Codex

Add the server, then sign in:

Shell 
codex mcp add franchisesee --url https://app.franchisesee.com/mcp/reporting
codex mcp login franchisesee

Your browser opens FranchiseSEE's sign-in. Sign in with your usual FranchiseSEE login.

Other tools

Most tools that support remote MCP servers over Streamable HTTP with OAuth connect the same way: give them the reporting URL and complete the sign-in they start. Your tool's own MCP documentation says where the URL goes.

When to use a token instead

A signed-in coding tool reads reports only. Use an API token to manage locations and users through the admin server, for a tool that can't sign in (such as GitHub Copilot), or for a script that runs on its own. Setup for each is in Token clients.

Something wrong?

See Troubleshooting: signing in.