77Fox77Fox is a Windows desktop app that runs a local MCP (Model Context Protocol) server for your own data: with it, Claude Code, Claude Desktop, Codex CLI, Cursor, Gemini CLI, VS Code, Cline, OpenCode and Windsurf can search and create prompts, record tasks and organise your schedule, each client limited to the access level and data scope you grant. The server listens only on the local machine, runs inside the desktop app, and can be paused or revoked per client from Settings.
This guide covers what an AI client can do through the connection, what it cannot, how permissions are layered, and how to set it up in three steps.
What MCP changes
Without MCP, your prompts and records live in 77Fox and your AI tools live somewhere else, and you shuttle text between them. With MCP, the AI client you already work in can ask 77Fox for the prompt you saved last week, add a task from the action items in a meeting transcript, or return a monthly income and expense summary, without you switching windows.
Permission matrix
| Data or action | Read-only | Write without deletion | Full trust | Extra permission needed |
|---|---|---|---|---|
| Search and read prompts, categories and versions | Yes | Yes | Yes | No |
| Create prompts, update categories and versions | No | Yes | Yes | No |
| Import reference images and videos while writing a prompt | No | Yes | Yes | No |
| Delete prompts or records | No | No | Yes | Grant deletion only when needed |
| Read or update tasks, timeline events, reminders, clocks | Read | Yes | Yes | No |
| Financial records and monthly summaries | Read | Yes | Yes | Financial details need separate permission |
| Server list | Read | Yes | Yes | Server addresses need separate permission |
| Canvases | Read | Yes | Yes | Canvas content needs separate permission |
| API Key vault | No | No | No | Separate permission required |
| Check hardware status, open a 77Fox page | Yes | Yes | Yes | No |
Two details matter here. Read results for prompts include the prompt text and media counts, not the media files themselves. And once you grant write access, permitted writes run directly without a confirmation dialog, so use read-only access for queries and keep deletion off unless a workflow really needs it.
What the server never does
- It never listens beyond your machine. The MCP server runs locally and listens only on the local machine. The web console does not host it.
- It never runs without the desktop app. 77Fox can run in the background, and connections stop when you quit the app.
- It never logs your content. Activity logs record which operations ran, without storing prompt text or other data content.
- It never hands over the API Key vault without a separate grant, and financial details, server addresses and canvas content each require their own permission.
- It never keeps a client connected against your will. You can pause all connections or revoke a single client from Settings, and writes that still have a saved snapshot can be undone there.
One limit sits outside 77Fox's control: your AI client may send retrieved content to its model provider. Grant only the access a workflow needs.
Setup in three steps
- Enable the server. In 77Fox, open Settings, then MCP server, and enable it.
- Add a client. Select your AI tool, its access level and the data it may use.
- Finish setup. Use the registration option for the client, or copy its connection configuration, then enable 77Fox in the client. Credentials are shown once; store them securely.
Connection configurations are provided for Claude Code, Claude Desktop, Codex CLI, Cursor, Gemini CLI, VS Code, Cline, OpenCode and Windsurf.
Three workflows that justify the setup
Prompt retrieval from the editor. In Cursor or VS Code, ask for "the system prompt I use for changelog drafts" and get the saved version back, with categories and version names intact, instead of scrolling through chat history.
Action items into tasks. Paste meeting notes into Claude Desktop and ask it to turn the action items into 77Fox tasks with deadlines. With write access, they land in the same task list you see on the dashboard and, if configured, on the timeline.
Money questions without a spreadsheet. With financial read permission, ask Codex CLI for last month's income and expense summary from the finance module, which stores its data in a local database.
Reviewing what happened
Settings keeps a record of tool calls and results. From there you can undo writes that still have a saved snapshot, pause everything at once, or revoke one client. Because the log stores operations rather than content, reviewing it does not itself expose the prompts or records that were touched.
FAQ
Does 77Fox need to stay open?
Yes. The Windows app hosts the MCP server and can run in the background. Opening the web console alone does not provide the connection.
Does the AI automatically get all my data?
No. Each client is limited by its access level and data scope, and access can be paused or revoked. Financial details, server addresses, canvas content and the API Key vault require separate permission.
Do I confirm every write?
No. Once write access is granted, allowed operations execute directly. Use read-only access for queries; writes with a retained snapshot can be undone in Settings.
Which clients are supported?
Claude Code, Claude Desktop, Codex CLI, Cursor, Gemini CLI, VS Code, Cline, OpenCode and Windsurf have ready-made connection configurations.
Is the MCP server a paid feature?
MCP is listed among the desktop app's capabilities and does not depend on a cloud AI plan; cloud AI credits apply only to 77Fox cloud AI features.