Console
The AI Bridge Console Is an Interface — Not the Agent
One of the most common questions we hear: “Does AI Bridge include a chatbot?” The answer is deliberately no. The AI Bridge Console is a self-hosted dashboard for managing connected WordPress sites and routing authenticated MCP tool calls. Conversation, reasoning, and model selection stay in Cursor, Claude Desktop, or VS Code — where they belong.
Console vs agent: who does what
| Task | AI client (Cursor, Claude…) | AI Bridge Console |
|---|---|---|
| Natural language reasoning | ✓ | — |
| Conversation history | ✓ | — |
| Store site credentials | — | ✓ |
| Test MCP connectivity | — | ✓ |
| Forward tool calls to WordPress | ✓ (direct) | ✓ (optional proxy) |
| Multi-site registry | — | ✓ |
What the Console actually does
- Site registry — encrypted Application Password storage per install
- Connection testing — verify REST and MCP endpoints before a session
- Session routing — forward agent tool calls without exposing raw credentials in chat logs
- Bootstrap workflows — pair with wp-elementor-bootstrap skills for repeatable site builds
A typical agency workflow
- Import five client sites into the Console with Application Passwords
- Verify MCP connectivity for each (green check = ready)
- Open Cursor, connect to a client site, prompt: “Audit plugins and update Elementor safely”
- Agent calls tools on the real install; you review diffs in git before deploy
The Console never sees your prompts unless you choose to run sessions through it. Direct MCP from Cursor to WordPress works without the Console entirely.
When you do not need the Console
Freelancers with one site, developers who store credentials in their MCP config, or teams already using CI/CD for deploys may skip the Console. AI Bridge on the WordPress side is complete without it.
Think of the Console as wp-admin for your agent fleet — a control panel, not the brain.
Privacy and data flow
The Console runs on your machine (or your team’s infrastructure). Site credentials are encrypted at rest. Prompts and model responses flow through your AI client’s normal channels — the Console only handles authenticated HTTP to WordPress when you use it as a session interface.