1Social MCP server
Commit 27. Okt. 2026Veröffentliche, plane und verwalte Posts auf Instagram, TikTok, X, LinkedIn und anderen sozialen Netzwerken ganz einfach per natürlicher Sprache.
Auch bekannt als sultanlive/1social-mcp, instagram
- Stars
- 0
- Tools
- 10
- Downloads, 30 Tage
- —
- Neueste Version
- 1.0.1
- Letzter Commit
- 27. Okt. 2026
- Lizenz
- MIT
Was ist 1Social MCP?
Veröffentliche, plane und verwalte Posts auf Instagram, TikTok, X, LinkedIn und anderen sozialen Netzwerken ganz einfach per natürlicher Sprache. Er stellt 10 Tools bereit, etwa list_accounts, preview_post, publish_post.
Zusammenfassung generiert aus dem README des Projekts
Über 1Social MCP server
1Social MCP ist ein Remote-Server mit OAuth-Absicherung, der es KI-Assistenten ermöglicht, die Social-Media-Präsenz über natürliche Sprache zu verwalten. Er verbindet sich mit Clients wie Claude, ChatGPT, Cursor und VS Code, um das Veröffentlichen und Planen von Inhalten auf Plattformen wie Instagram, TikTok, X, LinkedIn, Bluesky, Threads, Facebook und YouTube Shorts zu erleichtern. Nutzer interagieren via streamable HTTP mit dem Server, und das System nutzt OAuth 2.1 mit PKCE für eine sichere Autorisierung, was bedeutet, dass der Assistant niemals deine Social-Media-Zugangsdaten sieht.
Der Server stellt zehn spezifische Tools bereit, um verschiedene Social-Media-Aufgaben zu erledigen. Du kannst list_accounts nutzen, um deinen aktuellen Plan und das verbleibende Kontingent zu prüfen, oder preview_post für einen Testlauf verwenden, der Zeichenanzahl und Medienanforderungen prüft, bevor etwas live geht. Das Tool publish_post übernimmt sowohl sofortige Veröffentlichungen als auch die Planung bis zu 30 Tage im Voraus. Zur Verwaltung bestehender Inhalte bietet der Server Tools zum Aktualisieren, Abbrechen, Löschen oder erneuten Versuchen fehlgeschlagener Zustellungen in spezifischen Netzwerken, ohne erfolgreiche Posts zu beeinflussen.
Was du damit machen kannst
- 1Plattformübergreifendes SchedulingPlane eine einzelne Nachricht, die zu einem bestimmten Zeitpunkt in der Zukunft an mehrere soziale Netzwerke gesendet wird.
- 2Content-ValidierungÜberprüfe, ob ein Post die spezifischen Zeichenlimits und Medienanforderungen verschiedener sozialer Netzwerke erfüllt, bevor du ihn veröffentlichst.
- 3Gezielte FehlerbehebungVersuche einen fehlgeschlagenen Post in einem spezifischen sozialen Netzwerk erneut, ohne ihn erneut an die Plattformen zu senden, auf denen er bereits erfolgreich war.
- 4Audit des Post-StatusÜberprüfe den Lieferstatus und die Engagement-Metriken für bereits veröffentlichte Inhalte.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du 1Social MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügen1Social MCP in Claude Code installieren
$ claude mcp add --transport http instagram https://mcp.1social.dev/mcp/instagram1Social MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"instagram": {
"url": "https://mcp.1social.dev/mcp/instagram"
}
}
}1Social MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"instagram": {
"type": "http",
"url": "https://mcp.1social.dev/mcp/instagram"
}
}
}1Social MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"instagram","type":"http","url":"https://mcp.1social.dev/mcp/instagram"}'1Social MCP in Codex installieren
$ codex mcp add instagram --url https://mcp.1social.dev/mcp/instagram1Social MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.instagram] url = "https://mcp.1social.dev/mcp/instagram"
1Social MCP in Gemini CLI installieren
$ gemini mcp add -s user --transport http instagram https://mcp.1social.dev/mcp/instagram1Social MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"instagram": {
"url": "https://mcp.1social.dev/mcp/instagram",
"type": "http"
}
}
}1Social MCP tools 10
Erkannt aus dem 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 | — |
Automatisierte Checks
Geluften am 14. Nov. 2026Vollständiger Bericht →Noch nicht verifiziert. Ein Server benötigt einen Score von 80, keine kritischen Befunde und genug Daten für unsere Prüfung. Wie die Checks funktionieren · Was du für mehr Punkte verbessern kannst
- Source Repository verknüpft und erreichbarsultanlive/1social-mcp is public and reachablegithub.com/sultanlive/1social-mcp ↗Bestanden
- Paket nennt dieses Repository als QuelleNicht geprüft
- Build-Provenienz (Sigstore-Attestierung)Nicht geprüft
- Open Source Lizenz (OSI)MITspdx.org/licenses/MIT.html ↗Bestanden
- Commit oder Release im letzten JahrLast commit or release 2026-10-27github.com/sultanlive/1social-mcp ↗Bestanden
- OpenSSF ScorecardNicht geprüft
- Package-Name ähnelt keinem populären PackageNicht geprüft
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenNicht geprüft
- Keine versteckten Anweisungen an das Modell10 tool descriptions and the README read; no override phrases, credential paths or hidden charactersBestanden
- Destruktive Tools sind markiertNicht geprüft
- Remote-Endpoint beantwortet den MCP-HandshakeHTTPS endpoint answered 401 (sign-in required)Bestanden
README
Auf GitHub ansehen1Social 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.
1Social MCP Fragen
Wie füge ich 1Social MCP zu Claude Code hinzu?
Führe claude mcp add --transport http instagram https://mcp.1social.dev/mcp/instagram in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich 1Social MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Welche Tools bietet 1Social MCP?
Er stellt 10 Tools bereit, darunter list_accounts, preview_post, publish_post, list_posts, update_post.
Wie installiere ich 1Social MCP?
Es handelt sich um einen Remote-Server mit OAuth-Absicherung, der keine Paketinstallation oder API-Keys erfordert; du musst lediglich die Server-URL zu der MCP-Config deines Clients hinzufügen.
Kann ich Posts im Voraus planen?
Ja, du kannst Posts bis zu 30 Tage im Voraus planen.
Sieht der Assistant meine Social-Media-Zugangsdaten?
Nein, der Assistant hält nur ein Token für dein 1Social-Konto, während deine Netzwerk-Token sicher bei 1Social bleiben.
Kann ich Posts von Instagram oder TikTok löschen?
Nein, Instagram, TikTok und Threads bieten über diesen Service keine funktionierende Delete-API an, daher bleiben die Posts online.