WordPress MCP Integration

Created By
rizaardiyanto1412a year ago
MCP Server for WordPress
Overview

What is WordPress MCP Integration?

WordPress MCP Integration is a streamlined TypeScript SDK that allows interaction with WordPress sites through the WordPress REST API using the Model Context Protocol (MCP).

How to use WordPress MCP Integration?

To use this integration, clone the repository, install the dependencies, and configure your WordPress site credentials either through environment variables or request parameters.

Key features of WordPress MCP Integration?

  • Create, retrieve, and update WordPress posts via the REST API.
  • Supports configuration through environment variables for security.
  • Provides example JSON-RPC calls for each available tool.

Use cases of WordPress MCP Integration?

  1. Automating the creation of blog posts.
  2. Retrieving and displaying posts on a custom frontend.
  3. Updating existing content programmatically.

FAQ from WordPress MCP Integration?

  • Is this integration secure?

Yes, it is recommended to use WordPress application passwords for authentication.

  • What are the requirements to use this integration?

You need Node.js 18.0.0 or higher and a WordPress site with the REST API enabled.

  • Can I run the server on a specific port?

Yes, you can specify a port when starting the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rizaardiyanto1412
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago