Skip to main content
Glama
Leonelberio

WordPress MCP Server

by Leonelberio

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WORDPRESS_PASSWORDNoWordPress application password
WORDPRESS_SITE_URLNoYour WordPress site URL
WORDPRESS_USERNAMENoWordPress username

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
create_postC

Create a new WordPress post

get_postsC

Get WordPress posts

update_postC

Update an existing WordPress post

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose targeting different CRUD operations: create_post for creation, get_posts for retrieval, and update_post for modification. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (create_post, get_posts, update_post) with no deviations in style or convention. This predictability enhances readability and usability for agents.

Tool Count3/5

With only 3 tools, the set feels thin for a WordPress server, as it lacks delete_post and other common operations like managing pages or media. While the tools cover basic post CRUD, the scope is limited and may not support full agent workflows.

Completeness2/5

The tool surface is significantly incomplete for WordPress management. It includes create, get, and update for posts but omits delete_post, as well as tools for pages, media, users, or settings, leaving notable gaps that could cause agent failures in broader tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues