MCP server de 1Social
Commit 27 oct 2026Permite que un asistente de IA publique, programe y gestione publicaciones en Instagram, TikTok, X, LinkedIn, Bluesky, Threads, Facebook y YouTube Shorts.
También conocido como sultanlive/1social-mcp, threads
- Stars
- 0
- Herramientas
- 10
- Descargas, 30 días
- —
- Última versión
- 1.0.1
- Último commit
- 27 oct 2026
- Licencia
- MIT
¿Qué es 1Social MCP?
1Social es un MCP server. Permite que un asistente de IA publique, programe y gestione publicaciones en Instagram, TikTok, X, LinkedIn, Bluesky, Threads, Facebook y YouTube Shorts. Expone 10 herramientas, como list_accounts, preview_post, publish_post.
Resumen generado a partir del README del proyecto
Acerca del MCP server de 1Social
1Social MCP es un servidor remoto con seguridad OAuth que permite a los asistentes de IA gestionar la presencia en redes sociales en múltiples plataformas. Permite a los usuarios publicar y programar contenido para Instagram, TikTok, X, LinkedIn, Bluesky, Threads, Facebook y YouTube Shorts mediante comandos en lenguaje natural. El servidor utiliza transporte streamable HTTP y gestiona la autenticación mediante OAuth 2.1 con PKCE, garantizando que tus credenciales de redes sociales permanezcan privadas frente al asistente de IA.
Los desarrolladores pueden integrar este servidor en clientes como Claude, ChatGPT, Cursor y VS Code, o utilizar herramientas de CLI como Claude Code y Gemini CLI. El sistema proporciona herramientas específicas para previsualizar publicaciones según los límites de caracteres y requisitos de archivos multimedia, verificar recibos de entrega y reintentar publicaciones fallidas en redes específicas sin afectar a las que se enviaron correctamente. Gestiona el contenido mediante una cuota de entrega medida, donde los usuarios pueden monitorear las unidades restantes y gestionar las publicaciones programadas mediante comandos de edición o cancelación.
Qué puedes hacer con él
- 1Programación multiplataformaPrograma una única publicación en múltiples redes sociales con hasta 30 días de antelación.
- 2Validación de contenidoVerifica si una publicación cumple con los requisitos específicos de la red, como el recuento de caracteres o necesidades de archivos multimedia, antes de enviarla.
- 3Recuperación de errores dirigidaReintenta una entrega fallida en una sola plataforma sin duplicar las publicaciones en las demás.
- 4Gestión de publicacionesModifica o elimina contenido programado antes de que se publique.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar 1Social MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar 1Social MCP en Claude Code
$ claude mcp add --transport http threads https://mcp.1social.dev/mcp/threadsInstalar 1Social MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"threads": {
"url": "https://mcp.1social.dev/mcp/threads"
}
}
}Instalar 1Social MCP en VS Code
.vscode/mcp.json
{
"servers": {
"threads": {
"type": "http",
"url": "https://mcp.1social.dev/mcp/threads"
}
}
}Instalar 1Social MCP en VS Code CLI
$ code --add-mcp '{"name":"threads","type":"http","url":"https://mcp.1social.dev/mcp/threads"}'Instalar 1Social MCP en Codex
$ codex mcp add threads --url https://mcp.1social.dev/mcp/threadsInstalar 1Social MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.threads] url = "https://mcp.1social.dev/mcp/threads"
Instalar 1Social MCP en Gemini CLI
$ gemini mcp add -s user --transport http threads https://mcp.1social.dev/mcp/threadsInstalar 1Social MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"threads": {
"url": "https://mcp.1social.dev/mcp/threads",
"type": "http"
}
}
}Herramientas de 1Social MCP 10
Detectado desde el READMElist_accountspreview_postpublish_postlist_postsupdate_postcancel_postdelete_postretry_deliveryupload_mediaconfirm_delivery
| list_accounts | — | |
| preview_post | — | |
| publish_post | — | |
| list_posts | — | |
| update_post | — | |
| cancel_post | — | |
| delete_post | — | |
| retry_delivery | — | |
| upload_media | — | |
| confirm_delivery | — |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Aún no verificado. Un servidor necesita una puntuación de 80, ningún hallazgo grave y suficientes datos para que podamos revisarlo. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesiblesultanlive/1social-mcp is public and reachablegithub.com/sultanlive/1social-mcp ↗Aprobado
- El paquete indica este repositorio como su origenNo verificado
- Procedencia de la compilación (atestación de Sigstore)No verificado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-10-27github.com/sultanlive/1social-mcp ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo verificado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo10 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPHTTPS endpoint answered 401 (sign-in required)Aprobado
README
Ver en GitHub1Social MCP
Model Context Protocol server for publishing to social networks — secured by OAuth.
1Social MCP lets an AI assistant post for you. Connect Claude, ChatGPT, Cursor, VS Code, or a CLI client to 1Social, then publish, schedule, check and fix posts across Instagram, TikTok, X, LinkedIn, Bluesky, Threads, Facebook and YouTube Shorts in natural language.
- Server URL:
https://mcp.1social.dev/mcp - Transport: Streamable HTTP
- Auth: OAuth 2.1 with PKCE and Dynamic Client Registration
- Landing & setup: 1social.dev/mcp
Install
1Social MCP is a remote, OAuth-secured server. There is no package to install and no API key to paste. Add this to your client's MCP config:
{
"mcpServers": {
"1social": {
"url": "https://mcp.1social.dev/mcp"
}
}
}
One-click install: Cursor · VS Code · Claude connectors · ChatGPT connectors
CLI clients (Claude Code, Gemini CLI, Codex CLI) and manual snippets: see Supported clients.
Quick start
- Create a 1Social account at 1social.dev.
- Connect your social accounts in the browser. This step needs a browser and cannot be done from a chat — each network's OAuth consent screen has to be signed for by you.
- Add the server to your client with the one-click link, the CLI command, or the JSON/TOML snippet above.
- Authorize with OAuth when your client opens the consent screen.
- Ask your assistant to post.
What you can do from chat
- 📤 Publish and schedule — one message goes to every network you pick, now or up to 30 days ahead.
- 🔍 Check before it goes — per-network character counts, whether an image is required, whether a multi-part post will thread natively or be joined, and what it costs against your quota.
- 🧾 Read the receipt — what reached each network, what failed and why, and what genuinely could not be determined.
- ♻️ Fix what broke — retry one network without touching the ones that already went out.
- 🖼 Attach media — post an image or video from the chat. Instagram and TikTok refuse posts without one.
- ✏️ Edit, cancel, delete — change a scheduled post, unschedule it, or delete it from the networks that allow deletion.
Tool surface
Ten tools, deliberately few. Publish-now and schedule are the same tool (scheduledAt: null means now), and reading one post is list_posts with a postId rather than a second tool — a smaller set is one a model picks from accurately.
| Tool | What it does |
|---|---|
list_accounts |
Connected accounts, what each network accepts, current plan, remaining quota. Call it first — channel ids come from here. |
preview_post |
Free dry run: per-network limits, media requirements, threading behaviour, quota cost. Nothing is published. |
publish_post |
Publishes now, or schedules up to 30 days ahead. Returns a per-network receipt. Takes an idempotencyKey. |
list_posts |
Posts with their delivery outcome per network — delivered, failed with a reason, cancelled, or unknown — plus stored engagement metrics. |
update_post |
Edits a post that has not been sent yet. The networks have no edit endpoint, so it withdraws and replaces. |
cancel_post |
Unschedules a post and releases the quota it reserved. |
delete_post |
Deletes from 1Social and attempts removal from each network. See What deletion can and cannot do. |
retry_delivery |
Retries one failed network, leaving the successful ones alone. Refused for permanent failures. |
upload_media |
Pre-signed upload target, for clients that cannot attach a file to a tool call. |
confirm_delivery |
Records your answer about a delivery whose outcome was unknown: is the post live on that network or not? |
The live set is what the server says it is — run tools/list against https://mcp.1social.dev/mcp for the exact, current shapes.
It tells you when it doesn't know
A post to four networks can land on three. Every tool result is per network: the failure is named in words you can act on, and a delivery whose outcome genuinely could not be determined comes back as unknown rather than as success.
unknown is not a dead end. You look at the network, tell the assistant what you see, and confirm_delivery settles it — confirming it is live commits the quota, confirming it is not marks the delivery failed so retry_delivery can pick it up. The assistant is not allowed to guess this on your behalf.
What deletion can and cannot do
delete_post always removes the post from 1Social. Removal from the network depends on the network:
| Network | Remote delete |
|---|---|
| X, LinkedIn, Bluesky, Facebook | ✅ works |
| Instagram, TikTok, Threads | ❌ no working delete API — the post stays live and only you can take it down |
On a multi-part thread only the first post is removed; the rest stay live as orphans. The tool reports what actually came down, per network, and the assistant is instructed to tell you that rather than confirm a clean delete.
Plans & access
Publishing costs us money per delivery, so the quota is metered in deliveries, not posts — one post to four networks is four deliveries. A delivery to X costs more units than the others because X charges per post (pricing has the current numbers).
| No subscription | Solo | Pro | |
|---|---|---|---|
| Price | $0 | $19/mo | $39/mo |
| Monthly deliveries | 30 units | 600 units | 1,600 units |
| All eight networks | ✅ | ✅ | ✅ |
| Delivery receipts & retries | ✅ | ✅ | ✅ |
A new account has a small free monthly allowance — enough to publish, watch the receipt come back, retry something, and schedule a post — so the tools work before you pay for anything. A failed delivery does not count against the quota when the failure was ours or the network's.
You never have to leave the chat to pay. A tool call that runs out of quota comes back with a checkout link for your account.
Supported clients
- Claude (web & desktop) — Settings → Connectors → Add custom connector
- ChatGPT — Settings → Apps & Connectors → Advanced → Developer mode → Add custom connector
- Cursor — one-click deeplink, or
~/.cursor/mcp.json - VS Code — one-click deeplink, or
.vscode/mcp.json - Claude Code (CLI) —
claude mcp add --transport http 1social https://mcp.1social.dev/mcp - Gemini CLI —
gemini mcp add --transport http 1social https://mcp.1social.dev/mcp - Codex CLI —
codex mcp add 1social --url https://mcp.1social.dev/mcp - Generic HTTP MCP client — point it at the URL and let it complete OAuth discovery
Full per-client instructions: docs/setup.md.
Cursor plugin
This repository is also a Cursor plugin. It contributes one MCP server (1social) and no rules, skills, agents, or hooks.
.cursor-plugin/plugin.json ← plugin manifest
mcp.json ← the MCP server it contributes
assets/logo.svg ← plugin logo
There is nothing to configure. The server advertises OAuth 2.1 metadata, Cursor registers itself dynamically, and the consent screen opens on first use.
Example prompts
Cross-post with a check first
"Draft a post about our new pricing page for LinkedIn, X and Bluesky, check it fits, then publish."
→ preview_post reports the per-network counts and cost; publish_post returns a receipt per network.
Schedule with an image
"Post this screenshot to Instagram and Threads on Friday at 9am."
→ The attached file goes in media; Instagram would have refused the post without it.
Find out what actually happened
"Did yesterday's post make it everywhere?"
→ list_posts returns the receipt — including any delivery still marked unknown.
Repair, not repost
"LinkedIn failed. Retry just LinkedIn."
→ retry_delivery touches one delivery and leaves the successful networks alone.
More: docs/examples.md.
Authorization
OAuth 2.1 with PKCE, per the MCP authorization spec. The authorization server is https://1social.dev; it supports Dynamic Client Registration, so compatible clients set themselves up and you only see the consent screen. Scopes granted are openid, profile, email and offline_access.
The assistant never sees your social credentials. Your network tokens stay in 1Social; the assistant holds only a token for your 1Social account, and you can revoke it at any time from the web app.
Flow details: docs/oauth.md.
Troubleshooting
Common connection, OAuth, and tool-call errors: docs/troubleshooting.md.
Marketplace listings
This repo is the source for two listings:
| Registry | Record | Manifest |
|---|---|---|
| MCP Registry | dev.1social/1social |
server.json — published by CI on a v* tag, authenticated by a DNS TXT record on 1social.dev |
| LobeHub | sultanlive-1social-mcp |
lhm.plugin.json — published with npx -y @lobehub/market-cli plugin publish --dir . |
The tools array in lhm.plugin.json is generated from the TOOLS table in the server's own contract (packages/contract/src/mcp/tools.ts in the private repo), the same table that answers tools/list. It is a snapshot: when the tool surface changes, regenerate it rather than hand-editing, or the listing will describe a server that no longer exists.
Note that the two registries carry different version numbers on purpose — server.json is at 0.1.0, while LobeHub assigned 1.0.0 at import time and a version cannot be renamed.
Project links
- Product: 1social.dev
- MCP page: 1social.dev/mcp
- MCP server:
https://mcp.1social.dev/mcp - OAuth issuer:
https://1social.dev - Issues: github.com/sultanlive/1social-mcp/issues
License
MIT — see LICENSE.
Built by @sultanlive. 1Social is a hosted publishing service; this repo is documentation for its public MCP server. Server source is not open.
Preguntas sobre 1Social MCP
¿Cómo agrego 1Social MCP a Claude Code?
Ejecuta claude mcp add --transport http threads https://mcp.1social.dev/mcp/threads en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego 1Social MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Qué herramientas proporciona 1Social MCP?
Expone 10 herramientas, incluidas list_accounts, preview_post, publish_post, list_posts, update_post.
¿Cómo instalo 1Social MCP?
Es un servidor remoto con seguridad OAuth que no requiere la instalación de paquetes ni claves de API; simplemente añade la URL del servidor a la configuración de MCP de tu cliente.
¿Puedo programar publicaciones con antelación?
Sí, puedes programar publicaciones con hasta 30 días de antelación usando la herramienta de publicación.
¿El asistente puede ver mis contraseñas de redes sociales?
No, el asistente solo mantiene un token para tu cuenta de 1Social, mientras que tus tokens de red permanecen seguros en 1Social.