Central MCP Documentation / Getting started Remote MCP · imhdev

Getting started with Central MCP

Connect an AI agent to InMotion Central over HTTP. You use the same account as the Central app; the agent lists projects, sites, and teams, and can create a playground — without leaving the chat.

Introduction

This is the public getting-started page for this Central MCP server. It covers what the server is, how to point Cursor (or any MCP client) at it, how sign-in works, what you can ask the agent to do, and what this development instance will not do.

What you’ll need

A Central account on this environment, a browser where you can sign into the Central app, and an MCP client such as Cursor.

What Central MCP is

Central MCP is an MCP server in front of InMotion Central. Agents talk to it with the Model Context Protocol; it talks to Central with your signed-in account — the same one you use in the Central SPA.

This is an HTTP remote MCP endpoint. You do not run npx, you do not install a local process, and you do not paste a Central API token into a config file. Add the URL, connect, and complete OAuth in the browser.

Server URL:

https://mcp.surajb.central.imhdev.com/mcp

Use with agents

Cursor

Add the server to user-level ~/.cursor/mcp.json or to the project file .cursor/mcp.json:

{
  "mcpServers": {
    "central": {
      "url": "https://mcp.surajb.central.imhdev.com/mcp"
    }
  }
}

Then enable the central server in Cursor Settings → MCP.

Connect

  1. Sign into Central in the browser first at surajb.central.imhdev.com. Stay signed in. (See Authentication for why this step is separate.)

  2. In Cursor, connect the Central MCP server. A browser window opens for OAuth.

  3. Approve access. When the client says connected, you can ask it to list your projects or who you are signed in as.

If connect hangs or the authorize page looks stale, log out of MCP in the client and reconnect. A leftover session is a common cause of a confusing login loop.

Other MCP-capable agents (Claude, VS Code Copilot, and similar) use the same URL. Put it wherever that client stores remote MCP servers.

Authentication

Do this in order

Log into Central in the browser first (the SPA / SSO). Then start MCP connect. If you open the MCP authorize page while you are not already signed into Central, you can end up in a redirect loop instead of a login screen.

It is reasonable to ask why MCP does not just open Central for you. The authorize page hits the API / OIDC host. The session cookie from the Central SPA is not always in that cookie jar until you have signed into Central. Sign in there first, then connect. It works; we may smooth this later.

After a successful connect, the client holds a token for this MCP, not a raw Central API token. Actions still run as your Central user, with the same access you have in the app.

What it can do

Ask in ordinary language. The agent picks the matching Central actions. Capabilities a CS or agent user actually cares about:

Account and projects

Who you are signed in as, list and open projects, create an empty project folder, rename a project.

Sites, playgrounds, and environments

List WordPress / UltraStack sites, inspect a site or environment, add a WordPress playground under a project (development playground — not paid hosting).

Teams and domains

List teams, inspect a team, invite a member, list domains on the account.

SSH as Central stores it

Ask for the SSH user Central has for a site. On this instance that is often username only — see limitations.

Snapshots

List saved WordPress Cloud Snaps (installable site copies) on the account.

Cloud usage and Horizon

Plan & Usage / quotas when Flex Spend exists on the project. Horizon login URL for Cloud projects (VMs live in Horizon, not here).

Support tickets

List, read, open, and comment on tickets when Zendesk is up for this environment.

Writes that are available: create a project, create a WordPress playground, update a project, invite a team member, and (when Zendesk is up) open or comment on a ticket. Review those with the user before confirming.

Limitations of this dev instance

This host is imhdev / Suraj’s development environment, not production Central MCP. Use it to try the agent flow. Do not treat it as a substitute for production.

  • Playground public URL / BoldGrid TLS often does not load. Central objects still create (project, site, environment). Don’t wait on the site in a browser to decide if the tool worked.
  • get_site_ssh on playgrounds typically returns a username only — no host or key. The SPA hardcodes the trial host on non-prod.
  • Paid UltraStack / real hosted WordPress does not provision here. Create a playground, not a checkout.
  • Support tickets may 503 when Zendesk is down on this stack.
  • Cloud Plan & Usage / Flex Spend may be empty even when OpenStack VMs exist for the project.
  • The service can 503 if the node or volume flaps (single replica plus disk).