shapeless
Related Servers
Alternatives to shapeless
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceExposes a governed brand brain to any MCP-compatible agent over stdio or an OAuth 2.1-protected Streamable HTTP endpoint, letting agents read brand context (mission, voice, guidelines, personas, policy) and create or edit drafts, campaigns, records and connector jobs. Approving and publishing stay with a human operator.684 PyPIAGPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to schedule, publish, update, retry, and inspect social media posts across connected platforms, while managing profiles, queues, media uploads, analytics, and webhooks. It runs locally over stdio with an API key and exposes the same tools as the hosted endpoint.MIT
- AlicenseBqualityBmaintenanceEnables MCP clients such as Claude and Cursor to read timelines, search statuses, and look up users or conversations, plus optionally post, delete, favorite, and follow with explicit confirmation. It supports both local stdio launches and remote HTTP hosting with per-user authorization.15MIT

RepeatPost MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables Claude or any MCP client to schedule and publish social media posts across 15 platforms, write brand-voice captions, create branded graphics, and manage media and workspaces through a hosted remote server.MIT- AlicenseNot gradedqualityCmaintenanceConnects MCP clients to a local social engine that reads bounded posts, comments, replies, and feeds into local inboxes, turns source material into drafts and briefs, and publishes exact frozen jobs with recorded provider IDs and receipts across Instagram, Threads, and Substack.MIT
- AlicenseNot gradedqualityBmaintenanceEnables keyword, user, and expert social-media searches with post retrieval, topic-tree access, agent run and schedule management, integration setup, and account usage checks through a stdio MCP interface.MIT
TDQS
Scored across 65 tools
Most tools have distinct resource+action targets, but the search/pulse family (web_search, news_search, concept_search, x_pulse, current_pulse, related_trends, community_hot, find_evidence, reference_search) overlaps heavily in purpose, and brain_*/jobs_* clusters have several near-neighbors (jobs_get vs jobs_brief vs jobs_tail). The rich descriptions help distinguish them, but an agent could easily misselect among the many semantic-search variants.
Nearly everything is snake_case with two systematic patterns: resource_verb for scoped operations (posts_create, brain_read, jobs_get, characters_voice) and verb_noun for generic actions (generate_image, find_photo, edit_footage, render_carousel). Minor outliers like 'me', 'speak' and 'plan_music' break the pattern slightly, but the convention is largely predictable.
65 tools is a very heavy surface, well past the point where an agent can hold the catalog in mind. Given the platform's breadth (generation, search, publishing, Brand Memory, jobs, agents) many tools do earn their place, but the count still demands excessive selection effort.
The surface covers full lifecycles across every domain: posts (list/get/create/approve/dismiss/publish), jobs (create/list/get/brief/tail/continue/run/stop), Brand Memory (read/write/tree/import/onboarding), agents and media assets, plus generation, editing, transcription and rich search. No obvious dead ends.