Respira for WordPress

https://www.respira.press/docs
Admin
Respira for WordPress is a safe bridge connecting AI coding assistants like Cursor and Claude Code...
Tokens:98,093
Snippets:1,382
Trust Score:5.7
Update:2 months ago
Show doc for...
Tokens:
Raw
### Install and Setup MCP Server

Source: https://www.respira.press/docs/changelog

Commands to initialize the Respira WordPress MCP server via setup wizard or global installation.

```bash
npx @respira/wordpress-mcp-server --setup
```

```bash
npm install -g @respira/wordpress-mcp-server
```

--------------------------------

### GET /plugins

Source: https://www.respira.press/docs/api-reference

Lists all installed plugins with status and update availability.

```APIDOC
## GET /plugins

### Description
List all installed plugins with status and update availability.

### Method
GET

### Endpoint
/plugins
```

--------------------------------

### Install plugin

Source: https://www.respira.press/docs/api-reference

Installs a plugin from a ZIP URL or the WordPress.org repository.

```http
POST /plugins/install
```

--------------------------------

### Run the Respira MCP setup wizard

Source: https://www.respira.press/docs/mcp-server

Executes the setup wizard to validate the site connection and generate local configuration files.

```bash
npx @respira/wordpress-mcp-server --setup
```

--------------------------------

### Install the MCP Server via npm

Source: https://www.respira.press/docs

Install the server package globally or execute it directly using npx.

```bash
npm install -g @respira/wordpress-mcp-server
```

```bash
npx -y @respira/wordpress-mcp-server
```

--------------------------------

### Full Update Request and Response Example

Source: https://www.respira.press/docs/tools/builders/update-module

A complete example showing a request to update a Divi button and the resulting system response.

```json
{
  "builder": "divi",
  "pageId": 42,
  "moduleIdentifier": {
    "admin_label": "Hero CTA"
  },
  "updates": {
    "attributes": {
      "button_text": "Start Free Trial"
    }
  }
}
```

```json
{
  "success": true,
  "message": "Module 'Hero CTA' updated successfully",
  "module_found": true,
  "module_type": "et_pb_button",
  "module_path": "sections[0].rows[0].columns[0].modules[1]",
  "changes_applied": {
    "button_text": "Start Free Trial"
  },
  "duplicate_created": true,
  "duplicate_id": 156,
  "approval_url": "https://yoursite.com/wp-admin/admin.php?page=respira-approvals"
}
```

--------------------------------

### Full example response for page update

Source: https://www.respira.press/docs/tools/pages/update-page

A complete example of the JSON response when updating a page title.

```json
{
  "id": 156,
  "title": "Welcome to Acme Corp",
  "slug": "home-respira-draft",
  "status": "draft",
  "respira_message": "Respira says: ✅ Created duplicate of 'Home' for safe editing. Review and approve at Respira → Approve Edits.",
  "respira_instructions": "Go to WordPress Admin → Respira → Approve Edits to review and publish changes.",
  "duplicate_created": true,
  "duplicate_id": 156,
  "original_id": 2,
  "approval_url": "https://yoursite.com/wp-admin/admin.php?page=respira-approvals"
}
```

--------------------------------

### Install MCP Adapter via WP-CLI

Source: https://www.respira.press/docs/inhale-mcp-abilities/troubleshooting

Install and activate the required MCP Adapter plugin using the command line interface.

```bash
wp plugin install mcp-adapter --activate
```

--------------------------------

### Install MCP Server

Source: https://www.respira.press/docs/changelog

Standard command to install or run the latest version of the WordPress MCP server via npx.

```bash
npx @respira/wordpress-mcp-server
```

--------------------------------

### Install and Authenticate Respira CLI

Source: https://www.respira.press/docs/changelog

Global installation of the Respira CLI package followed by authentication and verification of site access.

```bash
npm install -g @respira/cli
respira auth login
respira sites list
```

--------------------------------

### POST /plugins/install

Source: https://www.respira.press/docs/api-reference

Installs a plugin from WordPress.org or a ZIP URL.

```APIDOC
## POST /plugins/install

### Description
Install a plugin from WordPress.org or ZIP URL.

### Method
POST

### Endpoint
/plugins/install
```

--------------------------------

### Affiliate Deep-Link Examples

Source: https://www.respira.press/docs/dashboard/partner

Examples showing how to append the referral parameter to various public pages on the Respira website.

```text
https://www.respira.press/pricing?ref=<your-slug>
https://www.respira.press/cli?ref=<your-slug>
https://www.respira.press/blog/april-2026-update?ref=<your-slug>
```

--------------------------------

### First session primer prompt

Source: https://www.respira.press/docs/prompts

Run this prompt at the start of a new conversation to initialize the agent with site context and safety protocols.

```text
Before we start, prime yourself for this site with Respira. Detect the active page builder and its version, read my site context, and list a few of my pages so you know the lay of the land. From here on, follow Respira's safe workflow: every page edit goes through the builder's native modules, never raw HTML; duplicate any live page before editing it; read the exact element before you change it. When you are ready, give me a one-line briefing of what you found.
```

--------------------------------

### AI Agent Prompt: Feed Setup

Source: https://www.respira.press/docs/woocommerce/agent-ready-commerce

Request the system to configure product feeds for Google and ChatGPT and provide registration URLs.

```text
Set up product feeds for Google and ChatGPT and give me the URLs to register.
```

--------------------------------

### GET /context/theme-docs

Source: https://www.respira.press/docs/api-reference

Returns theme documentation and available template files.

```APIDOC
## GET /context/theme-docs

### Description
Returns theme documentation and available template files.

### Method
GET

### Endpoint
/context/theme-docs
```

--------------------------------

### Install via Composer

Source: https://www.respira.press/docs/inhale-mcp-abilities/installation

Use these commands to add the plugin to a Composer-managed WordPress site and activate it via WP-CLI.

```bash
composer require respira/inhale-mcp-abilities
wp plugin activate inhale-mcp-abilities
```

