FastPixel AI Assistants (MCP)

Use FastPixel with AI Assistants via MCP #

FastPixel now supports the Model Context Protocol (MCP), allowing you to manage your website’s cache and troubleshoot optimization issues directly from compatible AI assistants, using natural language.

Instead of navigating through WordPress settings, you can simply ask your AI assistant questions like:

• “How many pages are currently cached by FastPixel?”
• “Is my homepage cached and up to date?”
• “Clear the cache for my contact page.”
• “Exclude my checkout page from FastPixel optimization.”
• “Check if FastPixel is configured correctly.”

Your AI assistant can retrieve information from FastPixel and perform supported actions on your WordPress website.

What is MCP? #

MCP (Model Context Protocol) is an open standard that allows AI assistants to communicate with external applications and services.

With MCP, compatible AI assistants such as ChatGPT, Claude, and other MCP-enabled tools can access specific FastPixel features on your WordPress website.

Once connected, you can interact with FastPixel through simple conversations.

For example, instead of manually checking the cache statistics, you could ask:

“Check my FastPixel cache status and tell me if everything looks normal.”

The assistant can retrieve the relevant information and explain the results.

Important: MCP does not automatically give an AI assistant unrestricted access to your website. The available actions depend on the tools exposed through your connection and the permissions granted to it.

Getting started #

To use FastPixel’s MCP functionality, you need:

1. A WordPress website with a version of FastPixel that supports MCP.
2. An MCP-compatible AI assistant.
3. An MCP connection to your WordPress website, configured with appropriate permissions.

The exact connection procedure depends on your AI assistant and your WordPress MCP configuration.

Once your assistant is connected, ask:

“List the FastPixel tools available on my website.”

You should be able to access seven FastPixel abilities covering cache statistics, individual pages, cache purging, exclusions, and diagnostics.

Let’s explore what you can do with them.

---

1. Check your website’s cache status #

Example prompt:

“Show me the current FastPixel cache statistics for my website.”

FastPixel can provide an overview of your page cache, including:

Information	What it means
API key configured	Whether a FastPixel API key is set
Cache directory	Whether the cache directory exists
Cached pages	Number of cached page variants
Cache size	Total disk space used by the cached files
Cache hits	Number of requests served from the cache
Cache misses	Number of requests that were not served from the cache
Cache hit ratio	Percentage of counted requests that resulted in cache hits
Serve stale	Whether previously cached content can be served while a fresh version is needed
Cached content for logged-in users	Whether the corresponding cache display setting is enabled

Understanding the cache hit ratio #

The cache hit ratio is one of the most useful statistics.

For example, suppose FastPixel reports:

• Cache hits: 8,000
• Cache misses: 2,000
• Cache hit ratio: 80%

This means that 80% of the counted requests were served from the cache.

A higher cache hit ratio generally means more requests can benefit from cached content, although the expected ratio depends on your website’s traffic patterns and configuration.

Why are there more cached pages than actual website pages? #

FastPixel may store multiple cached versions of the same URL.

For example, a single page might have separate cache entries for desktop, mobile, query-string variations, or other cache variants.

Each variant is counted separately.

Therefore, the number of cached pages reported by FastPixel may be higher than the number of published WordPress pages.

More prompts to try #

“What’s my FastPixel cache hit ratio?”

“How much disk space is the FastPixel cache using?”

“Is FastPixel configured to serve stale cached content?”

“Check whether my FastPixel API key is configured.”

MCP ability: fastpixel/get-cache-status

---

2. Check whether a specific page is cached #

Sometimes you want to check just one page, especially after publishing or updating content.

Example prompt:

“Is https://example.com/about/ cached by FastPixel?”

FastPixel can report:

• Whether the page currently has a cached version.
• Whether that cached version needs to be refreshed.
• When the page was cached.
• When its cache was invalidated, if applicable.
• When the page was last requested, if known.
• Whether an error occurred during the last optimization attempt.

Example #

You ask:

“Check the FastPixel cache status for /about/.”

The assistant might report:

• Cached: Yes
• Needs refresh: No
• Cached at: November 3, 2026, 10:30 UTC
• Last requested: November 3, 2026, 12:15 UTC
• Last optimization error: None

This tells you that the page has a cached version and FastPixel does not currently consider it in need of refreshing.

What does “needs refresh” mean? #

If FastPixel reports that a page needs refreshing, its cached version has been marked as requiring an update.

For example, this might happen after content changes or cache invalidation.

You can ask your assistant to check the page again or purge its cache to request fresh optimization.

What if a page isn’t cached? #

A page without a cached version is not necessarily experiencing a problem.

It might not have been requested yet, could have been purged, or might be excluded from optimization.

If you’re unsure, ask:

“My /contact/ page isn’t cached. Check whether it’s excluded and run FastPixel diagnostics if necessary.”

Note: The individual page cache status tool checks the desktop cache version. It does not provide a complete status report for every mobile, query-string, or other cache variation.

MCP ability: fastpixel/get-page-cache-status

---

3. Clear the cache for a specific page #

If you’ve updated a page and want FastPixel to generate a fresh optimized version, you can ask your AI assistant to purge its cache.

Example prompt:

“Purge the FastPixel cache for /about/.”

FastPixel will invalidate the relevant page cache and request fresh optimization.

You can identify the page in different ways:

Using a full URL:

“Clear the FastPixel cache for https://example.com/pricing/.”

Using a relative path:

“Purge the cache for /pricing/.”

Using a WordPress post or page ID:

“Purge the FastPixel cache for WordPress page ID 123.”

FastPixel also supports purging by a term ID.

When should you purge a page? #

You might want to purge its cache when:

• You’ve changed the page’s content or layout.
• Your visitors are still seeing an outdated version.
• You’ve changed important page elements.
• You want to request a fresh optimization.

After purging, you can ask:

“Check the cache status of /pricing/ again.”

Important: Purging initiates cache invalidation and requests fresh optimization. It does not guarantee that the new optimized page is immediately available.

MCP ability: fastpixel/purge-cache

---

4. Clear your entire website’s cache #

You can also purge all cached pages at once.

Example prompt:

“Purge the entire FastPixel cache and request fresh optimization.”

This is useful after significant website changes, such as:

• Updating your WordPress theme.
• Making site-wide design changes.
• Changing important CSS or JavaScript files.
• Making major updates that affect many pages.

Two ways to purge the entire cache #

FastPixel supports two different behaviors.

Option A: Purge and request fresh optimization

“Clear my entire FastPixel cache and request fresh optimization.”

FastPixel invalidates the existing cache and requests fresh optimization.

This is the default behavior.

Option B: Purge without immediately requesting optimization

“Invalidate the entire FastPixel cache, but don’t request immediate optimization. Let pages be re-optimized when visitors access them.”

In this case, FastPixel invalidates the cache but does not immediately request optimization for all pages.

Instead, pages are re-optimized as they are subsequently visited.

This can be useful when you prefer to let the cache rebuild gradually.

Should you clear the entire cache regularly? #

Generally, no.

There’s usually no reason to clear your entire cache frequently if FastPixel is functioning normally.

A full purge invalidates existing cached content, and pages may need to be optimized again.

For small changes affecting a single page, purging only that page is usually preferable.

MCP ability: fastpixel/purge-cache

---

5. Check which pages are excluded from FastPixel #

Some pages should not be optimized or cached by FastPixel.

This is particularly relevant for pages containing dynamic or personalized information.

You can retrieve your exclusion list through your AI assistant.

Example prompt:

“Show me all pages excluded from FastPixel optimization and caching.”

Your assistant might return a list such as:

