To connect an AI agent to Elevated Instagram Feed, go to Elevated › Instagram Feed › AI Agent, click Install & Activate Agent Connector, then click Open Agent Connector and follow the connection wizard: pick your agent, generate an application password, and paste the setup command into your agent. Once connected, your agent can create and manage feeds, look after your connected accounts, and keep the media cache fresh. Logging in to Instagram itself stays a human action: the agent can prepare the login link, but only you can authorize an account. Every operation is validated and permission-checked.
Navigate to Elevated › Instagram Feed in your WordPress admin.
Click AI Agent in the plugin’s top navigation, next to Settings.
Agent Connector for WP is the free plugin that exposes Elevated Instagram Feed’s abilities to your agent over MCP. The AI Agent page installs it for you.
Click Install & Activate Agent Connector.
Elevated Instagram Feed downloads a pinned Agent Connector release and verifies its checksum before installing anything. When it finishes, the page shows Agent Connector is active and ready to create a secure connection.
Leave Allow AI agent access switched on. This is the master switch for agent access to Instagram Feed. Turn it off at any time to cut agents off without disconnecting anything else.
Click Open Agent Connector. The Agent Connector screen opens.
Click Get started.
Select the agent you use. Agent Connector shows exact setup instructions for each one; pick Other for universal instructions that work with any MCP-capable agent.
Click Continue.
Your agent authenticates with a WordPress application password, a credential scoped to your account that you can revoke at any time. The agent connects through a local proxy, so the computer running your agent needs Node.js.
Click Generate App Password. If you already created one, click I already have one instead.
The password is shown once. Copy it, or save it to your password manager.
Follow the setup instructions shown for your agent: copy the command, open your terminal, and paste it. Your agent confirms the MCP server was added.
On Mac, the terminal app is called Terminal. On Windows, search for how to open your terminal. The steps are the same after that.
Open your agent and ask:
Are you connected to my WordPress site over MCP? List the Elevated Instagram Feed tools you can use.
The agent should confirm the connection and list the Instagram Feed tools: feed management, account management, cache control, and maintenance.
Then try a real request:
List my Instagram feeds with their shortcodes.
The agent reads your saved feeds and reports each one with the shortcode you can paste into a page.
Elevated Instagram Feed registers its operations as WordPress abilities: the same validated, permission-checked operations the admin interface uses. Agent Connector serves those abilities to your agent over MCP, an open protocol supported by Claude, Codex, Cursor, and most other agents.
The guardrails, in plain terms:
The AI Agent page says WordPress abilities are unavailable. Your WordPress version doesn’t include the Abilities API yet. Update WordPress, then reload the page.
The AI Agent page says Agent Connector is inactive. The connector is installed but switched off. Click Activate Agent Connector.
The setup command fails in the terminal. The connection runs through a local proxy that requires Node.js. Install Node.js from nodejs.org, then run the command again.
The agent connects but has no Instagram Feed tools. Check that Allow AI agent access is switched on on the AI Agent page, then ask the agent to reconnect or refresh its tool list.
You want to cut off access. Switch off Allow AI agent access to block Instagram Feed abilities, or revoke the application password under Users › Profile › Application Passwords to sever the connection entirely.
This is the machine-readable version of this article. Feed it to your agent, or point the agent at the raw Markdown.
Elevated Instagram Feed registers 27 WordPress Abilities under the elevated-instagram-feed/* namespace. Agent Connector for WP serves them over MCP (Streamable HTTP) at:
{site_url}/wp-json/mcp/mcp-adapter-default-serverAuthentication: WordPress application password (Basic auth), typically via the @automattic/mcp-wordpress-remote stdio proxy with env vars WP_API_URL, WP_API_USERNAME, WP_API_PASSWORD.
tools/list on the MCP endpoint returns the exposed tools.mcp-adapter-discover-abilities lists every registered ability; mcp-adapter-get-ability-info returns an ability's full input/output JSON Schema; mcp-adapter-execute-ability executes one.list-feeds, get-feed, create-feed, update-feed, delete-feed (requires confirm: true)list-accounts-local (read-only), list-accounts, get-account, list-account-media, set-active-account, disconnect-account (requires confirm: true), prepare-account-connection, get-account-connection-status, cancel-account-connectionget-cache-info, get-cache-refresh-progress, refresh-feed-cache, refresh-all-feed-caches, clear-feed-cache, clear-cache (all four refresh/clear operations require confirm: true)cleanup-orphaned-media (requires confirm: true, supports dry_run), get-feed-update-schedule, set-feed-update-schedule, get-global-settings, update-global-settings, reregister-feed-translations, get-plugin-update-statusThe exact schema of every ability and captured request/response examples: https://elevatedextensions.com/documentation/instagram-feed/managing-with-ai-agent/?format=agent
confirm: true: delete-feed, disconnect-account, refresh-feed-cache, refresh-all-feed-caches, clear-feed-cache, clear-cache, cleanup-orphaned-media. The flag is schema-required, so an unconfirmed call fails validation before any handler runs: Ability "elevated-instagram-feed/delete-feed" has invalid input. Reason: confirm is a required property of input. Refreshes require confirmation because they spend the site's Instagram API quota, not because they destroy anything.feed_id is a string, not an integer. Sending { "feed_id": 39 } fails with input[feed_id] is not of type string; send { "feed_id": "39" }.list-accounts and get-account are writes, not reads: each makes an Instagram Graph call and rewrites the stored accounts option with refreshed profile-picture URLs. list-accounts-local is the genuinely read-only alternative; prefer it whenever you only need to know who is connected. list-account-media validates the account token first, which can trigger a token refresh.prepare-account-connection produces the login URL and stops; cancel-account-connection withdraws it. No ability completes the OAuth flow.clear-cache is site-wide: it deletes every cache entry AND every downloaded image, video, and profile picture on disk, then marks all posts for re-download (which consumes Instagram bandwidth and quota). Prefer the scoped clear-feed-cache.Allow AI agent access off (option elevated_instagram_feed_agent_access), the abilities are not registered and calls fail with a 404, code rest_ability_not_found, message Ability not found. Ask the human to switch it on; agents cannot.// create-feed (input): only what you want to set; defaults fill the rest
{ "settings": { "title": "Spring Lookbook", "account_id": "@yourshop" } }The response returns the complete feed object with every default filled in (template, postStyles, layoutSettings, styleSettings, filterSettings) plus the new feed's id. Read it back with get-feed, and get the embed shortcode from list-feeds.
// delete-feed (input)
{ "feed_id": "39", "confirm": true }// delete-feed (response data)
{ "feed_id": "39", "deleted": true, "feed_post_rows_removed": 0, "cache_rows_removed": 0 }Deleted feeds leave downloaded media on disk: files are shared between feeds, and cleanup-orphaned-media will not reclaim them either, because it only deletes files no post row claims.
