Tools Reference

This page documents all available tools in the WPNuxt MCP server.

WordPress Discovery Tools

wp_connect

Connect to a WordPress site for the current session.

Parameters:

Example:

Connect to https://wordpress.wpnuxt.com

Returns: Site information including title, description, language, and GraphQL endpoint status.

wp_get_site_settings

Fetch WordPress general settings (site title, tagline, URL, etc.).

Parameters: None

Returns: Site title, description, URL, language, and reading settings.

wp_list_content_types

List all content types in WordPress including custom post types.

Parameters: None

Returns: Array of content types with:

• name - Internal name (e.g., post, page, product)
• graphqlSingleName - Singular GraphQL name
• graphqlPluralName - Plural GraphQL name
• hierarchical - Whether content supports parent/child relationships

wp_list_taxonomies

List all taxonomies (categories, tags, custom taxonomies).

Parameters: None

Returns: Array of taxonomies with GraphQL names and associated content types.

wp_list_menus

List all WordPress navigation menus with their items.

Parameters: None

Returns: Array of menus with:

• name - Menu name
• slug - Menu slug
• locations - Theme locations where menu is assigned
• items - Menu items with labels, URLs, and hierarchy

wp_detect_plugins

Detect installed WordPress plugins by analyzing the GraphQL schema.

Parameters: None

Returns: Detected plugins including:

• WooCommerce
• Advanced Custom Fields (ACF)
• Yoast SEO
• WPGraphQL extensions
• Headless Login for WPGraphQL

wp_list_blocks

Analyze Gutenberg blocks used across the site.

Parameters:

Returns: Block usage statistics including:

• Core blocks (paragraph, heading, image, etc.)
• Custom/plugin blocks
• Usage frequency
• Sample attributes

Content Fetching Tools

wp_fetch_posts

Fetch posts from WordPress.

Parameters:

Returns: Posts with title, excerpt, content, featured image, author, and categories.

wp_fetch_pages

Fetch pages from WordPress.

Parameters:

Returns: Pages with title, content, featured image, and parent/child hierarchy.

wp_sample_content

Get sample content for development and testing.

Parameters:

Returns: Sample content items with full data structure.

wp_query

Execute a custom GraphQL query against WordPress.

Parameters:

Returns: Raw GraphQL response.

Code Generation Tools

wpnuxt_init

Generate a complete WPNuxt project based on WordPress site analysis.

Parameters:

Returns: Complete project files including:

• nuxt.config.ts
• package.json
• app.vue
• Default layout
• Home page
• Environment files

wpnuxt_generate_pages

Generate Nuxt page components for WordPress content types.

Parameters:

Returns: Page components with:

• Archive (index) pages
• Single item pages
• Catch-all route for WordPress URIs

wpnuxt_generate_components

Generate Vue components for WordPress content types.

Parameters:

Returns: Components including:

• PostCard.vue / PageCard.vue - Content preview cards
• PostsList.vue / PagesList.vue - Grid list components
• CategoriesList.vue / TagsList.vue - Taxonomy lists
• FeaturedImage.vue - Responsive image component

wpnuxt_generate_queries

Generate custom GraphQL queries for content types.

Parameters:

Returns: GraphQL query files for the extend/queries/ folder.

wpnuxt_generate_block_renderers

Generate Vue components for rendering Gutenberg blocks.

Parameters:

Returns: Block renderer components including:

• BlockRenderer.vue - Main renderer component
• CoreParagraph.vue, CoreHeading.vue, etc. - Core blocks
• Custom block components based on detected usage

wpnuxt_setup_menus

Generate navigation menu components.

Parameters:

Returns: Menu components with:

• Desktop navigation
• Mobile navigation
• Dropdown submenus

Utility Tools

wpnuxt_list_composables

List WPNuxt composables available for the project.

Parameters: None

Returns: Available composables with:

• Default composables (usePosts, usePages, useMenu, etc.)
• Naming convention explanation
• Usage examples

wpnuxt_migrate

Analyze a WPNuxt v1 project and detect usage anti-patterns, then generate migration helpers.

Parameters:

What it scans for:

v1 → v2 Migration Issues:

• Removed composables (useFeaturedImage, useWPUri, usePrevNextPost, isStaging)
• Renamed composables (useWPPosts → usePosts, useAsyncWPPosts → useLazyPosts)
• Renamed directives (v-sanitize → v-sanitize-html)
• Removed components (<WPContent>, <ContentRenderer>, <StagingBanner>)
• Changed configuration options

Usage Anti-Patterns (SSR issues):

• Composables called inside lifecycle hooks (onMounted, etc.) - breaks SSR
• Composables called inside functions instead of top level
• Missing .value access on Refs returned by composables
• Incorrect data assignment patterns

Example of anti-patterns detected:

<script setup>
// ❌ BAD: Composable inside onMounted breaks SSR
onMounted(async () => {
  const { data } = await usePosts()  // Will not work on server!
  posts.value = data || []           // Missing .value on data
})

// ✅ GOOD: Composable at top level
const { data: posts } = await usePosts()
</script>

Returns:

• List of issues with file locations, line numbers, and severity
• Auto-fix suggestions
• Generated compatibility helper file (app/composables/wpnuxt-compat.ts)
• Step-by-step migration instructions

See Migration Guide for more details.