Skip to main content

​
What is a Resource?

Resources are a way to expose data content — documents, files, database query results, or any structured information — to AI clients via the MCP resources/read method. Unlike tools (which execute actions), resources provide read-only content that the AI can reference. Think of resources as:
  • Documentation or knowledge base articles the AI should be aware of
  • Real-time data from your database (e.g., product catalog, user list)
  • Static configuration or reference content
  • WordPress posts/pages exposed as MCP-readable content

​
Resource URI

Every resource has a unique URI that serves as its identifier. URIs follow a URI scheme: 
docs://getting-started
file:///config/settings.json
resource://products/featured
AI clients reference resources by URI when calling resources/read.

​
Resource Properties

PropertyDescription
URIUnique identifier for the resource (e.g., docs://intro)
NameHuman-readable display name
DescriptionWhat the resource contains; used by AI for discovery
MIME TypeContent type (e.g., text/plain, application/json, text/markdown)
Data Source TypeWhere the content comes from
Template URIURI template for parameterized resources

​
Data Source Types

TypeDescription
staticHardcoded content defined directly in GetMCP
urlFetched from an external URL on each read
wp_queryGenerated from a WordPress query (posts, pages, etc.)
dynamicCustom dynamic source via WordPress hooks

​
Static Resources

The simplest type. You define the content directly in the editor and it never changes unless you update it: 
# API Documentation

This server provides tools for managing customer records.

## Available Operations
- `get_customer` — Retrieve a customer by ID
- `create_customer` — Create a new customer record
- `list_customers` — List all customers with pagination
Use static resources for documentation, configuration, or any content that doesn’t change frequently.

​
URL Resources

Content is fetched from an external URL each time the resource is read. Useful for:
  • Live documentation sites
  • External data feeds
  • Remote JSON config files
The URL is fetched server-side by WordPress, so authentication headers can be included if needed.

​
WordPress Query Resources

Query your own WordPress database and expose the results as a resource. For example:
  • All published blog posts (title + excerpt)
  • WooCommerce products (name, price, SKU)
  • Custom post types
  • User lists

​
Resource Templates

Resource templates allow parameterized resources using URI templates (RFC 6570): 
resource://products/{product_id}
An AI client can request resource://products/123 and receive data specific to product 123.

​
Creating a Resource

1

Open the Resources Tab

Inside a server, click the Resources tab.
2

Click Add Resource

Click Add Resource to open the resource editor.
3

Set URI and Name

Enter a URI (e.g., docs://api-overview) and a human-readable name.
4

Choose Data Source

Select the data source type and configure it accordingly.
5

Set MIME Type

Choose the appropriate MIME type for your content (text/plain, text/markdown, application/json, etc.).
6

Save

Click Save. The resource is now available via resources/list and resources/read.
Resource Editor

​
MCP Protocol

Resources integrate with the standard MCP protocol methods:
  • resources/list — Returns all resources for the server (URI, name, description, MIME type)
  • resources/read — Returns the content of a specific resource by URI
  • resources/templates/list — Returns available URI templates