IM-Press
Menu
IM-Press / Documentation

Connect an AI agent

Understand REST discovery, dedicated credentials and the optional WordPress MCP Adapter setup.

Connect a compatible agent

The Connect AI Agent screen provides setup guidance for Claude Desktop, Claude Code, Codex, Cursor and custom clients. Choose the REST/OpenAPI or optional MCP path supported by your client and WordPress installation. Setup examples do not certify every operation or configuration, and providers do not endorse IM-Press.

Start with what the site actually supports

IM-Press exposes WordPress capabilities through REST APIs and a machine-readable OpenAPI specification. The enabled modules, installed version, permissions and license determine what is available.

On your own installation, begin with these discovery paths:

/wp-json/
/wp-json/imp-openapi/v1/spec

Discovery is not permission to change anything. Your client must authenticate and satisfy each operation's authorization requirements.

Use a dedicated connection

  1. Choose a compatible agent/client and decide the exact site and work it may perform.
  2. Use an appropriate WordPress account with a dedicated Application Password. Keep access limited to what the work requires.
  3. Store the credential in your client's secure credential facility—not in a public prompt, page, browser URL or repository.
  4. Verify read-only discovery first, then test one small draft change with review and rollback available.
  5. Revoke the Application Password when the connection is no longer needed.

MCP is optional—and the adapter is separate

The optional agent layer depends on compatible WordPress Abilities functionality, an enabled IM-Press agent layer, a separately installed WordPress MCP Adapter, and a compatible client. The IM-Press 5.2.7 package does not bundle or automatically install that third-party adapter.

Follow the adapter's own setup guidance and the actual capabilities exposed by the installation. Do not assume every MCP client or WordPress version supports the same workflow.

Keep the operator in charge

  • Review the exact proposed change and target before a write.
  • Make a separate backup before replacing existing content.
  • Use supported mutation services instead of improvising database edits.
  • Verify the public page and relevant interactions afterward.
  • Keep hosting administration separate. WordPress credentials are not authority to change DNS, server files or account-wide settings.
No agent required for ordinary WordPress use.

You can install the plugin and use its supported editing workflows without configuring MCP or subscribing to an AI provider through this site.