shapeless
Related Servers
Alternatives to shapeless
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceExposes 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.AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to plan, schedule, publish, and analyze Instagram and Facebook posts, upload local media, and read or write articles via a self-hosted openContent MCP backend. It runs locally as a stdio bridge and passes through all remote tools while adding a local file-upload tool.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to discover and create agents, durably submit messages with verifiable replies, and search source-linked local memory. Exposes eight authenticated tools with owner-approved OAuth, transcript-backed verification, and explicit control over history import and embedding.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI assistants to read a workspace, upload media, and create, schedule and publish branded short videos, slideshows and images to connected social accounts. Also lets assistants review plans, post status and performance data over a chosen time window.30 npmMIT
- AlicenseNot gradedqualityCmaintenanceSocial media API and MCP server for AI agents that enables publishing to X, Instagram, LinkedIn, Reddit, Bluesky, and Threads from a single endpoint.8 npmMIT

@fopost/mcpofficial
AlicenseAqualityBmaintenanceEnables managing social media posts, accounts, and AI-powered content features from any MCP client, including scheduling, publishing, analysis, and AI caption generation.1412 npmMIT
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.