--------------------------------

### GET /menus/{id}

Source: https://www.respira.press/docs/api-reference

Get menu with all items and hierarchy.

```APIDOC
## GET /menus/{id}

### Description
Get menu with all items and hierarchy.

### Method
GET

### Endpoint
/menus/{id}

### Parameters
#### Path Parameters
- **id** (string) - Required - The menu ID
```

--------------------------------

### GET /menus

Source: https://www.respira.press/docs/api-reference

List all navigation menus.

```APIDOC
## GET /menus

### Description
List all navigation menus.

### Method
GET

### Endpoint
/menus
```

--------------------------------

### Staging and Backup Planning Prompt

Source: https://www.respira.press/docs/toolkits/divi-5-migration-prompt-pack

Use this prompt to generate a comprehensive migration strategy, including staging setup, backup/rollback procedures, and a team runbook.

```text
You are a senior WordPress DevOps engineer and Divi specialist.

I am preparing to migrate a site from Divi 4 to Divi 5 using Divi’s Migrator. I need a concrete, low-drama staging and backup plan that a small team or agency can actually follow.

1) BACKUP SETUP
- Current backup plugin(s) in use:
- Hosting-level backups available (yes/no, details):
- Backup frequency and retention:
- Date of last successful restore test and how it was tested:

2) STAGING / ENVIRONMENTS
- Do we have an existing staging site? If yes, how is it kept in sync with production?
- Is there a local development copy? If yes, how up to date is it?
- Any differences between staging and production (domains, caching, CDN, object cache, PHP settings, etc.):

3) ACCESS & ROLES
- Who can:
  - Trigger backups:
  - Restore backups:
  - Create or refresh staging:
  - Run Divi’s Migrator:
  - Approve changes (client, PM, etc.):

4) CHANGE WINDOW
- Preferred migration window (day/time and timezone):
- Any blackout periods where changes are not allowed:
- Expected traffic levels during the migration window (low/medium/high):

Using this information, produce:

A. STAGING STRATEGY
- Recommend whether to:
  - Create a new staging site, or
  - Reuse and refresh an existing staging site, or
  - Work locally first, then stage.
- Explain why this strategy fits the inputs above.
- Give a numbered checklist for setting up/refreshing staging before the migration.

B. BACKUP & ROLLBACK PLAN
- Describe exactly which backups to take and when, in relation to the migration (database + files).
- Provide a clear, step-by-step rollback plan that:
  - Restores the site to its pre-migration state.
  - Includes sanity checks after restore (front-end, forms, key funnels).
- Call out any gaps or risks in the current backup setup.

C. MIGRATION RUNBOOK
Create a concise, reusable runbook with:
- Pre-migration checklist (what to verify the day before and hour before).
- During-migration steps (what to do in staging and production).
- Post-migration checklist (what to verify before calling the migration complete).

D. TEAM COMMUNICATION NOTES
Write a short note I can share with the team that covers:
- Where we will run Divi’s Migrator (staging vs production).
- How we will back up and how to roll back.
- Who is on point during the migration window.
- What to do and who to contact if unexpected issues appear.
```

--------------------------------

### Configure a styled heading

Source: https://www.respira.press/docs/builders/divi-5

Example of a heading module using simplified settings for typography, alignment, and background styling.

```json
{
  "type": "divi/heading",
  "settings": {
    "title": "Welcome to Our Site",
    "tag": "h1",
    "heading_color": "#ffffff",
    "heading_font": "Inter",
    "heading_font_size": "48px",
    "text_alignment": "center",
    "background_color": "#1a1a2e",
    "padding": "60px 40px 60px 40px"
  }
}
```

--------------------------------

### GET /options/{option}

Source: https://www.respira.press/docs/api-reference

Get option value by name.

```APIDOC
## GET /options/{option}

### Description
Get option value by name.

### Method
GET

### Endpoint
/options/{option}

### Parameters
#### Path Parameters
- **option** (string) - Required - The name of the option.
```

--------------------------------

### Prompting for Bricks elements

Source: https://www.respira.press/docs/builders/bricks

Example prompt for generating a pricing section using native Bricks elements and existing design system styles.

```text
Build a pricing section on [page] using native Bricks elements. First read my Bricks global classes and color palette and reuse them instead of inline styles. Duplicate the page first and show me a preview.
```

--------------------------------

### Analyze WordPress page performance example response

Source: https://www.respira.press/docs/tools/analysis/analyze-performance

An example response for a specific performance analysis request, highlighting identified opportunities for improvement.

```json
{
  "success": true,
  "summary": {
    "grade": "C",
    "score": 68
  },
  "opportunities": [
    {
      "priority": "high",
      "category": "images",
      "message": "Large hero image is unoptimized",
      "details": "Compress and resize hero image; add responsive sizes"
    },
    {
      "priority": "medium",
      "category": "scripts",
      "message": "Too much JS on initial load",
      "details": "Delay non-critical scripts and remove unused plugins"
    }
  ]
}
```

--------------------------------

### Install Cowork plugin via Claude Code

Source: https://www.respira.press/docs/configuration

Use these commands in the Claude Code CLI to add and install the Respira plugin.

```bash
/plugin marketplace add respira-press/cowork-plugin-wordpress
/plugin install respira
```

--------------------------------

### GET /media

Source: https://www.respira.press/docs/api-reference

List all media files.

```APIDOC
## GET /media

### Description
List all media files (images, videos, etc.).

### Method
GET

### Endpoint
/media
```

--------------------------------

### Spectra Block Structure Example

Source: https://www.respira.press/docs/builders/spectra

Example of the native WordPress block structure used by Spectra, identified by the uagb namespace.

```html
<!-- wp:uagb/container {"block_id":"a1b2c3"} -->
  <!-- wp:uagb/advanced-heading {"headingTitle":"Welcome"} /-->
  <!-- wp:uagb/buttons -->
    <!-- wp:uagb/buttons-child {"label":"Get Started"} /-->
  <!-- /wp:uagb/buttons -->
<!-- /wp:uagb/container -->
```