• /checkout/
• /cart/
• /my-account/
• /private/*

These are examples, not default FastPixel exclusions.

Understanding wildcard exclusions #

FastPixel supports the * wildcard in exclusion paths.

For example:

/private/*

This pattern can be used to exclude pages matching the specified path pattern.

Wildcard exclusions are useful when multiple pages should follow the same exclusion rule.

MCP ability: fastpixel/list-exclusions

---

6. Exclude a page from FastPixel optimization and caching #

You can add exclusions directly through your AI assistant.

Example prompt:

“Exclude /checkout/ from FastPixel optimization and caching.”

FastPixel will add the page to your exclusion list and delete its cached files.

You can specify a page using:

• Its full URL.
• Its relative path.
• Its WordPress post slug.
• A path containing a supported wildcard.

Excluding an entire section #

For example:

“Exclude all pages matching /members/* from FastPixel optimization and caching.”

This can be helpful for sections containing personalized or frequently changing information.

Excluding the homepage #

FastPixel includes an additional safeguard for homepage exclusions.

If you ask:

“Exclude my homepage from FastPixel.”

The operation requires explicit homepage confirmation.

This helps protect you against accidentally disabling optimization and caching for one of your website’s most important pages.

If you’re sure, you can explicitly confirm that you want the homepage excluded.

When should you use exclusions? #

Typical situations include:

• Checkout pages.
• Shopping carts.
• Account pages.
• Pages containing personalized information.
• Pages with dynamic content that should not be served from a page cache.

Some of these pages may already be handled by your existing cache configuration. Check the current exclusions and behavior before adding redundant rules.

MCP ability: fastpixel/add-exclusion

---

7. Remove a page from the exclusion list #

If you previously excluded a page but now want FastPixel to optimize and cache it again, you can remove its exclusion.

Example prompt:

“Remove /about/ from the FastPixel exclusion list.”

FastPixel will remove the matching exclusion and request fresh optimization for the page.

You can then verify the updated exclusion list:

“Show me the FastPixel exclusions again.”

What happens after removing an exclusion? #

Removing an exclusion makes the page eligible for optimization and caching again, subject to the remaining FastPixel configuration.

A fresh optimization is requested, but the updated cache may not be available immediately.

MCP ability: fastpixel/remove-exclusion

---

8. Run FastPixel diagnostics #

One of the most helpful MCP features is the ability to check whether FastPixel is configured correctly.

Example prompt:

“Run FastPixel diagnostics and explain any issues you find.”

FastPixel runs a series of setup checks and returns their results.

These checks cover areas such as:

• FastPixel API key configuration.
• Cache-related drop-in configuration.
• WordPress configuration (wp-config.php).
• Required REST API endpoints.
• Potentially conflicting plugins.
• Other FastPixel setup requirements.

Each diagnostic check includes a pass/fail result and explanatory messages.

Example #

An assistant might summarize the results like this:

FastPixel diagnostic results

• API key: Passed
• Required REST endpoints: Passed
• Cache drop-in: Passed
• WordPress configuration: Passed
• Plugin conflicts: Failed

The assistant can explain the reported problem and suggest potential next steps based on the diagnostic messages.

The exact checks and messages depend on your website’s configuration.

Useful troubleshooting prompts #

“Run FastPixel diagnostics and summarize the results in simple language.”

“Are there any plugin conflicts affecting FastPixel?”

“Check whether FastPixel’s required REST endpoints are working.”

“Run diagnostics and tell me which issues I should investigate first.”

MCP ability: fastpixel/run-diagnostics

---

Practical examples: Managing FastPixel through a conversation #

The real advantage of MCP is that you can combine several operations in a single conversation.

Here are some examples.

Scenario 1: My website is showing outdated content #

You:

“I updated my homepage, but visitors might still be seeing the old version. Check whether it’s cached and needs refreshing.”

The assistant checks your homepage’s cache status.

If it needs refreshing, you can follow up:

“Purge the homepage cache and request fresh optimization.”

Then:

“Check the homepage cache status again.”

Scenario 2: My cache hit ratio seems low #

You:

“Check my FastPixel cache statistics and explain the hit ratio.”

The assistant retrieves the statistics and explains what they mean.

You can then ask:

“List my excluded pages and run FastPixel diagnostics to help identify possible reasons for a low cache hit ratio.”

This allows you to investigate potential problems without manually inspecting several different settings.

Scenario 3: I run a WooCommerce store #

You:

“Show me my FastPixel exclusions. I want to check whether the checkout and account pages are excluded.”

After reviewing the results, you can request an exclusion if necessary:

“Exclude /checkout/ from FastPixel optimization and caching.”

This is particularly useful when managing dynamic e-commerce pages.

Scenario 4: I redesigned my website #

You:

“I’ve updated my website’s theme and layout. Purge the entire FastPixel cache and request fresh optimization.”

After the operation, you can ask:

“Check my cache statistics and confirm whether pages are being cached again.”

Scenario 5: FastPixel doesn’t seem to be working #

You:

“Run FastPixel diagnostics, check whether the API key is set, and tell me if there are any setup problems.”

The assistant gathers the available diagnostic information and helps you understand what needs attention.

---

Available FastPixel MCP abilities #

For advanced users and developers, here is the complete list of supported FastPixel abilities.

Ability	Description	Required input
fastpixel/get-cache-status	Retrieve overall cache statistics and settings	None
fastpixel/get-page-cache-status	Check the desktop cache status of a page	url
fastpixel/purge-cache	Purge one page or the entire cache	One of url, post_id, or all
fastpixel/list-exclusions	List excluded pages and patterns	None
fastpixel/add-exclusion	Exclude a page or path pattern	page
fastpixel/remove-exclusion	Remove a page or pattern from exclusions	page
fastpixel/run-diagnostics	Check FastPixel’s configuration	None

For cache purging, you must specify exactly one target: a URL, a post/term ID, or the entire site.

The optional request_optimization parameter applies only to whole-site purges and defaults to true.

For homepage exclusions, confirm_homepage must be set to true.

These abilities can be discovered and invoked by a properly connected MCP-compatible assistant. You generally don’t need to remember their technical names—the assistant can select the appropriate ability based on your request.

Security and best practices #

AI assistants connected through MCP can perform actions that change your website’s cache behavior.

Keep these recommendations in mind:

1. Use appropriate permissions. Connect your assistant using a WordPress account with only the permissions it needs.
2. Review site-wide operations. Make sure you intend to purge the entire cache before approving such a request.
3. Be careful with wildcard exclusions. An overly broad pattern could disable caching and optimization for more pages than intended.
4. Check before changing settings. Ask your assistant to retrieve the current status or exclusion list before making changes.
5. Verify the results. After purging or changing an exclusion, ask the assistant to check the relevant status again.

Remember that AI assistants can interpret tool results and offer recommendations, but their conclusions should be checked against the actual data returned by FastPixel.

Frequently asked questions #

Do I need programming knowledge to use FastPixel MCP? #

No. Once the MCP connection is configured, you can interact with FastPixel using natural-language requests.

Can I use FastPixel MCP with ChatGPT? #

Yes, provided your ChatGPT environment supports the required MCP connection and has been configured to access your WordPress website.

Does MCP replace the FastPixel WordPress dashboard? #

No. MCP provides an additional way to interact with supported FastPixel features.

You can continue using the FastPixel dashboard as usual.

Can the AI assistant change FastPixel settings? #

The current abilities allow the assistant to inspect cache settings and statistics, purge cached content, manage exclusions, and run diagnostics.

They do not provide general-purpose editing of every FastPixel setting.

Can I check the cache status of any page? #

You can request the desktop cache status of a page using its full URL or a path relative to your website’s home URL.

Does purging the cache automatically optimize every page again? #

Not necessarily.

For a whole-site purge, FastPixel supports requesting fresh optimization immediately or allowing pages to be re-optimized when they are subsequently visited.

Can I ask the assistant to fix every diagnostic problem automatically? #

No. The diagnostics ability reports configuration checks and their results. It does not automatically repair problems.

Your AI assistant may explain the results and recommend possible solutions.

Does the cache statistics tool show real-time visitor analytics? #

No. It reports FastPixel cache statistics, including cache hits and misses. It is not a replacement for a visitor analytics platform.

---

Start managing FastPixel with AI #

FastPixel’s MCP integration gives you another way to interact with your website’s optimization and caching features.

Whether you want to check cache performance, refresh a page, manage exclusions, or investigate configuration issues, you can now do so by simply asking your AI assistant.

A great first prompt is:

“Check my FastPixel cache status, list any excluded pages, run diagnostics, and give me a short summary of my website’s caching health.”

With a single request, your assistant can gather information from several FastPixel abilities and help you understand how your website’s caching is working.