Connect My Site To Ai – Wordpress Mcp Server

Created By
Muntaseer Rahman2 months ago
Turn any WordPress site into an MCP server. Connect Claude, Cursor, or any MCP-compatible AI tool to read content, audit SEO, manage posts, upload media, and handle taxonomies — all via secure OAuth 2.0 with PKCE. 45 tools: 24 free read-only + 21 pro write. No coding required.
Overview

What It Does

Connect My Site to AI is a WordPress plugin that turns any WordPress site into a fully compliant MCP server. AI tools connect via OAuth 2.0 with PKCE and get access to 45 purpose-built tools.

Free Tools (24)

  • Search content by keyword, category, tag, or status
  • Full SEO audit: orphan content, thin content, stale content, duplicate titles
  • Internal link mapping and analysis
  • Media library search and browsing
  • Site health and security audit
  • ACF field groups and values reader
  • Post revision history

Pro Tools (21)

  • Create, update, trash, restore, duplicate, merge posts
  • Find and replace across entire site (dry run default)
  • Upload media from URL, batch-fix alt text
  • Create/delete categories and tags
  • Manage 301/302/307 redirects (Redirection plugin)
  • Schedule future publish dates
  • Bulk update meta fields

Setup

  1. Install the plugin on your WordPress site
  2. Go to Settings > Connect to AI, click "Copy Instructions for AI"
  3. Paste into your AI tool — OAuth handles the rest automatically

Server Config

{
  "mcpServers": {
    "wordpress": {
      "url": "https://your-site.com/wp-json/cmsta/v1/mcp",
      "transport": "http"
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
Muntaseer Rahman
Star
-
Language
-
License
-
Category

Recommend Servers

View All
GovQL
@Alex Stout

# govql-mcp-server An MCP (Model Context Protocol) server for [GovQL](https://govql.us) — gives AI clients like Claude Desktop, Claude Code, and Cursor direct access to the US Congressional GraphQL API at [api.govql.us/graphql](https://api.govql.us/graphql) without bespoke HTTP wiring. For the design rationale (why FastMCP-Python, the passthrough+curated philosophy, roadmap through v0.4), see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md). ## What you can do with it Ask an agent questions like: - *"How did Vermont's two senators vote on the most recent nomination?"* - *"Which legislators in the 118th Congress switched parties during their service?"* - *"Compare Senator Sanders' voting record to Senator Murkowski's on cloture votes in the most recent Congress."* The agent picks the right tool, writes the GraphQL query against the live schema, and parses the response — no manual API wrangling. ## Install The server runs as a per-client subprocess over stdio. Pick your client: ### Claude Desktop Edit `claude_desktop_config.json` (Settings → Developer → Edit Config): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` Restart Claude Desktop. The `govql` tools appear in the tools panel. ### Claude Code Add to `.mcp.json` in your project (or `~/.mcp.json` for global): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` ### Cursor Settings → MCP → Add Server. Use the same `command` / `args` as above. ### Other clients Any MCP-compatible client that supports stdio servers will work. The command is `uvx govql-mcp-server` with no required arguments. ## Tools | Tool | Purpose | |---|---| | `execute_graphql` | Run any GraphQL query against the GovQL endpoint. Returns the result plus an `last_ingest` timestamp so the agent can reason about data freshness. | | `list_types` | Returns the names and kinds of every type in the GovQL schema. Optional `kind` filter (`"OBJECT"`, `"INPUT_OBJECT"`, `"ENUM"`, etc.) to narrow further. Start here when you don't know what's queryable. | | `describe_type` | Returns one type's full details — fields, arg signatures, input fields, enum values. Call after `list_types` to learn the shape of a specific type before writing a query. | ## Configuration All env vars are optional — the package is zero-config for end users. | Env var | Default | Purpose | |---|---|---| | `GOVQL_ENDPOINT` | `https://api.govql.us/graphql` | Endpoint to query. Override to point at a local dev stack. | | `GOVQL_TIMEOUT_MS` | `30000` | Per-request HTTP timeout. | | `LOG_LEVEL` | `INFO` | Logging level. Logs go to stderr only (stdout is reserved for the MCP transport). | ## Limits (enforced by the upstream API) - Max query depth: 10 - Max query complexity: ~10 billion points (`first: N` multiplies child cost by N — keep page sizes reasonable on deeply nested queries) - Rate limit: 100 requests / 60 s per source IP A depth or complexity violation surfaces as a GraphQL `errors` entry in the tool response so the agent can adjust and retry. ## Data freshness Every `execute_graphql` response includes a `last_ingest` ISO timestamp. Vote data refreshes hourly; legislator data refreshes daily. ## Status Version 0.1.0 ships three foundational tools: a GraphQL passthrough (`execute_graphql`) and two narrow schema-discovery tools (`list_types`, `describe_type`). Curated higher-level tools (`find_legislator`, `get_voting_record`, `compare_voters`, etc.) are planned for subsequent releases — see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md) for the roadmap. ## Links - [GovQL project site](https://govql.us) - [GraphQL API](https://api.govql.us/graphql) - [Source / issues](https://github.com/govql/govql)

a day ago
Meok Bs7121 Mcp

9 hours ago