--------------------------------

### List plugins

Source: https://www.respira.press/docs/api-reference

Retrieves a list of all installed plugins including their status and update availability.

```http
GET /plugins
```

--------------------------------

### Available MCP Server CLI Commands

Source: https://www.respira.press/docs

Reference for common CLI operations including setup, listing sites, and testing connections.

```bash
npx @respira/wordpress-mcp-server --setup   # Run setup wizard
npx @respira/wordpress-mcp-server --list    # List configured sites
npx @respira/wordpress-mcp-server --test    # Test connection to default site
npx @respira/wordpress-mcp-server --help    # Show help
```

--------------------------------

### Respira Workflow Example

Source: https://www.respira.press/docs/builders/overview

Demonstrates the interaction flow between user requests and Respira tools for site analysis and element updates.

```text
You: "What page builder is my site using?"
AI: Uses respira_get_builder_info → "Your site uses Flatsome UX Builder"

You: "Show me the structure of the homepage"
AI: Uses respira_extract_builder_content → Shows sections, rows, columns, elements

You: "Update the hero banner heading to 'Welcome to Our Store'"
AI: Uses respira_find_element → Finds the text_box inside ux_banner
AI: Uses respira_update_element → Updates just that text
```

--------------------------------

### Create a hero section

Source: https://www.respira.press/docs/builders/divi-5

Example of a section containing a row, column, heading, text, and button using simplified settings.

```json
{
  "type": "divi/section",
  "settings": {
    "background_color": "#0f172a",
    "padding": "100px 0px 100px 0px"
  },
  "children": [{
    "type": "divi/row",
    "settings": {"column_structure": "24_24"},
    "children": [{
      "type": "divi/column",
      "children": [
        {"type": "divi/heading", "settings": {"title": "Build Faster", "tag": "h1", "heading_color": "#ffffff", "heading_font_size": "56px", "text_alignment": "center"}},
        {"type": "divi/text", "settings": {"content": "<p>Ship your WordPress site with AI-powered tools.</p>", "text_color": "#94a3b8", "font_size": "20px", "text_alignment": "center"}},
        {"type": "divi/button", "settings": {"button_text": "Get Started", "button_url": "/pricing", "button_bg_color": "#4f46e5", "button_color": "#ffffff"}}
      ]
    }]
  }]
}
```

--------------------------------

### Kadence Block Structure Example

Source: https://www.respira.press/docs/builders/kadence-blocks

Example of the native WordPress block markup used by Kadence Blocks, including nested row and column layouts.

```html
<!-- wp:kadence/rowlayout {"uniqueID":"123_abc"} -->
  <!-- wp:kadence/column -->
    <!-- wp:kadence/advancedheading -->Welcome<!-- /wp:kadence/advancedheading -->
    <!-- wp:kadence/advancedbtn {"uniqueID":"btn1"} /-->
  <!-- /wp:kadence/column -->
<!-- /wp:kadence/rowlayout -->
```

--------------------------------

### One-command install with add-mcp

Source: https://www.respira.press/docs/mcp-install

Uses the add-mcp utility to auto-detect the AI client and configure the MCP server. Requires setting WORDPRESS_URL and WORDPRESS_API_KEY environment variables after execution.

```bash
npx add-mcp "npx -y @respira/wordpress-mcp-server"
```

--------------------------------

### GET /options

Source: https://www.respira.press/docs/api-reference

List WordPress options (with optional search filter).

```APIDOC
## GET /options

### Description
List WordPress options (with optional search filter).

### Method
GET

### Endpoint
/options
```

--------------------------------

### wordpress_install_plugin response format

Source: https://www.respira.press/docs/tools/plugins/install-plugin

The JSON structure returned upon a successful plugin installation request.

```json
{
  "success": true,
  "installed": true,
  "slug": "wordpress-seo"
}
```

--------------------------------

### Bulk Update Prompt Example

Source: https://www.respira.press/docs/guides/bulk-content-updates

A template for instructing the AI to identify, modify, and verify content changes across multiple pages while maintaining formatting integrity.

```text
I want to update 10 pages safely.

1) List all published pages and identify the ones that contain the phrase “Book a call”.
2) For each matching page, create a safe update that replaces ONLY that phrase with “Schedule a call”.
3) Do not change anything else. Keep the rest of the HTML and formatting identical.
4) Return a summary of pages changed (page ID + old snippet + new snippet).
5) Then apply the updates using Respira’s duplicate-first workflow.
```

--------------------------------

### Example JSON Response

Source: https://www.respira.press/docs/tools/custom-posts/list-post-types

The tool returns a JSON object containing a success status and an array of post type objects.

```json
{
  "success": true,
  "post_types": [
    {
      "type": "page",
      "label": "Pages"
    },
    {
      "type": "post",
      "label": "Posts"
    }
  ]
}
```

--------------------------------

### Resolve Windows npx Path Issues

Source: https://www.respira.press/docs/troubleshooting

Use the full path to npx or install the package globally on Windows.

```bash
C:\Program Files\nodejs\npx.cmd
```

```bash
npm install -g @respira/wordpress-mcp-server
```

--------------------------------

### wordpress_list_plugins

Source: https://www.respira.press/docs/tools/plugins/list-plugins

Lists all installed plugins with their status, version, and update availability.

```APIDOC
## wordpress_list_plugins

### Description
Lists all installed plugins with their status, version, and update availability. Requires plugin management to be enabled in Respira settings.

### Parameters
This tool takes no parameters.

### Response
- **success** (boolean) - Indicates if the request was successful.
- **plugins** (array) - A list of installed plugins.
  - **slug** (string) - The plugin slug.
  - **name** (string) - The display name of the plugin.
  - **status** (string) - The current status (e.g., active).
  - **version** (string) - The current version of the plugin.
  - **update_available** (boolean) - Indicates if an update is available.

### Response Example
{
  "success": true,
  "plugins": [
    {
      "slug": "woocommerce",
      "name": "WooCommerce",
      "status": "active",
      "version": "9.0.0",
      "update_available": false
    }
  ]
}
```

--------------------------------

### Example Response Structure

Source: https://www.respira.press/docs/tools/builders/get-page-outline

The tool returns a JSON object containing a success flag and an array of row objects, each detailing the index, type, kind, primary heading, child count, and child types.

```json
{
  "success": true,
  "outline": [
    {
      "index": 0,
      "type": "et_pb_section",
      "kind": "section",
      "primary_heading": "Welcome",
      "child_count": 3,
      "child_types": ["et_pb_text", "et_pb_button", "et_pb_image"]
    }
  ]
}
```

--------------------------------

### Check Node.js version

Source: https://www.respira.press/docs/installation

Verify that the installed Node.js version meets the minimum requirement of 18 or higher.

```bash
node --version
```

--------------------------------

### Manage Respira WordPress MCP Server via CLI

Source: https://www.respira.press/docs/mcp-install

Use these commands to perform setup, diagnostics, and configuration management for the MCP server.

```bash
npx @respira/wordpress-mcp-server --setup   # Run setup wizard
npx @respira/wordpress-mcp-server --doctor   # Diagnose connection, auth, and config issues
npx @respira/wordpress-mcp-server --list    # List configured sites
npx @respira/wordpress-mcp-server --test    # Test connection to default site
npx @respira/wordpress-mcp-server --help    # Show help
```

--------------------------------

### GET /post-types

Source: https://www.respira.press/docs/api-reference

List all registered post types.

```APIDOC
## GET /post-types

### Description
List all registered post types.

### Method
GET

### Endpoint
/post-types
```

--------------------------------

### GET /posts

Source: https://www.respira.press/docs/api-reference

List all blog posts with optional filtering.

```APIDOC
## GET /posts

### Description
List all blog posts with optional filtering.

### Method
GET

### Endpoint
/posts
```

--------------------------------

### Switch site

Source: https://www.respira.press/docs/api-reference

Changes the active site context for multi-site WordPress installations.

```http
POST /sites/switch
```

--------------------------------

### Example JSON Response

Source: https://www.respira.press/docs/tools/context/get-theme-docs

The structure of the response returned by the tool, containing theme metadata and a list of available template files.

```json
{
  "success": true,
  "theme": {
    "name": "My Theme",
    "version": "1.0.0"
  },
  "templates": [
    "front-page.php",
    "page.php",
    "single.php",
    "archive.php"
  ],
  "notes": "Theme-specific docs and template availability"
}
```

--------------------------------

### GET /comments/{id}

Source: https://www.respira.press/docs/api-reference

Get comment details.

```APIDOC
## GET /comments/{id}

### Description
Get comment details.

### Method
GET

### Endpoint
/comments/{id}

### Parameters
#### Path Parameters
- **id** (string) - Required - The unique identifier of the comment.
```

--------------------------------

### Run diagnostic commands for Respira MCP server

Source: https://www.respira.press/docs/troubleshooting

Use these commands to verify connectivity, list configured sites, or re-initialize the setup wizard.

```bash
# Test your connection
npx @respira/wordpress-mcp-server --test

# List configured sites
npx @respira/wordpress-mcp-server --list

# Re-run setup wizard
npx @respira/wordpress-mcp-server --setup
```

--------------------------------

### Get menu

Source: https://www.respira.press/docs/api-reference

Retrieve a specific menu including its items and hierarchy.

```http
GET /menus/{id}
```

--------------------------------

### GET /taxonomies/{taxonomy}

Source: https://www.respira.press/docs/api-reference

Get taxonomy details.

```APIDOC
## GET /taxonomies/{taxonomy}

### Description
Get taxonomy details.

### Method
GET

### Endpoint
/taxonomies/{taxonomy}

### Parameters
#### Path Parameters
- **taxonomy** (string) - Required - The taxonomy name
```

--------------------------------

### Example JSON Response for Custom Post Listing

Source: https://www.respira.press/docs/tools/custom-posts/list-custom-posts

The response structure returned when successfully querying custom posts.

```json
{
  "success": true,
  "type": "product",
  "posts": [
    {
      "id": 3001,
      "title": "Product A",
      "status": "publish"
    }
  ]
}
```

--------------------------------

### GET /menus/locations

Source: https://www.respira.press/docs/api-reference

Get all registered menu locations.

```APIDOC
## GET /menus/locations

### Description
Get all registered menu locations.

### Method
GET

### Endpoint
/menus/locations
```

--------------------------------

### GET /context/builder-info

Source: https://www.respira.press/docs/api-reference

Returns information about the active page builder including available modules/widgets.

```APIDOC
## GET /context/builder-info

### Description
Returns information about the active page builder including available modules/widgets.

### Method
GET

### Endpoint
/context/builder-info
```

--------------------------------

### Define a two-column feature row

Source: https://www.respira.press/docs/builders/divi-5

Example of a row with two columns, each containing a blurb module configured with simplified settings.

```json
{
  "type": "divi/row",
  "settings": {"column_structure": "12_24,12_24"},
  "children": [
    {"type": "divi/column", "children": [{"type": "divi/blurb", "settings": {"title": "Fast Setup", "content": "<p>Connect in under 2 minutes.</p>", "heading_color": "#1e293b", "text_color": "#64748b"}}]},
    {"type": "divi/column", "children": [{"type": "divi/blurb", "settings": {"title": "Secure by Default", "content": "<p>API keys, snapshots, governance.</p>", "heading_color": "#1e293b", "text_color": "#64748b"}}]}
  ]
}
```

--------------------------------

### POST /sites/switch

Source: https://www.respira.press/docs/api-reference

Switches to a different WordPress site in a multi-site setup.

```APIDOC
## POST /sites/switch

### Description
Switch to a different WordPress site (for multi-site setups).

### Method
POST

### Endpoint
/sites/switch
```

