ShapelessAI
com.shapelessaiPublished by shapelessai.comOfficial publisherv0.3.5Updated Nov 13, 2026
AI social media team for founders: posts and short video to LinkedIn, X, Instagram, TikTok and more.
Overview
ShapelessAI is a hosted social media team for founders: an assistant can draft, schedule and publish posts and short video to connected platforms.
- What you can do
- Create, schedule, queue, approve, publish and dismiss posts across connected social accounts, with media, titles and first comments
- List connected accounts and platform limits, media rules and settings schemas
- Run durable jobs that keep working server-side, then list, brief, tail, continue or stop them, with file attachments
- Manage standing agents that post on a schedule, and read or edit Brand Memory and account assets
- Generate images, footage, carousels, speech and captions, and search the web, returning media keys usable in posts
- When to use it
- Use it when you want an assistant to run a founder's or small team's social presence end to end: drafting and scheduling a week of posts, keeping a queue approved and published, or letting standing agents keep posting while you are away.
- Requirements
- Remote MCP endpoint over streamable HTTP with OAuth sign-in in a browser; non-browser clients send an API key from Settings -> API keys as an Authorization Bearer header. A ShapelessAI account is required, with key scopes read, write or publish. A local stdio variant runs via npx on Node 20 or newer with SHAPELESS_API_KEY.
Installation
In SourceWeft
- Open ShapelessAI in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.shapelessai%2Fshapeless/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"shapelessai": {
"type": "http",
"url": "https://shapelessai.com/mcp"
}
}
}README
ShapelessAI
ShapelessAI runs your social presence: it drafts, schedules, and publishes content across your connected platforms, holds your Brand Memory, and keeps standing agents working while you sleep.
This repo is the public home of the agent surface: the shapeless CLI, the MCP server, the
Claude Code plugin, and the issue tracker. Your agent or script drives a ShapelessAI account: write
and schedule posts, create jobs and resume stuck ones, approve and publish, edit Brand Memory,
manage the standing agents.
The documentation lives at shapelessai.com/docs - routes,
scopes, platform limits, refusal codes, one page per subject. Every page also answers raw
Markdown: append .md to its path (https://shapelessai.com/docs/posts.md) or send
Accept: text/markdown. An agent that wants all of it in one fetch should read
shapelessai.com/llms-full.txt.
Install
Node 20 or newer.
Claude's directory
The connector Anthropic lists is https://shapelessai.com/mcp/social, the same account server
without the media-generation tools (Anthropic's Software Directory Policy 4.B lists no software that
generates images, video or audio with a model); its plugin bundle is plugins/shapeless-social.
plugins/shapeless and https://shapelessai.com/mcp stay the full server, for this marketplace and
every other host. Details: https://shapelessai.com/docs/mcp.
Authenticate
Mint a key in the studio: Settings -> API keys (/studio/api-keys). Give it
only the scopes the caller needs - read, write, or publish. Only publish
can put content out.
Config lives in ~/.config/shapeless/config.json. SHAPELESS_BASE_URL
overrides the API host (default https://shapelessai.com). shapeless logout
forgets the local copy; revoke the key itself in the studio.
Every command takes --json to print the raw API response, and --help.
Post
Write it yourself and put it on the rail - now, at a time, or in the account's next free queue
slot. Needs the publish scope.
The MCP tool is posts_create with the same arguments: connectionId, text, mediaKeys,
title, scheduledAt or queue: true, settings, firstComment. Read platforms_list
first for the platform's limits and its settingsSchema.
Free plan: ten posts a day on the rail, counted on the UTC day each post goes out on, so a
week planned ahead is ten a day rather than ten in total. The eleventh answers
402 {code: "free_daily_cap", limit, day, resetsAt}, which names the day that is full. X bills
per post, so Free posts to X once a day and without links (402 free_x_daily_cap, free_x_link);
the $9 Scheduler plan lifts the daily cap and carries 150 X posts a month, and the agent plans have
no cap. Composing, scheduling and publishing never spend credits, and Free also carries 125
credits a month for the agent team. Details:
shapelessai.com/docs/posts.
Jobs: durable runs
A job is a run the server keeps going whether or not you stay connected - the right shape for agents and cron.
Posts: the queue
Agents, Brand Memory, assets
MCP server
The hosted server is https://shapelessai.com/mcp. Add that URL to any host that speaks
remote MCP - Claude (Settings -> Connectors -> Add custom connector), ChatGPT (Developer mode),
Claude Code, Cursor, Codex, VS Code, Gemini CLI - and it opens a ShapelessAI tab to sign in and
allow. OAuth, no key. The steps for each host, in the vendor's words, are at
shapelessai.com/connect.
A client that cannot open a browser (the Agent SDK, a CI job, a self-hosted agent) skips OAuth: send
an API key from Settings -> API keys as Authorization: Bearer slk_... to the same URL. Any MCP
client that sets a header works; the scope is the key's.
The same tools (posts_create, jobs_create, posts_approve, brain_write, ...) also run locally:
shapeless mcp speaks MCP on stdio with the API key from shapeless login, and adds the tools
that read your disk (assets_upload, brain_import, and files on a job message). Every tool
carries a title and annotations - read-only tools run freely, anything that publishes, spends or
overwrites is flagged destructive so a host asks you first - and each description names the scope
it needs.
Beyond the account tools, every tool our own studio agent holds is its own MCP tool too:
generate_image, generate_footage, edit_footage, render_carousel, speak,
caption_file, web_search, x_pulse and the rest. Each answers the files it made as media keys
you can publish with posts_create. The table with what each one costs is at
shapelessai.com/docs/mcp; tools_list reads it
live.
A job is a conversation, so work passes both ways between your terminal and the web app:
- Every job result carries a
url-https://shapelessai.com/studio/c/<id>- so an agent can hand the human back a link to what it just did. jobs_brief <id>is the cheap read before replying: the last 30 messages clipped, reasoning and tool-activity dropped, an artifact inventory and post counts per queue status. Deterministic, no model in the loop.jobs_getstill gives the full transcript.jobs_listanswers 200 jobs at a time, newest first, with anextCursor; pass it back asbeforeto walk further into the history.jobs_tail <id>watches a job's run (60 seconds max, 200 events) and returns the events plus a cursor to resume from; a job with no run stream to attach to answers{live: false}instead of erroring.jobs_createandjobs_continuetake files:files(absolute local paths -.md/.txtride inline, images, video, audio and PDF are uploaded here) andmediaKeys(anything already in the account, e.g. whatassets_uploadreturned). Up to 6 per message. They land on the message the human sees in the studio, and the agent reads them for real - an image's pixels are inlined for that turn, not just its filename.
There is one prompt, continue (argument: id), which Claude Code surfaces
as a slash command: it loads that conversation's brief and tells the agent to
reply into the same thread with jobs_continue.
Running the stdio server instead of the hosted one - Claude Code:
Claude Desktop (claude_desktop_config.json), and other stdio-only hosts:
Without the env var the server uses the key stored by shapeless login.
Agent Plugins (Cursor, Kiro, Copilot, Codex) and Gemini CLI
plugins/shapeless is also an Agent Plugins 1.0 package (plugin.json,
mcp.json, skills/), so any client that loads that format installs the hosted MCP server and the
skill from this repo. Gemini CLI reads gemini-extension.json at the root:
Claude Code plugin
This repo is also a plugin marketplace. The shapeless plugin wires up the hosted MCP server and
ships a skill that teaches Claude the ropes - scopes, the post queue, when to touch Brand Memory:
Then run /mcp, pick shapeless and choose Authenticate - a browser tab signs you in once.
Where else ShapelessAI is listed
The same server and skill, installable from the registry your client already reads:
- MCP: Official MCP Registry (
com.shapelessai/shapeless), Glama, LobeHub, ModelScope - Apps, plugins and skills: ChatGPT, cursor.directory, ClawHub, skills.sh, claude-plugins.dev, ModelScope skills, 360 SkillHub
- Packages: Docker Hub, conda, Snap, Chocolatey, npm (AI SDK tools: shapelessai-ai-sdk), Rust crate, Ruby gem, Swift Package Index, CocoaPods
- Workflow platforms and API hubs: Dify Marketplace, Open WebUI, Postman, RapidAPI, APIs.io
- Docs for coding agents: Context7
- Product directories: Twelve Tools, Product Watch, Lifto, Dynamite AI, LibHunt, Startup Fame, Saaspa.ge
- Company: The Org
The API
Everything above rides one documented contract: shapelessai.com/docs/api - every route, the scope each needs, rate limits, and what deliberately refuses an API key. Machine-readable at /api/openapi.json.
Support and privacy
- Support: [email protected], or open an issue. The CLI is developed against the contract above; this repo is where it ships.
- Privacy policy: shapelessai.com/privacy
- Terms: shapelessai.com/terms
Source: README.md at commit a92a397
Tools
0Version history
6- v0.3.5LatestNov 13, 2026
- v0.3.4Nov 12, 2026
- v0.3.3Oct 30, 2026
- v0.3.2Oct 29, 2026
- v0.3.1Oct 10, 2026
- v0.3.0Sep 29, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts