wattpad-mcp
Related Servers
Alternatives to wattpad-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables Claude Code to read, edit, and manage WordPress pages, posts, shortcodes, and media via the WordPress REST API.8011 npm3MIT
- AlicenseAqualityCmaintenanceEnables direct interaction with WordPress sites via Claude using the REST API, allowing reading, creating, updating, and deleting content securely with application passwords.20MIT
- FlicenseAqualityCmaintenanceEnables Claude to read context, create, and edit pages on WordPress sites via the REST API using Application Passwords.6-
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to directly manage WordPress sites via natural language, including posts, pages, categories, tags, media, and multiple site support.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to read Google Docs and their comment threads, then write corrections and replies back into the same document at the same URL.26 npmMIT
- AlicenseNot gradedqualityDmaintenanceConnects your WordPress.com account to Claude Desktop, enabling you to read your feed, check notifications, manage tags and follows, and discover new blogs through natural conversation.3 npm8MIT
TDQS
Scored across 15 tools
Each tool maps to a clear resource+action: user, story, part, comments, session, stats, markup preview, and backup. Although backup_part and get_part_text both read chapter content, their outputs and purposes are distinct enough that an agent should not confuse them.
All tools follow the wattpad_<verb>_<noun> snake_case pattern, e.g. get_part_text, create_story, update_part, publish_part. wattpad_whoami is a minor idiomatic exception but still fits the consistent snake_case style.
Fifteen tools is at the upper edge of the ideal range but each covers a distinct part of the Wattpad reading/writing workflow: auth, search, story/part CRUD, comments, stats, backup, and markup validation. No tool feels redundant.
The set covers the core workflow: session check, search, list/create/get stories, create/read/update/publish parts, comments, stats, and a safety backup. The main gaps are the absence of story update/delete operations and no way to delete/unpublish a part, but agents can complete the primary write-and-publish loop.