Hi all,
I’m working on a side project called IFMPC (InfinityFree MCP) and I want to run it past the community — and ideally get a staff read on the ToS implications — before releasing it.
What it is
A Chrome extension that exposes parts of your own InfinityFree account to an AI assistant (Claude Desktop, Cursor, or anything that speaks the Model Context Protocol). The extension acts entirely inside your already-logged-in browser session — there are no stored credentials, no scraping from a server, and no third-party proxy.
In practice, that means you could ask an AI:
- “Show me which files in
htdocswere modified this week.” - “My site is throwing a 500 — pull the latest error log and explain it.”
- “Create a
stagingsubdomain pointing at/htdocs/staging.” - “Dump the schema of my
wp_userstable.”
…and it would carry the request out through the same VistaPanel / client area pages you’d use by hand.
How it works (high level)
- The extension runs as a content script on
*.infinityfree.com/*.epizy.com/cpanel.infinityfree.compages. - A local MCP server (Node-based native messaging host) bridges Claude Desktop ↔ the extension over a Chrome
nativeMessagingchannel. - Each MCP “tool” maps to a small, well-defined DOM interaction on the corresponding panel page.
- Write actions (file edits, DB writes, DNS changes) require an in-extension confirmation popup before they fire.
Nothing leaves your machine. The AI only sees what you explicitly let a tool return.
Why I’m posting before publishing
I want to make sure this is welcome here. A few specific questions for staff / experienced users:
- ToS: Section on “automated tools” is broad. Does a user-initiated, locally-running extension that drives the user’s own panel session count as prohibited automation, or is this in the same bucket as a browser autofill / accessibility tool?
- Rate limits: Are there documented or unwritten rate limits on VistaPanel actions I should respect (e.g., max file ops per minute)? I’d like to bake the limits into the extension rather than have it trip them.
- Preferred entry points: Is there any chance of an official read-only API in the future, even something minimal like account stats? If so I’d rather wait and build against that than scrape the panel HTML.
Where it lives
- Project page & demo: https://ifmpc.nathanrojas.com
- I’ll publish source on GitHub once the scope is locked.
Happy to answer questions, hear “please don’t” if that’s the verdict, or pivot the design based on what staff prefers. Thanks for taking a look.
— SinceTwentyFive