"Inappropriate or harmful content" matching MCP servers:

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

Enables interaction with Prismic through tools for reading documents, managing media assets, and performing content migrations or updates. Supports the Prismic Content, Asset, Migration, and Custom Types APIs with secure write operations and multi-transport support.

Just to be clear about the final JSON: the MCP server is named herdr-inbox, and it enables Claude Code agents in herdr to ask questions asynchronously without stalling, with all open questions answered from one popup and answers routed back to the asking agent.

An MCP server that uses AI to generate structured Asana project plans from diverse sources like text, PDFs, and meeting transcripts. It enables users to preview, generate, and directly sync detailed task lists, subtasks, and dependencies into Asana.

Enables AI models to interact with IBM FileNet Content Manager for document management, folder operations, metadata handling, search, and content extraction through a standardized interface.

An MCP server that provides access to project files and their contents, allowing users to retrieve file data from specified project directories with error handling and configuration options.

Enables AI agents to read and edit a Django site's content over its API, creating tools at startup from whatever resources the site registers so no code changes are needed. Works with any site running django-agent-content, with HTTPS-only API key authentication and no delete operations.

Enables AI-driven batch refactoring of Movable Type content via the MT Data API using natural language instructions. It provides a secure workflow featuring automated backups, visual diff reports, and rollback capabilities for safe HTML transformations.

Enables AI assistants to interact directly with Strapi v5 CMS content through full CRUD operations, media uploads, and content type exploration using Strapi's Document Service API.

Enables AI agents to query OpenRouter model information including prices, ELO rankings, context, and perform comparisons.

Enables AI agents to read Git-backed project context and append validated, audited, idempotent progress events through short-lived, scoped credentials, supporting resumable work and safer handoffs.

Provides a standardized interface for interacting with Ghost-Content tools and services through a unified API.

Enables AI agents to read any web page as clean Markdown and inspect its metadata, structure and technology stack, plus check redirects, TLS certificates, security headers, robots.txt, sitemaps, feeds, domains, SEO, broken links, email authentication (SPF/DMARC/DKIM) and SSO (SAML/OIDC). It also provides developer utilities such as cron, regex, color, Unicode and time-zone tools along with Hyperliquid perpetuals market data, all hosted remotely on Apify with pay-per-call pricing.

It enables AI agents to retrieve Git-backed project context, handoff packages, and next actions, then append validated, audited progress events as project-record commits.

MCP-ORTools integrates Google's OR-Tools constraint programming solver with Large Language Models through the MCP, enabling AI models to: Submit and validate constraint models Set model parameters Solve constraint satisfaction and optimization problems Retrieve and analyze solution

A local, file-based bridge that lets an AI client read, draft, validate, and safely write content into an RPG Maker MV project.

Enables Claude to offload code generation to Google's Gemini, saving tokens by writing files directly to disk without returning the content to the chat.

Enables Codex to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited, idempotent progress events backed by a matching project-record Git commit. Access is scoped to one workspace and project via short-lived, revocable, hash-stored credentials that cannot reach members, keys, deletion, publication, or deployment.

Enables Codex agents to read a project's kickoff card, acceptance criteria, progress, Git trail, and handoff package, then append one validated, idempotent progress event with an agent verification note and matching Git commit. Access is limited to short-lived, scoped, revocable credentials bound to a single workspace and project, with high-risk actions kept outside the tool surface.

Enables MCP clients to read a project's Git-backed kickoff, acceptance criteria, handoff package, progress, and next step, and to append validated, audited progress events as project records. It provides short-lived scoped credentials and fail-closed tool allowlisting for safe, resumable AI-assisted development.