--------------------------------

### GET /users/{id}

Source: https://www.respira.press/docs/api-reference

Get user details by ID.

```APIDOC
## GET /users/{id}

### Description
Get user details by ID.

### Method
GET

### Endpoint
/users/{id}

### Parameters
#### Path Parameters
- **id** (string) - Required - The user ID
```

--------------------------------

### Define a Case Study Playbook

Source: https://www.respira.press/docs/playbooks

Example of a JSON Playbook definition that accepts client inputs and uses a capture to return specific post data.

```json
{
  "id": "case-study-create",
  "label": "Create Case Study",
  "description": "Creates a case study post with client name and industry.",
  "input_schema": {
    "type": "object",
    "properties": {
      "client_name": { "type": "string" },
      "industry": { "type": "string" }
    },
    "required": ["client_name"]
  },
  "steps": [
    {
      "tool": "respira_create_custom_post",
      "args": {
        "type": "post",
        "title": "{{input.client_name}} case study",
        "status": "draft",
        "content": "How {{input.client_name}} works in {{input.industry}}."
      },
      "capture": "post"
    }
  ],
  "returns": {
    "post_id": "{{post.id}}",
    "url": "{{post.link}}"
  }
}
```

--------------------------------

### Example JSON Response

Source: https://www.respira.press/docs/tools/builders/extract-content

The structure returned by the tool, showing nested sections, rows, columns, and module definitions.

```json
{
  "success": true,
  "builder": "divi",
  "pageId": 42,
  "structure": {
    "sections": [
      {
        "rows": [
          {
            "columns": [
              {
                "modules": [
                  {
                    "type": "et_pb_text",
                    "admin_label": "Hero Text",
                    "content": "<h1>Welcome</h1>"
                  }
                ]
              }
            ]
          }
        ]
      }
    ]
  }
}
```

--------------------------------

### GET /context/site-info

Source: https://www.respira.press/docs/api-reference

Returns comprehensive information about the WordPress site including version, theme, plugins, and detected page builders.

```APIDOC
## GET /context/site-info

### Description
Returns comprehensive information about the WordPress site including version, theme, plugins, and detected page builders.

### Method
GET

### Endpoint
/context/site-info
```

--------------------------------

### Gutenberg post_content structure

Source: https://www.respira.press/docs/builders/gutenberg

Example of how content is stored using HTML with block comment delimiters.

```html
<!-- wp:heading {"level":1} -->
<h1 class="wp-block-heading">Welcome to Our Site</h1>
<!-- /wp:heading -->

<!-- wp:paragraph -->
<p>This is the introduction paragraph with some <strong>bold text</strong>.</p>
<!-- /wp:paragraph -->

<!-- wp:button {"backgroundColor":"primary"} -->
<div class="wp-block-button">
  <a class="wp-block-button__link has-primary-background-color">Get Started</a>
</div>
<!-- /wp:button -->
```

--------------------------------

### Configure Cowork manually on Mac or Linux

Source: https://www.respira.press/docs/configuration

Move the downloaded configuration file to the required directory to enable site access.

```bash
mkdir -p ~/.respira && mv ~/Downloads/config.json ~/.respira/config.json
```

--------------------------------

### GET /post-types/{type}

Source: https://www.respira.press/docs/api-reference

Get post type details.

```APIDOC
## GET /post-types/{type}

### Description
Get post type details.

### Method
GET

### Endpoint
/post-types/{type}

### Parameters
#### Path Parameters
- **type** (string) - Required - The post type identifier
```

--------------------------------

### GET /taxonomies/{taxonomy}/terms/{id}

Source: https://www.respira.press/docs/api-reference

Get term details.

```APIDOC
## GET /taxonomies/{taxonomy}/terms/{id}

### Description
Get term details.

### Method
GET

### Endpoint
/taxonomies/{taxonomy}/terms/{id}

### Parameters
#### Path Parameters
- **taxonomy** (string) - Required - The taxonomy name
- **id** (string) - Required - The term ID
```

--------------------------------

### Get Page Structure Prompt

Source: https://www.respira.press/docs/prompts

Use this prompt to retrieve a breakdown of the sections present on a specific webpage.

```text
Get the structure of my homepage and show me what sections it has.
```

--------------------------------

### GET /media/{id}

Source: https://www.respira.press/docs/api-reference

Get single media item details.

```APIDOC
## GET /media/{id}

### Description
Get single media item details.

### Method
GET

### Endpoint
/media/{id}

### Parameters
#### Path Parameters
- **id** (string) - Required - The media ID
```

--------------------------------

### GET /posts/{id}

Source: https://www.respira.press/docs/api-reference

Get full content of a specific post.

```APIDOC
## GET /posts/{id}

### Description
Get full content of a specific post.

### Method
GET

### Endpoint
/posts/{id}

### Parameters
#### Path Parameters
- **id** (string) - Required - The unique identifier of the post
```

--------------------------------

### GET /post-types/{type}/posts/{id}

Source: https://www.respira.press/docs/api-reference

Get custom post details.

```APIDOC
## GET /post-types/{type}/posts/{id}

### Description
Get custom post details.

### Method
GET

### Endpoint
/post-types/{type}/posts/{id}

### Parameters
#### Path Parameters
- **type** (string) - Required - The post type identifier
- **id** (string) - Required - The post ID
```

--------------------------------

### Flatsome Shortcode Hierarchy Example

Source: https://www.respira.press/docs/builders/flatsome

Demonstrates the standard nesting structure for Flatsome elements, including sections, rows, columns, and content elements like banners and text boxes.

```shortcode
[section bg_color="#1a1a2e" padding="60px"]
  [row]
    [col span="6"]
      [ux_banner height="400px" bg="hero.jpg"]
        [text_box text_color="light" width="60" position_x="50" position_y="50"]
          <h1>Welcome</h1>
          <p>Your content here</p>
        [/text_box]
      [/ux_banner]
    [/col]
    [col span="6"]
      [featured_box img_width="60" pos="top" title="Feature"]
        Description text
      [/featured_box]
    [/col]
  [/row]
[/section]
```

--------------------------------

### GET /analyze/core-web-vitals/{page_id}

Source: https://www.respira.press/docs/api-reference

Get Core Web Vitals metrics (LCP, FID, CLS) for a page.

```APIDOC
## GET /analyze/core-web-vitals/{page_id}

### Description
Get Core Web Vitals metrics (LCP, FID, CLS) for a page.

### Method
GET

### Endpoint
/analyze/core-web-vitals/{page_id}

### Parameters
#### Path Parameters
- **page_id** (string) - Required - The unique identifier of the page.
```

--------------------------------

### Constrained AI Prompt Example

Source: https://www.respira.press/docs/woocommerce/safety

A template for writing explicit prompts that restrict AI modifications to specific product fields and prevent changes to sensitive data like pricing or stock.

```text
For the products with SKUs HOODIE-OC-1 and SHIRT-LN-2:
- Improve titles, short descriptions, and long descriptions
- Keep SKUs, prices, tax classes, and stock levels exactly as they are
- Create duplicates instead of modifying live products
Summarize all changes at the end.
```

--------------------------------

### List configured WordPress sites via CLI

Source: https://www.respira.press/docs/usage

Use this command to display all WordPress sites currently configured in the Respira server.

```bash
npx @respira/wordpress-mcp-server --list
```

--------------------------------

### Create menu

Source: https://www.respira.press/docs/api-reference

Create a new navigation menu.

```http
POST /menus
```

--------------------------------

### GET /taxonomies

Source: https://www.respira.press/docs/api-reference

List all registered taxonomies.

```APIDOC
## GET /taxonomies

### Description
List all registered taxonomies.

### Method
GET

### Endpoint
/taxonomies
```

--------------------------------

### Create user

Source: https://www.respira.press/docs/api-reference

Create a new user account.

```http
POST /users
```

--------------------------------

### GET /comments

Source: https://www.respira.press/docs/api-reference

List all comments with optional filtering.

```APIDOC
## GET /comments

### Description
List all comments with optional filtering.

### Method
GET

### Endpoint
/comments
```

--------------------------------

### POST /users

Source: https://www.respira.press/docs/api-reference

Create a new user.

```APIDOC
## POST /users

### Description
Create a new user.

### Method
POST

### Endpoint
/users
```

--------------------------------

### GET /users

Source: https://www.respira.press/docs/api-reference

List all users with optional filtering.

```APIDOC
## GET /users

### Description
List all users with optional filtering.

### Method
GET

### Endpoint
/users
```

--------------------------------

### Post-migration QA Checklist Prompt

Source: https://www.respira.press/docs/toolkits/divi-5-migration-prompt-pack

Use this prompt to generate a tailored QA checklist by providing site-specific priorities, technical details, and known fragile areas.

```text
You are a senior QA lead for WordPress and Divi-based sites.

I have migrated a site from Divi 4 to Divi 5 using Divi’s Migrator. I need a focused, high-value QA checklist tailored to this site so we catch critical issues before we push to production.

1) SITE PRIORITIES
- List the primary conversion paths (e.g. lead forms, checkout, bookings, contact forms):
- List the top 10–20 pages by importance (home, key landing pages, pricing, product pages, etc.):
- Any pages that are especially brand-sensitive (must look perfect):

2) TECHNICAL DETAILS
- Custom post types that use Divi layouts:
- Use of Divi Theme Builder (headers, footers, templates, archives):
- Third-party integrations (forms, CRMs, payments, booking tools, marketing scripts, A/B testing tools):
- Any known structured data / schema requirements:

3) FRAGILE AREAS
- Pages with heavy animations, motion effects, or complex layouts:
- Known issues from previous theme/builder updates:
- Known performance or Core Web Vitals problems:

4) ENVIRONMENT
- Where QA will be done (staging vs local vs production shadow):
- Devices/browsers we care most about (e.g. iPhone Safari, Chrome desktop, etc.):

Using this information, produce:

A. PRIORITIZED QA CHECKLIST
Organize checks into these sections:
- Business-critical flows
- High-traffic and brand-critical pages
- Templates and global elements (headers, footers, theme builder templates)
- Forms, integrations, and tracking
- Performance and UX sanity checks

For each section:
- Provide a numbered checklist of specific things to verify.
- Include clear pass/fail criteria where possible.

B. QUICK SMOKE TEST
Design a very short (10–15 minute) smoke test I can run immediately after migration to catch show-stopper issues fast.

C. DETAILED PASS TEMPLATE
Provide a simple template I can copy into a ticket or doc to record:
- What was tested
- Who tested
- Date/time
- Findings and severity
- Go/no-go recommendation

D. CLIENT/STAKHOLDER SUMMARY
Write a short, non-technical paragraph summarizing:
- What we checked after the Divi 5 migration
- Whether we saw any major issues
- What will happen next (fixes, sign-off, deployment).
```

--------------------------------

### Get term

Source: https://www.respira.press/docs/api-reference

Retrieve details for a specific term.

```http
GET /taxonomies/{taxonomy}/terms/{id}
```

--------------------------------

### Get taxonomy

Source: https://www.respira.press/docs/api-reference

Retrieve details for a specific taxonomy.

```http
GET /taxonomies/{taxonomy}
```

--------------------------------

### Configure Claude Desktop

Source: https://www.respira.press/docs/inhale-mcp-abilities/connecting-mcp-clients

Add the WordPress MCP server to the Claude Desktop configuration file using basic authentication.

```json
{
  "mcpServers": {
    "wordpress-inhale": {
      "transport": "http",
      "url": "https://your-site.com/wp-json/mcp/mcp-adapter-default-server",
      "auth": {
        "type": "basic",
        "username": "admin",
        "password": "xxxx xxxx xxxx xxxx xxxx xxxx"
      }
    }
  }
}
```

--------------------------------

### Get option

Source: https://www.respira.press/docs/api-reference

Retrieve the value of a specific option by name.

```http
GET /options/{option}
```

--------------------------------

### Migration Readiness Audit Prompt

Source: https://www.respira.press/docs/toolkits/divi-5-migration-prompt-pack

Use this prompt to generate a risk assessment and stakeholder briefing for Divi 5 migrations. Ensure all site context, usage, and customization details are provided to the assistant.

```text
You are a senior WordPress technical lead and Divi specialist.

I am planning a migration from Divi 4 to Divi 5 for this site. I need a concise, practical readiness audit that a web agency or technical site owner can use to plan the migration and communicate risk to stakeholders.

1) SITE CONTEXT
- WordPress version:
- PHP version:
- Hosting type (shared/managed/VPS/other) and caching stack:
- Current Divi version and whether Divi 5 is already installed:
- Does the site use a child theme? If yes, describe what it customizes:
- Any known performance, SEO, or accessibility constraints that must not regress:

2) DIVI USAGE
- Approximate number of Divi-built pages:
- Use of Divi Theme Builder (headers, footers, templates, archive templates, etc.):
- Use of global modules and global presets:
- Use of dynamic content (ACF, Toolset, custom fields, etc.):
- Any usage of Divi’s legacy or deprecated modules:
- Any third-party Divi add-ons or modules:

3) CUSTOMIZATIONS
- Custom PHP (functions.php, mu-plugins, snippets) that touch Divi output:
- Custom JavaScript related to layout, animations, or interactions:
- Custom CSS frameworks or utility classes used alongside Divi:
- Any custom post types with Divi layouts:
- Any custom integrations that rely on specific HTML structure or classes:

4) BUSINESS CONSTRAINTS
- Allowed maintenance window(s):
- Recovery time objective (how long the site can be partially broken):
- Stakeholders who must approve the migration (roles, not names):

Using only the information provided, produce:

A. HIGH-LEVEL SUMMARY
- 3–5 bullet summary of overall migration risk (low/medium/high) and why.

B. RISK CATEGORIES
List risks under these headings. For each, give:
- Risk description
- Why it matters in a Divi 4 → Divi 5 migration
- How to confirm whether it is a real issue
- Recommended mitigation

Categories:
- Theme and child theme risks
- Plugin and Divi add-on risks
- Custom code risks (PHP, JS, CSS)
- Layout and UX risks
- Performance, SEO, and accessibility risks
- Operational/process risks (backups, staging, approvals)

C. PRIORITIZED MIGRATION ORDER
- Suggest an order in which to migrate sections or entire sites, based on risk and business impact.
- Call out any sections that should be delayed until later (and why).

D. STAKEHOLDER BRIEFING
Write a short, non-technical summary I can paste into an email or ticket to stakeholders, covering:
- Why we are migrating to Divi 5 now
- The main risks you identified (in plain language)
- How we will reduce those risks (staging, backups, QA)
- What stakeholders should expect during the migration window.
```

--------------------------------

### Get comment

Source: https://www.respira.press/docs/api-reference

Retrieve details for a specific comment by ID.

```http
GET /comments/{id}
```

--------------------------------

### Verify Ability Registration via WP-CLI

Source: https://www.respira.press/docs/inhale-mcp-abilities/troubleshooting

Use this command to list all registered abilities and verify if a specific ability is present in the system.

```bash
wp ability list
```

--------------------------------

### GET /taxonomies/{taxonomy}/terms

Source: https://www.respira.press/docs/api-reference

List terms in a taxonomy.

```APIDOC
## GET /taxonomies/{taxonomy}/terms

### Description
List terms in a taxonomy.

### Method
GET

### Endpoint
/taxonomies/{taxonomy}/terms

### Parameters
#### Path Parameters
- **taxonomy** (string) - Required - The taxonomy name
```

--------------------------------

### Get user

Source: https://www.respira.press/docs/api-reference

Retrieve details for a specific user by ID.

```http
GET /users/{id}
```

--------------------------------

### Compatibility Mode Cleanup Prompt

Source: https://www.respira.press/docs/toolkits/divi-5-migration-prompt-pack

Use this prompt to generate a strategic plan for transitioning a Divi 5 site away from Compatibility Mode.

```text
You are a senior Divi implementer experienced with Divi 5 and Compatibility Mode trade-offs.

I have a site that has been migrated to Divi 5 using Divi’s Migrator. Many layouts still rely on Compatibility Mode. I want a practical plan to reduce that dependency without breaking important pages.

1) COMPATIBILITY MODE STATUS
- Is Compatibility Mode currently enabled globally?
- Are there any per-page overrides or exceptions?
- Any attempts so far to disable or restrict Compatibility Mode? What happened?

2) LAYOUT INVENTORY
Describe, at a high level:
- Types of layouts in use (landing pages, blog posts, shop pages, archives, etc.).
- Examples of layouts that clearly break when Compatibility Mode is disabled (what breaks?).
- Examples of layouts that still look fine without Compatibility Mode.
- Any third-party Divi modules or add-ons that seem to depend on legacy behavior.

3) CUSTOM CODE & INTEGRATIONS
- Custom CSS that targets Divi-specific classes or markup:
- JavaScript that relies on specific Divi DOM structure or events:
- Any integrations (forms, tracking scripts, A/B testing) that may rely on legacy markup:

4) CONSTRAINTS
- Time available for cleanup per site (e.g. 2 hours, 1 day, multiple days):
- How strictly do layouts need to match existing designs (pixel-perfect vs “close enough”):
- Any pages or flows that are business-critical and must be handled with extra care:

Using this information, produce:

A. CLEANUP STRATEGY OVERVIEW
- Explain the recommended approach to reducing Compatibility Mode usage for this site.
- Call out which categories of pages should stay in Compatibility Mode for now, and which are candidates for early cleanup.

B. CLASSIFICATION FRAMEWORK
Provide a simple framework I can use to classify pages into:
- “Safe without Compatibility Mode”
- “Needs partial refactor”
- “Leave in Compatibility Mode for now”
For each category, describe:
- Typical symptoms
- How to test quickly
- Recommended action

C. PHASED CLEANUP PLAN
Propose a phased plan with concrete steps:
- Phase 1: Quick wins and low-risk pages.
- Phase 2: Medium complexity pages.
- Phase 3: High-risk or business-critical flows.
For each phase, include:
- Entry criteria (which pages to tackle).
- A numbered checklist for what to do on each page.
- Exit criteria (how I know the phase is complete).

D. TESTING CHECKLIST
Create a repeatable checklist I can use when toggling Compatibility Mode for a page or group of pages, covering:
- Visual layout checks
- Functional checks (forms, navigation, CTAs)
- Responsive checks (mobile/tablet/desktop)
- Performance and Core Web Vitals considerations (at a high level).

E. COMMUNICATION NOTES
Write a short note I can share with stakeholders that:
- Explains what Compatibility Mode is in plain language.
- Describes why we are trying to reduce reliance on it.
- Sets expectations about which pages may change slightly and why.
```

--------------------------------

### Get menu locations

Source: https://www.respira.press/docs/api-reference

Retrieve all registered menu locations.

```http
GET /menus/locations
```

--------------------------------

### POST /menus

Source: https://www.respira.press/docs/api-reference

Create a new navigation menu.

```APIDOC
## POST /menus

### Description
Create a new navigation menu.

### Method
POST

### Endpoint
/menus
```

--------------------------------

### Manage Taxonomies

Source: https://www.respira.press/docs/usage

Commands for listing and creating categories for site content.

```text
List all categories on my blog
```

```text
Create a new category called "Tutorials" with slug "tutorials"
```

--------------------------------

### wordpress_switch_site Response Format

Source: https://www.respira.press/docs/tools/other/switch-site

The tool returns a JSON object confirming the operation status and the newly active site ID.

```json
{
  "success": true,
  "activeSite": "staging"
}
```

--------------------------------

### Get media details

Source: https://www.respira.press/docs/api-reference

Retrieves details for a single media item.

```http
GET /media/{id}
```

--------------------------------

### Manage Media Library

Source: https://www.respira.press/docs/usage

Commands for listing media files and identifying accessibility improvements.

```text
List all images in my media library
```

```text
Find images without alt text and suggest descriptions
```

--------------------------------

### GET /analyze/seo-issues/{page_id}

Source: https://www.respira.press/docs/api-reference

Quick check for common SEO issues with recommendations.

```APIDOC
## GET /analyze/seo-issues/{page_id}

### Description
Quick check for common SEO issues with recommendations.

### Method
GET

### Endpoint
/analyze/seo-issues/{page_id}

### Parameters
#### Path Parameters
- **page_id** (string) - Required - The unique identifier of the page.
```

--------------------------------

### GET /post-types/{type}/posts

Source: https://www.respira.press/docs/api-reference

List posts of a custom post type.

```APIDOC
## GET /post-types/{type}/posts

### Description
List posts of a custom post type.

### Method
GET

### Endpoint
/post-types/{type}/posts

### Parameters
#### Path Parameters
- **type** (string) - Required - The post type identifier
```

--------------------------------

### Get custom post details

Source: https://www.respira.press/docs/api-reference

Retrieves details for a specific custom post.

```http
GET /post-types/{type}/posts/{id}
```

--------------------------------

### Read-only site discovery prompts

Source: https://www.respira.press/docs/builders/site-editor

Use these prompts to query block templates, template parts, and patterns without modifying site structure.

```text
List the block templates on this site and tell me which ones
are theme-provided and which ones have been customised.
```

```text
Show me the header template part and the navigation inside it.
Do not change anything.
```

```text
List the synced patterns on this site and tell me which pages use them.
```

--------------------------------

### Get post type details

Source: https://www.respira.press/docs/api-reference

Retrieves details for a specific post type.

```http
GET /post-types/{type}
```

--------------------------------

### Invoke a Playbook

Source: https://www.respira.press/docs/playbooks

Example of calling a registered Playbook using the respira_invoke_ability tool.

```text
respira_invoke_ability({
  ability: "respira-playbooks/case-study-create",
  args: { client_name: "AcmeBank", industry: "fintech" }
})
```

--------------------------------

### CLI options for MCP server

Source: https://www.respira.press/docs/installation

Common CLI commands for managing, diagnosing, and testing the MCP server connection.

```bash
npx @respira/wordpress-mcp-server --setup    # Run setup wizard
npx @respira/wordpress-mcp-server --doctor   # Diagnose connection, auth, and config issues
npx @respira/wordpress-mcp-server --list     # List configured sites
npx @respira/wordpress-mcp-server --test     # Test connection to default site
npx @respira/wordpress-mcp-server --help     # Show help
```

--------------------------------

### GET /analyze/structured-data/{page_id}

Source: https://www.respira.press/docs/api-reference

Checks schema markup and structured data for AI parsing.

```APIDOC
## GET /analyze/structured-data/{page_id}

### Description
Check schema markup and structured data (JSON-LD, microdata) for AI parsing.

### Method
GET

### Endpoint
/analyze/structured-data/{page_id}

### Parameters
#### Path Parameters
- **page_id** (string) - Required - The unique identifier of the page.
```

--------------------------------

### Components & Templates

Source: https://www.respira.press/docs/builders/bricks

Methods for listing, retrieving, and applying Bricks components and templates.

```APIDOC
## Component Methods

- `respira_list_bricks_components`: List all Bricks components/templates.
- `respira_get_bricks_component`: Get a specific component's structure.
- `respira_apply_bricks_component`: Apply a component to a page location.
```

--------------------------------

### Get Core Web Vitals

Source: https://www.respira.press/docs/api-reference

Retrieve LCP, FID, and CLS metrics for a specific page.

```http
GET /analyze/core-web-vitals/{page_id}
```
Tokens:
Raw