WordPress MCP Integration

Created By
Dmitrii-Demenkoa year ago
This MCP server let you automate interactions with Wordpress
Overview

What is WordPress MCP Integration?

WordPress MCP Integration is a TypeScript SDK that automates interactions with WordPress sites using the Model Context Protocol (MCP) and the WordPress REST API.

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 programmatically.
  • Supports configuration via environment variables for security.
  • Easy-to-use API for managing WordPress content.

Use cases of WordPress MCP Integration?

  1. Automating blog post creation and updates.
  2. Integrating WordPress with other applications for content management.
  3. Streamlining content publishing workflows.

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 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
Dmitrii-Demenko
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago