[{"_1":2,"_264":-5,"_265":-5},"loaderData",{"_3":4,"_53":54,"_55":56,"_227":228},"root",{"_5":6,"_49":50,"_51":52},"appGlobal",{"_7":8,"_38":39,"_40":41},"config",{"_9":10,"_11":12,"_13":14,"_15":16,"_17":18,"_19":20,"_21":22,"_23":-5,"_24":25,"_26":27,"_28":29,"_30":31,"_32":33,"_34":31,"_35":31,"_36":37},"APP_URL","https://glama.ai","CLIENT_ASSETS_URL","https://static.glama.ai/client/","ENVIRONMENT","LIVE","FACEBOOK_PIXEL_ID","1988603181578092","GOOGLE_ANALYTICS_MEASUREMENT_ID","G-GDQ5NW5CB5","GOOGLE_OAUTH2_CLIENT_ID","48173796263-7ohlqirg28gh2a7nel61coff3m1ogjtc.apps.googleusercontent.com","INTERCOM_APP_ID","wgcqevfz","INTERCOM_USER_HASH","POSTHOG_API_KEY","phc_aK0RnJxBEBRE0h0LIz21yyc9w6ylBxwUHMPB4712Bjc","REDDIT_PIXEL_ID","a2_fcqsoymvje51","RELEASE_VERSION","glama@production","SENTRY_DRY_RUN",false,"SENTRY_DSN","https://fc82aa9f808b13927ff29c56bda4d486@o4507975513735168.ingest.us.sentry.io/4507975514849280","SENTRY_SPOTLIGHT","SENTRY_TRACE","STRIPE_PUBLIC_KEY","pk_live_51QpZQ32LV3sZcHqzHlFuNhgSfggSNaQqCzZw9EMJ8tbhpQyZgcwQj1vz168FxQ35EGRcztKu2MankxiSs7zLCF4g00blUverGs","viewportWidth",1280,"visitorSession",{"_42":43,"_45":-5,"_46":47,"_48":-5},"attributes",[44],"BOT","membership","uid","9swr1mep5c","userAccount","nonce","9357082671e0fbbf40ea2b6337813b0d","toasts",[],"routes/_public/_layout",{},"routes/_public/mcp/servers/~uid/_pages/_layout",{"_57":-5,"_58":59,"_147":148},"githubUser","mcpServer",{"_60":61,"_62":63,"_42":80,"_83":84,"_85":84,"_86":87,"_92":93,"_112":113,"_114":31,"_115":116,"_117":118,"_122":-5,"_123":124,"_131":-5,"_132":133,"_138":-5,"_139":140,"_143":-5,"_46":144,"_145":146},"addedAt",["D",1737190845461],"argumentsJsonSchema",{"_64":65,"_66":67,"_69":70},"type","object","required",[68],"WP_SITES_PATH","properties",{"_71":72,"_68":78},"PORT",{"_64":73,"_74":75,"_76":77},"string","default","3000","description","Port for SSE transport (optional).",{"_64":73,"_76":79},"Path to the sites configuration JSON file.",[81,82],"category:other","language:typescript","descriptionMarkdown","A server enabling seamless interaction between AI models and WordPress sites with secure, standardized communication using the WordPress REST API for comprehensive site management.","descriptionPlainText","githubProject",{"_88":89,"_90":91},"readme","# 🤘 Claudeus WordPress MCP 🎸\n> *\"Unleash the Power of AI in Your WordPress Realm - Setting the Standard for MCP Excellence!\"* 🖤\n\n![License](https://img.shields.io/badge/license-MIT-blue.svg)\n![Node](https://img.shields.io/badge/node-%3E%3D22.0.0-brightgreen.svg)\n[![GitHub Stars](https://img.shields.io/github/stars/deus-h/claudeus-wp-mcp.svg)](https://github.com/deus-h/claudeus-wp-mcp/stargazers)\n[![NPM Version](https://img.shields.io/npm/v/claudeus-wp-mcp.svg)](https://www.npmjs.com/package/claudeus-wp-mcp)\n[![NPM Downloads](https://img.shields.io/npm/dm/claudeus-wp-mcp.svg)](https://www.npmjs.com/package/claudeus-wp-mcp)\n[![MCP Standard](https://img.shields.io/badge/MCP-2024--11--05-purple.svg)](https://github.com/deus-h/claudeus-wp-mcp)\n\n![Claudeus WordPress MCP Server](https://raw.githubusercontent.com/deus-h/claudeus-wp-mcp/refs/heads/master/assets/claudeus-wp-mcp-open-graph.png)\n\n## 🌟 Unleash Your WordPress Superpowers!\n\nAre you tired of the endless grind of WordPress management? Drowning in content creation, SEO optimization, and site maintenance? Get ready to experience something that will blow your mind! 🤯\n\n### 🎸 Meet Your New WordPress Superpower 🖤\n\nClaudeus WordPress MCP isn't just another WordPress tool – it's your personal WordPress wizard, powered by cutting-edge AI and crafted with the precision of a metal guitarist's sweep picking! This isn't just automation; it's liberation! ❤️\n\n### ⚡ What Makes It Epic?\n\n- **Content Creation on Steroids**: Generate engaging, SEO-optimized blog posts ✓ READY\n- **Bulk Operations at Light Speed**: Manage hundreds of posts across multiple sites ✓ READY\n- **AI-Powered SEO Magic**: Let AI analyze and optimize your content ✓ READY\n- **WooCommerce Mastery**: Handle products, orders, and sales ✓ READY\n- **Multi-Site Orchestra**: Conduct multiple WordPress sites ✓ READY\n\n### 💥 Why Developers Are Going Crazy\n\n```\nTraditional WordPress → 😫 Hours of manual work\nClaudeus WP MCP → 🚀 INSTANT RESULTS!\n\nContent Creation: 4 hours → 30 minutes\nSEO Optimization: 2 hours → 15 minutes\nBulk Updates: 8 hours → 45 minutes\n```\n\n### 🎯 Imagine Being Able To...\n\n- Create weeks of content in minutes ✓\n- Analyze and optimize your entire site's SEO instantly ✓\n- Manage multiple client sites with supernatural efficiency ✓\n- Handle WooCommerce operations at lightning speed ✓\n- All while your competition is still logging into WordPress! ✓\n\n### 🔮 The Future of WordPress is Here\n\nThis isn't just a tool – it's your ticket to WordPress enlightenment. Whether you're a solo developer, agency owner, or WordPress enthusiast, Claudeus WordPress MCP gives you superpowers that will make your competition's jaws drop!\n\n> \"I've seen the future of WordPress management, and it's absolutely metal! 🤘❤️\" - Every Developer After Using Claudeus WP MCP\n\nReady to transform your WordPress workflow from a garage band to a stadium-filling metal symphony? Let's rock! 🎸\n\n## 📖 Quick Start Guide\n\n### Using with Claude Desktop\nIf you're using Claude Desktop, you only need to:\n1. Configure Claude Desktop integration (see \"Claude Desktop Integration\" section)\n2. Create and configure your `wp-sites.json` file\n3. Rock on! 🤘\n\n### Full Installation (for development)\n```bash\n# Required Software\nNode.js ≥ 22.0.0\nTypeScript ≥ 5.0.0\nPNPM\nWordPress site with REST API\n```\n\n### 2. Installation\n```bash\n# Clone the repository\ngit clone https://github.com/deus-h/claudeus-wp-mcp\n\n# Install dependencies\npnpm install\n\n# Build the project\npnpm build\n\n# Configure Claude Desktop\ncp claude_desktop_config.json.example claude_desktop_config.json\n# Edit claude_desktop_config.json with your settings\n```\n\n### 3. Configuration\n```bash\n# Copy example configs\ncp .env.example .env\ncp wp-sites.json.example wp-sites.json\n\n# Edit .env and wp-sites.json with your settings\n```\n\n### Configuring wp-sites.json\n\nThe `wp-sites.json` file is used to configure your WordPress sites for integration. Below is an example structure:\n\n```json\n{\n \"site-alias\": {\n \"URL\": \"https://your-wordpress-site.com\",\n \"USER\": \"username\",\n \"PASS\": \"application-password\",\n \"authType\": \"basic\" // or \"jwt\"\n }\n}\n```\n\n- **URL**: The URL of your WordPress site.\n- **USER**: The username for authentication.\n- **PASS**: The application password for secure access.\n- **authType**: The authentication type, either \"basic\" or \"jwt\".\n\n#### Obtaining the Application Password\n\n1. **Log in to your WordPress Admin Dashboard.**\n2. **Navigate to Users > Profile.**\n3. **Scroll down to the Application Passwords section.**\n4. **Enter a name for the application and click \"Add New\".**\n5. **Copy the generated password and use it in your `wp-sites.json` file.**\n\nEnsure that your `wp-sites.json` file is kept secure and not shared publicly.\n\n### Multi-Site Configuration\n\nThe `wp-sites.json` file allows you to manage multiple WordPress sites seamlessly. Here's how you can set it up:\n\n#### Example Structure\n\n```json\n{\n \"default_test\": {\n\t\t\"URL\": \"https://test.yourdomain.se\",\n\t\t\"USER\": \"admin\",\n\t\t\"PASS\": \"Hn5K pL8x Wm2j Vt9q Bc4y Rs7D\",\n\t\t\"authType\": \"basic\"\n\t},\n \"live\": {\n \"URL\": \"https://our-live-site.se\",\n \"USER\": \"deus\",\n \"PASS\": \"Kj9P mN2x vR4h Zt8L wQ5y Bc3M\",\n \"authType\": \"basic\"\n },\n \"test\": {\n \"URL\": \"https://our-test-site.se\",\n \"USER\": \"deus\",\n \"PASS\": \"Yw7H fT6n Jm5k Vd9x Pg4q Ls2B\", \n \"authType\": \"basic\"\n },\n \"client1_live\": {\n \"URL\": \"https://client1-live-site.se\",\n \"USER\": \"deus\",\n \"PASS\": \"Xc8D bN4v Ht6m Rk2p Zj9w Qf5L\",\n \"authType\": \"basic\"\n },\n \"client1_test\": {\n \"URL\": \"https://client1-test-site.se\",\n \"USER\": \"deus\",\n \"PASS\": \"Gm7B sW3x Yn5h Kt9q Vf4c Pd2L\",\n \"authType\": \"basic\"\n }\n}\n```\n\n#### Logic and Usage\n\n- **Site Aliases**: Each site is identified by a unique alias (e.g., `live`, `test`, `client1_live`). This allows you to easily switch between different environments or client sites.\n- **URL**: The base URL for each WordPress site.\n- **USER**: The username used for authentication.\n- **PASS**: The application password for secure access.\n- **authType**: Defines the authentication method, either `basic` or `jwt`.\n\n#### How to Use\n\n1. **Define Multiple Sites**: Add as many site configurations as needed, each with a unique alias.\n2. **Switch Between Sites**: Use the alias to select the desired site for operations.\n3. **Secure Access**: Ensure that each site has a valid application password and secure authentication method.\n4. **Environment Management**: Easily manage different environments (e.g., live, test) for each client.\n\nThis setup allows you to efficiently manage multiple WordPress sites from a single configuration file, streamlining your workflow and enhancing productivity.\n\n### 4. Rock and Roll with MCP Inspector! 🎸\n```bash\n# Start the MCP Inspector UI\npnpm inspector\n\n# This will:\n# 1. Build the project\n# 2. Launch the Inspector UI\n# 3. Open your browser at http://localhost:5173\n```\n\n#### Exploring with Inspector UI\n1. **Connect to Server**\n - Click \"Connect\" in the top-right corner\n - Select \"Local Server\" for development\n\n2. **Available Features**\n - 🎸 Prompts: Test AI content generation\n - 🛠 Tools: Manage WordPress operations\n - 📦 Resources: Browse WordPress sites\n - 🔍 Inspector: Debug server communication\n\n3. **Testing Prompts**\n - Select \"Prompts\" tab\n - Try `create-blog-post` with your ideas\n - Analyze SEO with `analyze-post-seo`\n - Bulk update with `bulk-update-posts`\n\n4. **Managing Resources**\n - Browse connected WordPress sites\n - View site details and capabilities\n - Test API endpoints directly\n\n5. **Using Tools**\n - Create and update content\n - Manage media files\n - Run bulk operations\n\n> 🤘 Pro Tip: Use the Inspector tab to see real-time communication between the UI and server!\n\n## 🎮 Claude Desktop Integration\n\n### Configuration Location\nThe Claude Desktop configuration file can be found at:\n- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`\n- Windows: `%APPDATA%\\Claude\\claude_desktop_config.json`\n\n⚠️ **IMPORTANT**: If you already have other MCP servers configured in Claude Desktop, DO NOT directly copy our example file as it will overwrite your existing configuration! Instead:\n\n1. **For existing Claude Desktop users**:\n - Open your existing config through Claude Desktop:\n - Click on the Claude menu\n - Select \"Settings...\"\n - Click on \"Developer\" in the lefthand bar\n - Click on \"Edit Config\"\n - OR open your config file directly in a text editor\n - Add our Claudeus WordPress MCP server configuration to your existing `mcpServers` object\n\n2. **For new Claude Desktop users**:\n You can copy our example config file:\n ```bash\n # For macOS\n cp /Users/amadeus/code/claudeus/servers/claudeus-wp-mcp/claude_desktop_config.json.example ~/Library/Application\\ Support/Claude/claude_desktop_config.json\n\n # For Windows (in PowerShell)\n Copy-Item claude_desktop_config.json.example $env:APPDATA\\Claude\\claude_desktop_config.json\n ```\n\n> 🎸 Pro Tip: Our example config file comes pre-configured with the optimal settings - just update the path to your `wp-sites.json`!\n\n### Usage with Claude Desktop\n\nAdd this to your `claude_desktop_config.json`:\n\n#### NPX Setup\n```json\n{\n \"mcpServers\": {\n \"claudeus-wp-mcp\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"claudeus-wp-mcp\"\n ],\n \"env\": {\n \"WP_SITES_PATH\": \"/absolute/path/to/your/wp-sites.json\"\n }\n }\n }\n}\n```\n\n#### Docker Setup 🐳\n```json\n{\n \"mcpServers\": {\n \"claudeus-wp-mcp\": {\n \"command\": \"docker\",\n \"args\": [\n \"run\",\n \"-i\",\n \"--rm\",\n \"--network=host\",\n \"--mount\", \"type=bind,src=/absolute/path/to/your/wp-sites.json,dst=/app/wp-sites.json\",\n \"--mount\", \"type=bind,src=/absolute/path/to/your/.env,dst=/app/.env\",\n \"mcp/wordpress\",\n \"--config\", \"/app/wp-sites.json\"\n ]\n }\n }\n}\n```\n\n> 🎸 Pro Tip: Make sure to replace `/absolute/path/to/your/wp-sites.json` with the actual path to your configuration file!\n\n### After Configuration\n1. Restart Claude Desktop completely\n2. Look for the hammer 🔨 icon in the bottom right corner of the input box\n3. Click it to see available WordPress management tools\n4. Start shredding! 🤘\n\n### Troubleshooting\nIf the server isn't showing up in Claude:\n1. Verify your `claude_desktop_config.json` syntax\n2. Ensure file paths are absolute and valid\n3. Check Claude's logs at:\n - macOS: `~/Library/Logs/Claude`\n - Windows: `%APPDATA%\\Claude\\logs`\n\n## 🎯 What is This?\n\nClaudeus WordPress MCP is your ultimate AI-powered WordPress management system. It's like having a metal band's precision and power, but for your WordPress sites!\n\n| Feature | Description |\n|---------|-------------|\n| 🤖 AI Integration | Direct communication with AI models |\n| 🚀 Automation | Automate repetitive tasks |\n| 🔒 Security | Enterprise-grade security |\n| ⚡ Performance | Lightning-fast operations |\n| 🌐 Multi-site | Manage multiple WP instances |\n\n## 💪 Core Features\n\n### 1. Content Management\n| Feature | Description |\n|---------|-------------|\n| Posts | Create, update, analyze |\n| Pages | Full page management |\n| Media | Handle all media types |\n| SEO | AI-powered optimization |\n\n### 2. AI Capabilities\n| Feature | Description |\n|---------|-------------|\n| Content Generation | AI-written posts |\n| SEO Analysis | Smart optimization |\n| Bulk Operations | Mass updates |\n\n## 🛠 Technical Deep Dive\n\n### Architecture 🏗️\nWelcome to the backstage of our metal symphony! Each component is like an instrument in our technical orchestra, working together to create the most epic WordPress management system ever! 🤘🖤\n\n#### Directory Structure 🎸\n```typescript\nsrc/\n├── api/ # WordPress API integration layer\n│ ├── client/ # WordPress REST API client\n│ ├── endpoints/ # Endpoint definitions & handlers\n│ └── types/ # WordPress API type definitions\n│\n├── mcp/ # MCP protocol implementation\n│ ├── server.ts # Core MCP server implementation\n│ ├── transport/ # Transport layer handlers\n│ ├── tools.ts # Tool registration & management\n│ └── types/ # MCP protocol type definitions\n│\n├── security/ # Security framework\n│ ├── auth/ # Authentication handlers\n│ ├── validation/ # Input validation\n│ └── encryption/ # Data encryption utilities\n│\n├── tools/ # Tool implementations\n│ ├── content/ # Content management tools\n│ ├── media/ # Media handling tools\n│ ├── shop/ # WooCommerce integration\n│ └── system/ # System management tools\n│\n└── prompts/ # AI prompt templates\n ├── content/ # Content generation prompts\n ├── seo/ # SEO analysis prompts\n └── shop/ # E-commerce prompts\n```\n\n#### Core Components 🤘\n\n| Component | Responsibility | Key Features |\n|-----------|---------------|--------------|\n| **API Layer** | WordPress Integration | REST client, Type safety, Rate limiting |\n| **MCP Protocol** | Communication | JSON-RPC 2.0, Bi-directional flow |\n| **Security** | Protection | Auth, Encryption, Validation |\n| **Tools** | Operations | Content, Media, WooCommerce |\n| **Prompts** | AI Integration | Templates, Context awareness |\n\n#### Technical Amplification 🎸\n\n| Feature | Implementation | Description |\n|---------|---------------|-------------|\n| **Type Safety** | TypeScript | Full static typing, Runtime validation |\n| **API Handling** | REST/JSON-RPC | Efficient request/response handling |\n| **Event System** | EventEmitter | Async event processing |\n| **Error Handling** | Multi-layer | Comprehensive error management |\n| **Caching** | In-memory/Redis | Performance optimization |\n\n#### Security Measures 🛡️\n\n| Layer | Protection | Features |\n|-------|------------|-----------|\n| **Transport** | TLS/SSL | Encrypted communication |\n| **Authentication** | JWT/OAuth | Secure token management |\n| **Validation** | Schema-based | Input/Output validation |\n| **Encryption** | AES-256 | Data protection |\n| **Audit** | Comprehensive | Activity tracking |\n\n#### Performance Tuning 🚀\n\n| Optimization | Technique | Description |\n|-------------|-----------|-------------|\n| **Caching** | Multi-level | Response & Query caching |\n| **Batching** | Request grouping | Reduced API calls |\n| **Compression** | GZIP/Brotli | Network optimization |\n| **Query Optimization** | Smart fetching | Efficient DB queries |\n| **Load Balancing** | Distribution | Scale handling |\n\n#### Error Categories & Handling 🎸\n\n| Category | Code Range | Handling | Example |\n|----------|------------|----------|---------|\n| **Protocol** | -32600 to -32603 | Auto-retry | Invalid JSON-RPC |\n| **WordPress** | 1000-1999 | Fallback | API timeout |\n| **Security** | 2000-2999 | Alert | Auth failure |\n| **Tools** | 3000-3999 | Recover | Operation fail |\n| **System** | 4000-4999 | Restart | Resource exhaustion |\n\n#### Design Principles Power Chord 🤘\n\n| Principle | Description | Implementation |\n|-----------|-------------|----------------|\n| **Modularity** | Loose coupling | Independent components |\n| **Type Safety** | Strong typing | TypeScript + Validation |\n| **Security** | Zero trust | Multi-layer protection |\n| **Performance** | Speed metal | Optimized operations |\n\n> 🎸 Pro Tip: Like a well-tuned guitar, each component is precisely calibrated for maximum shredding capability! ❤️\n\n## 🎸 The Power of MCP\n\n### Time Savings\n| Task | Without MCP | With MCP | Result |\n|------|-------------|----------|---------|\n| Blog Post Creation | 4 hours | 4 mins | ✓ 98.3% |\n| SEO Optimization | 2 hours | 1 min | ✓ 99.2% |\n| Bulk Updates | 8 hours | 5 mins | ✓ 99.0% |\n| Content Analysis | 3 hours | 2 mins | ✓ 98.9% |\n\n### Cost Efficiency\n| Resource | Traditional Cost | Description |\n|----------|-----------------|-------------|\n| Content Writer | $500/month | Professional content creation |\n| SEO Expert | $1000/month | SEO optimization & strategy |\n| Developer Time | $2000/month | Technical implementation |\n| **TOTAL** | **$3500/month** | All services combined |\n| | | |\n| **Claude Pro** | **$20/month** | At [Anthropic](https://claude.ai/settings/billing?action=subscribe) |\n| | | |\n| **Difference** | **$3,480/month** | Potential Savings using **Claudeus WordPress MCP**
with Claude Desktop ([Mac](https://storage.googleapis.com/osprey-downloads-c02f6a0d-347c-492b-a752-3e0651722e97/nest/Claude.dmg), [Windows](https://storage.googleapis.com/osprey-downloads-c02f6a0d-347c-492b-a752-3e0651722e97/nest-win-x64/Claude-Setup-x64.exe)) |\n| | | |\n\n**Claudeus Solution**: All these capabilities for just **$20/month** with Claude Pro subscription\n\nTotal Monthly Savings: **$3,480 (99.4% reduction)** ❤️\n\n> 🎸 Pro Tip: One Claude Pro subscription replaces multiple expensive services, turning your WordPress management from a costly orchestra into a lean, mean, Metal Machine! 🤘\n\n## ⚡ With Great Power...\n\n> \"With great power comes great responsibility\" - Uncle Ben\n\nThe Claudeus WordPress MCP is a powerful tool that can:\n- Save hundreds of hours of manual work\n- Reduce operational costs by up to 85%\n- Improve content quality and consistency\n- Automate repetitive tasks\n\nBut remember:\n1. Always review AI-generated content\n2. Keep security best practices in mind\n3. Monitor system usage and performance\n4. Maintain backup strategies\n5. Use the power responsibly! 🤘\n\n## ⚠️ Issues and Considerations\n\n### Current Limitations and Workarounds\n\n#### 1. Claude Desktop Response Limits\n- **Issue**: Claude Desktop's maximum response length can be reached frequently during complex operations\n- **Impact**: Operations may be interrupted, requiring user intervention to continue\n- **Workaround**: \n - Configure Claude Desktop to break tasks into smaller batches\n - In Claude Desktop Settings > Advanced:\n - Set \"Maximum Response Length\" to a lower value\n - Enable \"Auto-split Responses\"\n - Use the Inspector UI for large-scale operations\n\n#### 2. Experimental Capabilities Control\n- **Issue**: The new capability control feature in `wp-sites.json` is experimental\n- **Status**: Integrated but under testing\n- **Example Configuration**:\n```json\n{\n \"capabilities\": {\n \"discovery\": {\n \"claudeus_wp_discover_endpoints\": true\n },\n \"posts\": {\n \"claudeus_wp_content__get_posts\": true,\n \"claudeus_wp_content__create_post\": true,\n \"claudeus_wp_content__update_post\": true,\n \"claudeus_wp_content__delete_post\": false\n }\n // ... other capabilities\n }\n}\n```\n- **Considerations**:\n - Use with caution in production environments\n - Test thoroughly in staging first\n - Consider contributing improvements (see Contributing section)\n - Default to basic configuration if unsure\n\n#### 3. Rate Limiting Considerations\n- **Issue**: WordPress REST API has rate limits\n- **Impact**: Bulk operations might be throttled\n- **Mitigation**: \n - Use batch processing features\n - Implement appropriate delays between requests\n - Monitor API response headers for rate limit info\n\n#### 4. Memory Management\n- **Issue**: Large operations can consume significant memory\n- **Impact**: Potential performance degradation\n- **Best Practices**:\n - Monitor system resources during large operations\n - Use pagination for large datasets\n - Implement cleanup routines\n\n### Future Improvements\nWe're actively working on:\n1. Improved response handling in Claude Desktop\n2. Stable release of capabilities control\n3. Advanced rate limiting management\n4. Memory optimization techniques\n\n\n## 🎸 Support and Community ❤️\n\n- GitHub Discussions: Share ideas, report issues, and join the conversation\n- Documentation: Full technical docs\n- Examples: Sample implementations\n\n> 🎸 Pro Tip: Use GitHub Discussions to share your experience, report issues, or suggest improvements!\n\n## 🏗️ MCP Server Development Standards\n\n### Setting the Bar for Excellence\n\nClaudeus WordPress MCP isn't just compliant with MCP standards - it defines them. Our implementation serves as a reference for developers building MCP servers, especially for Claude Desktop integration:\n\n### MCP Protocol Compliance\n- ✅ **Full MCP 2024-11-05 Spec Implementation**\n - Complete capability declarations\n - Strict message format adherence\n - Proper transport handling (stdio/SSE)\n - Comprehensive error handling\n\n### Development Excellence\n- ✅ **TypeScript Best Practices**\n - Strict mode enabled\n - Complete type coverage\n - Interface-driven development\n- ✅ **Testing Standards**\n - 95%+ test coverage\n - Comprehensive integration tests\n - Performance benchmarking\n- ✅ **Security First**\n - Input validation\n - Rate limiting\n - Authentication flows\n - Vulnerability scanning\n\n## 🧪 Testing Framework\n\nOur testing framework is built with precision and reliability in mind, just like a well-tuned guitar! 🎸\n\n### Test Structure\n- **Unit Tests**: Comprehensive testing of individual components\n- **Integration Tests**: Ensuring components work together harmoniously\n- **JSON-RPC Protocol Testing**: Validating server-client communication\n- **Custom Test Harness**: Simulating real-world scenarios\n\n### Key Features\n- **Custom Matchers**: Enhanced Jest matchers for JSON-RPC validation\n- **Test Transport Layer**: Simulated transport for controlled testing\n- **Async Operation Support**: Extended timeouts for complex operations\n- **Error Handling Tests**: Comprehensive error scenario coverage\n\n### Running Tests\n```bash\n# Run all tests\npnpm test\n\n# Run specific test suite\npnpm test:unit\npnpm test:integration\n\n# Run with coverage\npnpm test:coverage\n```\n\n## 🤝 Contributing\n\n⚠️ **PRIVATE TEAM NOTICE** ⚠️\n\nThis is a private repository maintained by the SimHop IT & Media AB development team. Contributions are limited to approved team members only. If you've been granted membership to the SimHop MCP Development Team, here's how to contribute:\n\n### For Approved Team Members\n\n1. ✓ Ensure you have the necessary repository access\n2. ✓ Follow our development workflow:\n - Create your feature branch (`git checkout -b feature/AmazingFeature`)\n - Write and run tests for your changes\n - Maintain test coverage above 80%\n - Follow our coding standards and documentation requirements\n3. ✓ Testing Requirements:\n - Ensure all existing tests pass\n - Add new tests for your features\n - Run the full test suite before submitting\n4. ✓ Commit your changes (`git commit -m '🎸 Add some AmazingFeature'`)\n5. ✓ Push to the branch (`git push origin feature/AmazingFeature`)\n6. ✓ Create a Pull Request for review\n\n### Development Standards\n\nAll team members must adhere to:\n- TypeScript strict mode\n- ESLint configuration with team rules\n- Prettier for consistent formatting\n- JSDoc documentation for public APIs\n- Team security protocols\n- Internal code review processes\n\n### Getting Team Access\n\nIf you're interested in joining the SimHop MCP Development Team:\n1. Contact our CTO: amadeus.hritani@simhop.se\n2. Provide your development background and expertise\n3. Complete the team onboarding process if approved\n\n> 🔥 Pro Tip: Team members should always run the test suite before submitting a PR!\n\n## 🤘 License\n\nMIT License - Rock on! \n\n## 🛠 MCP Tools Reference\n\n### Tool Categories and Danger Levels\n| Tool Name | Category | Capabilities | Danger Level |\n|-----------|----------|--------------|--------------|\n| **Content Management** ||||\n| `claudeus_wp_content__get_posts` | Content | List all posts with filters | 🟢 Safe |\n| `claudeus_wp_content__create_post` | Content | Create new blog posts | 🟡 Moderate |\n| `claudeus_wp_content__update_post` | Content | Modify existing posts | 🟡 Moderate |\n| `claudeus_wp_content__delete_post` | Content | Remove posts | 🔴 High |\n| `claudeus_wp_content__get_pages` | Content | List all pages | 🟢 Safe |\n| `claudeus_wp_content__create_page` | Content | Create new pages | 🟡 Moderate |\n| `claudeus_wp_content__update_page` | Content | Modify existing pages | 🟡 Moderate |\n| `claudeus_wp_content__delete_page` | Content | Remove pages | 🔴 High |\n| `claudeus_wp_content__get_blocks` | Content | List reusable blocks | 🟢 Safe |\n| `claudeus_wp_content__create_block` | Content | Create reusable blocks | 🟡 Moderate |\n| `claudeus_wp_content__update_block` | Content | Modify blocks | 🟡 Moderate |\n| `claudeus_wp_content__delete_block` | Content | Remove blocks | 🔴 High |\n| **Media Management** ||||\n| `claudeus_wp_media__get_media` | Media | List media files | 🟢 Safe |\n| `claudeus_wp_media__upload` | Media | Upload new media | 🟡 Moderate |\n| `claudeus_wp_media__update` | Media | Update media metadata | 🟡 Moderate |\n| `claudeus_wp_media__delete` | Media | Remove media files | 🔴 High |\n| **Theme Management** ||||\n| `claudeus_wp_theme__list` | Theme | List available themes | 🟢 Safe |\n| `claudeus_wp_theme__get_active` | Theme | Show current theme | 🟢 Safe |\n| `claudeus_wp_theme__activate` | Theme | Switch active theme | 🔴 High |\n| `claudeus_wp_theme__get_customization` | Theme | View theme settings | 🟢 Safe |\n| `claudeus_wp_theme__update_customization` | Theme | Modify theme settings | 🟡 Moderate |\n| `claudeus_wp_theme__get_custom_css` | Theme | View custom CSS | 🟢 Safe |\n| `claudeus_wp_theme__update_custom_css` | Theme | Modify custom CSS | 🟡 Moderate |\n| **WooCommerce** ||||\n| `claudeus_wp_shop__get_products` | Shop | List products | 🟢 Safe |\n| `claudeus_wp_shop__get_orders` | Shop | View orders | 🟢 Safe |\n| `claudeus_wp_shop__get_sales` | Shop | Access sales stats | 🟢 Safe |\n| **System** ||||\n| `claudeus_wp_discover_endpoints` | System | List available endpoints | 🟢 Safe |\n\n### Danger Level Legend\n- 🟢 **Safe**: Read-only operations, no data modification\n- 🟡 **Moderate**: Creates or modifies content, but can be reverted\n- 🔴 **High**: Destructive operations or system-wide changes\n\n> 🤘 Pro Tip: Always test high-danger tools in a staging environment first!\n\n## ⚠️ Warning: Use Data Manipulation Tools with Caution\n\nData manipulation tools in the Claudeus WordPress MCP are powerful and can significantly impact your WordPress sites. Here's what you need to know:\n\n### Potential Risks\n\n- **Data Loss**: Incorrect use of tools can lead to unintended data deletion or modification.\n- **Site Downtime**: Misconfigurations may cause site outages or performance issues.\n- **Security Vulnerabilities**: Improper handling of sensitive data can expose your site to security risks.\n\n### Best Practices\n\n1. **✓ SAFETY FIRST**: Always create backups before operations\n2. **✓ TEST SAFE**: Use staging environment for new tools\n3. **✓ VERIFY**: Review changes before applying\n4. **✓ SECURE**: Restrict tool access to trusted users\n5. **✓ MONITOR**: Track tool usage and performance\n\n### Constructive Use\n\nWhen used correctly, these tools can:\n- ✓ Automate repetitive tasks\n- ✓ Enhance site performance\n- ✓ Improve content quality\n\n> \"With great power comes great responsibility.\" Use these tools wisely to harness their full potential while minimizing risks.\n\n### Data Manipulation Tools\n\nThe following tools can create, update, or delete data on your WordPress site:\n\n#### Content Management\n- **Posts**:\n - `claudeus_wp_content__create_post`: Create new blog posts\n - `claudeus_wp_content__update_post`: Update existing posts\n - `claudeus_wp_content__delete_post`: Delete posts\n- **Pages**:\n - `claudeus_wp_content__create_page`: Create new pages\n - `claudeus_wp_content__update_page`: Update existing pages\n - `claudeus_wp_content__delete_page`: Delete pages\n- **Blocks**:\n - `claudeus_wp_content__create_block`: Create reusable blocks\n - `claudeus_wp_content__update_block`: Update existing blocks\n - `claudeus_wp_content__delete_block`: Delete blocks\n\n#### Media Management\n- `claudeus_wp_media__upload`: Upload new media files\n- `claudeus_wp_media__update`: Update media metadata\n- `claudeus_wp_media__delete`: Delete media items\n\n#### Theme Customization\n- `claudeus_wp_theme__activate`: Change active theme\n- `claudeus_wp_theme__update_customization`: Modify theme settings\n- `claudeus_wp_theme__update_custom_css`: Update custom CSS\n\nUse these tools with caution to avoid unintended changes. Always:\n1. Back up your data before making changes\n2. Test in a staging environment first\n3. Review changes before applying them\n4. Monitor the results after application\n\n> \"With great power comes great responsibility.\" Use these tools wisely to enhance your WordPress site while maintaining its integrity.\n\n## 🎯 Our Mission: Elevating MCP Development Standards\n\nIn the rapidly evolving landscape of AI-powered development, we observed a critical gap: many MCP servers, especially those designed for Claude Desktop, were falling short of professional development standards. Common issues included:\n\n- 🔴 Poor TypeScript implementation or complete lack of type safety\n- 🔴 Missing or inadequate test coverage\n- 🔴 Incomplete MCP protocol implementation\n- 🔴 Security vulnerabilities\n- 🔴 Unreliable error handling\n- 🔴 Lack of proper documentation\n\nThis motivated us to create Claudeus WordPress MCP - not just as another WordPress management tool, but as a reference implementation that demonstrates:\n\n- ✅ Complete TypeScript coverage with strict type checking\n- ✅ Comprehensive test suite (95%+ coverage)\n- ✅ Full MCP 2024-11-05 specification compliance\n- ✅ Enterprise-grade security practices\n- ✅ Robust error handling and recovery\n- ✅ Detailed documentation and examples\n\n### Why We're Setting the Standard\n\nWhile this remains a private repository, we've made the code available for viewing to:\n1. Demonstrate professional MCP server development practices\n2. Encourage better standards in the MCP ecosystem\n3. Show how to properly implement Claude Desktop integration\n4. Provide a reference for secure WordPress automation\n\n## 🏢 The Team Behind the Magic\n\n### SimHop IT & Media AB - Where Innovation Meets Metal 🤘\n\nBased in the heart of Sweden, SimHop IT & Media AB is the powerhouse behind Claudeus WordPress MCP. We're not your typical tech company - we're a fusion of technical excellence and creative innovation, orchestrating digital solutions that rock! \n\n#### 🎸 The Maestros\n\n**Amadeus Samiel H. (CTO/Lead Solutions Architect)**\n- MSc in Computer Science\n- 20+ years crafting digital excellence\n- Instructor at LIU and other institutes\n- The technical virtuoso behind Claudeus WP MCP\n- Specializations: System Architecture, Creative Development, Technical Education\n\n**Simon Malki (CEO)**\n- 20+ years orchestrating business success\n- Expert in strategic planning and market dynamics\n- The business mastermind driving SimHop's vision\n- Specializations: Business Strategy, Market Analysis, Technical Operations\n\n#### 🏗️ Our Dual-Power Structure\n\n**Stockholm HQ (Business & Strategy)**\n📍 Krögers Promenad 11, 191 37 Sollentuna\n- Strategic Operations\n- Business Development\n- Market Strategy\n- Client Relations\n\n**Norrköping Division (Technical Innovation)**\n📍 Klingsbergsgatan 13, 603 54 Norrköping\n- Development & Architecture\n- Technical Innovation\n- R&D Operations\n\n### 🤘 Why We Made It Free\n\nClaudeus WordPress MCP was born from our passion for both heavy metal and heavy-duty WordPress development, but it represents something even more important: our commitment to elevating the standards of MCP server development. We observed that many existing MCP servers, especially those designed for Claude Desktop, were falling short of professional standards - lacking proper testing, type safety, and security measures.\n\nBy making our code available for viewing, we're not just sharing a tool - we're setting a new standard for MCP server development. Just as metal music pushes the boundaries of musical excellence, we're pushing the boundaries of what a properly implemented MCP server should be:\n\n- **Technical Excellence**: Like a perfectly executed guitar solo, our code demonstrates pristine TypeScript implementation\n- **Comprehensive Testing**: Every riff (function) is tested, every solo (feature) is verified\n- **Security First**: Protected like a fortress of metal, with proper authentication and validation\n- **Documentation**: Clear and detailed, like the best metal lyrics\n\nWhile this remains a private repository, making the code viewable helps other developers understand how to properly implement MCP servers, especially for Claude Desktop integration. It's our way of saying \"this is how it's done!\" 🎸\n\n### 🔥 Our Philosophy\n\n1. **Technical Excellence**: Setting the standard for MCP development\n2. **Creative Innovation**: Breaking boundaries while maintaining stability\n3. **Security First**: Enterprise-grade protection by default\n4. **Continuous Evolution**: Always pushing the technical boundaries\n\n> \"We believe in empowering developers with tools that rock as hard as they do, while showing them how it should be done!\" - Amadeus Samiel H. (aka Deus)\n\n---\n## 🧙‍♂️ Words of Wisdom\n\n> `npm` is not a package manager, it's a repository of packages. If you want a dependable package manager, always use `pnpm` \n> — Amadeus Samiel H.\n\n---\n\n### The Package Manager's Anthem\n#### *by Amadeus & Claude*\n---\n*In code's vast land, \nnpm stands, a host, \nBut pnpm's hand, \nManages most.*\n\n*With iron might, \nDependencies align, \npnpm's light, \nIn code, it shines.*\n\n*A true manager's call, \nIn the coder's hall, \npnpm reigns, \nAbove them all.* \n\n\n---\n\n\n> Made with 🤘❤️ by [Amadeus Samiel H.](mailto:amadeus.hritani@simhop.se)\n","url","https://github.com/deus-h/claudeus-wp-mcp","githubRepository",{"_94":95,"_96":97,"_98":99,"_100":101,"_102":103,"_107":108,"_109":-5,"_110":111},"defaultBranch","master","fullName","deus-h/claudeus-wp-mcp","githubTreeId",48786,"language","TypeScript","owner",{"_104":105,"_106":31},"login","deus-h","verified","recentStargazers",1,"spdxLicense","stargazers",3,"id",672,"inspectable","name","Claudeus WordPress MCP","npmPackage",{"_115":119,"_120":121},"claudeus-wp-mcp","weeklyDownloads",12,"prompts","relatedMcpServerIds",[125,126,127,128,129,130],453,503,413,501,637,631,"resources","scores",{"_134":135,"_136":-5,"_137":-5},"license",0,"quality","security","simpleIcon","supportedPlatforms",[141,142],"MACOS","WINDOWS","tools","wrpd2x7eei","updatedAt",["D",1740207672154],"meta",[149,152,154,161,164,166,169,172,175,178,181,183,186,189,191,193,195,197,199],{"_150":151},"title","Claudeus WordPress MCP | Glama",{"_153":84,"_115":76},"content",{"_155":156,"_157":158,"_159":160},"href","https://glama.ai/mcp/servers/wrpd2x7eei","rel","canonical","tagName","link",{"_153":116,"_162":163},"property","og:title",{"_153":84,"_162":165},"og:description",{"_153":167,"_162":168},"https://glama.ai/logo.png","og:logo",{"_153":170,"_162":171},"https://glama.ai/mcp/servers/wrpd2x7eei/og-image","og:image",{"_153":173,"_162":174},"630","og:image:height",{"_153":176,"_162":177},"1200","og:image:width",{"_153":179,"_162":180},"website","og:type",{"_153":156,"_162":182},"og:url",{"_153":184,"_162":185},"ChatGPT alternative for power users","og:site_name",{"_153":187,"_115":188},"summary_large_image","twitter:card",{"_153":184,"_115":190},"twitter:title",{"_153":84,"_115":192},"twitter:description",{"_153":170,"_115":194},"twitter:image",{"_153":173,"_115":196},"twitter:image:height",{"_153":176,"_115":198},"twitter:image:width",{"_200":201},"script:ld+json",{"_202":203,"_204":205},"@context","http://schema.org","@graph",[206],{"_202":207,"_208":209,"_210":211},"https://schema.org","@type","BreadcrumbList","itemListElement",[212,218,222,225],{"_208":213,"_214":215,"_115":216,"_217":108},"ListItem","item","https://glama.ai/","Glama","position",{"_208":213,"_214":219,"_115":220,"_217":221},"https://glama.ai/mcp","MCP",2,{"_208":213,"_214":223,"_115":224,"_217":111},"https://glama.ai/mcp/servers","Servers",{"_208":213,"_214":156,"_115":116,"_217":226},4,"routes/_public/mcp/servers/~uid/_pages/_explorer/blob/~branch/~/_route",{"_229":230,"_234":95,"_58":235,"_251":252,"_253":254},"blob",{"_153":231,"_232":233},"This is a sample text file.\nIt contains multiple lines of text\nthat we can use for testing our context-aware LLM queries.\n\nThe purpose of this file is to demonstrate\nhow our system handles plain text files.","fileName","sample.txt","branch",{"_60":236,"_62":237,"_42":242,"_83":84,"_85":84,"_86":243,"_92":244,"_112":113,"_114":31,"_115":116,"_117":246,"_122":-5,"_123":247,"_131":-5,"_132":248,"_138":-5,"_139":249,"_143":-5,"_46":144,"_145":250},["D",1737190845461],{"_64":65,"_66":238,"_69":239},[68],{"_71":240,"_68":241},{"_64":73,"_74":75,"_76":77},{"_64":73,"_76":79},[81,82],{"_88":89,"_90":91},{"_94":95,"_96":97,"_98":99,"_100":101,"_102":245,"_107":108,"_109":-5,"_110":111},{"_104":105,"_106":31},{"_115":119,"_120":121},[125,126,127,128,129,130],{"_134":135,"_136":-5,"_137":-5},[141,142],["D",1740207672154],"path","storage","treeMembers",[255,258,260,262],{"_251":256,"_64":257},"storage/code-samples","tree",{"_251":259,"_64":257},"storage/notes",{"_251":261,"_64":229},"storage/config-example.json",{"_251":263,"_64":229},"storage/sample.txt","actionData","errors"]