Let your AI work on your sites — with a seatbelt.
Connect the AI you already use, give it a key that only opens what you allow, and keep the overview, the limits and the undo button.
Any AI, three ways of working
Use whatever AI you prefer — a small model on your own computer, the assistant you already pay for, or the most powerful model available. They all connect the same way, over MCP, with a key you create. Each key works in one of three modes, depending on the AI:
| Mode | How the AI works | Best for |
|---|---|---|
| Full tool list | It sees every tool it’s allowed to use and picks them itself. | Powerful models that should have full control. |
| Tool Assist | It describes the job; AICOMBase proposes the right tool, and the AI checks and runs it. | Saving tokens: the AI doesn’t read hundreds of tool descriptions. |
| MCPAssist | It just says what it wants in plain words; AICOMBase does the rest, step by step. | Small local models that get lost in long tool lists. |
Tool Assist and MCPAssist are part of every paid plan. A Free account gets both for its first 30 days.
Keys: only what you allow
You create a key in AICOMBase and paste it into your AI app. Each key is limited to:
- The sites you pick — or whole categories of sites.
- The permissions you pick, with the same names as in the AICOM plugin.
- Optional limits: only from certain IP addresses, only during working hours, preview-only (dry run), or an expiry date.
A key can never do more than your policy for the site allows, and you can revoke it at any time. Presets save a combination you use often.
Every job is a session
The AI opens a session with a name and a goal, works inside it and closes it once the result is checked. Without an open session the plugin refuses the work. You can read every session step by step — in AICOMBase and in WordPress (AICOM → Activity → Sessions) — and undo it.
MCP Guard: a second pair of eyes
MCP Guard checks risky actions before they run, against your rules and against what the AI said it was doing in the session:
- Clearly fine — the action runs.
- Unclear — the AI has to explain why it needs it, before anything happens.
- Can’t be undone and still unclear (deleting users, for example) — it waits for your approval, and you get an email.
- Clearly harmful — the key is frozen at once, and nothing more runs until a person looks at it.
You write rules in plain words — “Never deactivate the WooCommerce plugin” — and sensible rules are built in. MCP Guard is meant as a paid option; for now it’s included on every plan as a trial.
Connecting your AI app
ChatGPT, Claude on the web and the Claude app sign in instead of using a key: add a custom connector (in ChatGPT, a custom MCP server) with the address aicombase.com/api/mcp. It sends you to AICOMBase, where you sign in and choose the sites, the permissions and the mode — that becomes the app's key, shown on the Keys page, where you can change or disconnect it. Other AI apps use a key you make yourself:
Create a key
In AICOMBase, open Keys → Generate New Key: pick the sites, the permissions and the mode.
Add AICOMBase to your AI app
In any AI app or agent that supports MCP, add a remote MCP server with the AICOMBase address and your key (shown on the Keys page).
Ask for something
“Update the opening hours on the Contact page of example.com to 9–17.” The session appears live in AICOMBase.
See your sites in one place.
1 site free. No credit card. See the full pricing.