1Social MCPサーバー
コミット 2026年10月27日AIアシスタントを使用して、Instagram、TikTok、X、LinkedIn、Bluesky、Threads、Facebook、YouTube Shortsへの投稿、予約、管理を行います。
別名 sultanlive/1social-mcp, facebook
- スター
- 0
- ツール
- 10
- ダウンロード数(30日間)
- —
- 最新バージョン
- 1.0.1
- 最終コミット
- 2026年10月27日
- ライセンス
- MIT
1Social MCPとは
AIアシスタントを使用して、Instagram、TikTok、X、LinkedIn、Bluesky、Threads、Facebook、YouTube Shortsへの投稿、予約、管理を行います。 10個のツールを提供しており、list_accounts, preview_post, publish_postなどがあります。
プロジェクトのREADMEから生成された概要
1Social MCP server について
1Social MCPは、AIアシスタントが複数のプラットフォームにわたってソーシャルメディア運用を管理できるようにする、OAuthで保護されたリモートサーバーです。自然言語を使用して、Instagram、TikTok、X、LinkedIn、Bluesky、Threads、Facebook、YouTube Shorts向けのコンテンツの公開や予約が可能です。このサーバーはstreamable HTTPトランスポートを使用し、PKCEを用いたOAuth 2.1によって接続を保護しているため、SNSの認証情報をプライベートに保ったまま、アシスタントには1Socialアカウント用のトークンのみを渡すことができます。
開発者は、このサーバーをClaude、ChatGPT、Cursor、VS Codeなどのクライアントに統合できます。手動でのAPI管理の代わりに、preview_postなどのツールを使用して、公開前に文字数やメディア要件を確認できます。また、システムは詳細な配信レシートを提供するため、どのネットワークに投稿が届き、どれが失敗したかを正確に把握できます。特定のネットワークで失敗した場合でも、retry_deliveryを使用すれば、他のプラットフォームに影響を与えることなく、そのプラットフォームのみの再試行が可能です。
できること
- 1マルチプラットフォームでのコンテンツ予約単一のメッセージを、最大30日先までの複数のソーシャルネットワークへ予約投稿できます。
- 2公開前のバリデーション投稿を送信する前に、文字数制限やメディア要件などの各ネットワーク固有の要件を満たしているか確認できます。
- 3特定の配信エラーのリカバリ投稿に成功したネットワークで重複させることなく、失敗した特定のソーシャルネットワークに対してのみ再試行できます。
- 4投稿ステータスの監査過去の投稿の配信結果やエンゲージメントメトリクスを確認できます。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
1Social MCPのインストール方法
フォーマット検証日 2026年11月10日Cursor に追加Gooseに追加Claude Codeに1Social MCPをインストール
$ claude mcp add --transport http facebook https://mcp.1social.dev/mcp/facebookCursorに1Social MCPをインストール
~/.cursor/mcp.json
{
"mcpServers": {
"facebook": {
"url": "https://mcp.1social.dev/mcp/facebook"
}
}
}VS Codeに1Social MCPをインストール
.vscode/mcp.json
{
"servers": {
"facebook": {
"type": "http",
"url": "https://mcp.1social.dev/mcp/facebook"
}
}
}VS Code CLIに1Social MCPをインストール
$ code --add-mcp '{"name":"facebook","type":"http","url":"https://mcp.1social.dev/mcp/facebook"}'Codexに1Social MCPをインストール
$ codex mcp add facebook --url https://mcp.1social.dev/mcp/facebookCodex config.tomlに1Social MCPをインストール
~/.codex/config.toml
[mcp_servers.facebook] url = "https://mcp.1social.dev/mcp/facebook"
Gemini CLIに1Social MCPをインストール
$ gemini mcp add -s user --transport http facebook https://mcp.1social.dev/mcp/facebookGemini settings.jsonに1Social MCPをインストール
~/.gemini/settings.json
{
"mcpServers": {
"facebook": {
"url": "https://mcp.1social.dev/mcp/facebook",
"type": "http"
}
}
}1Social MCPツール 10
READMEから検出list_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 | — |
自動チェック
実行日 2026年11月14日完全なレポート →まだ検証されていません。サーバーには80点のスコア、重大な問題がないこと、および検証に必要な十分なデータが必要です。 チェックの仕組み · 点数を上げるための改善点
- ソースリポジトリがリンクされており、アクセス可能sultanlive/1social-mcp is public and reachablegithub.com/sultanlive/1social-mcp ↗合格
- パッケージがこのリポジトリをソースとして指定未チェック
- ビルドの来歴 (Sigstore 証明)未チェック
- オープンソースライセンス (OSI)MITspdx.org/licenses/MIT.html ↗合格
- 過去1年以内にコミットまたはリリースありLast commit or release 2026-10-27github.com/sultanlive/1social-mcp ↗合格
- OpenSSF Scorecard未チェック
- パッケージ名が有名なパッケージに酷似していない未チェック
- パッケージおよびその依存関係に重大な勧告なし未チェック
- モデルへの隠れた指示がない10 tool descriptions and the README read; no override phrases, credential paths or hidden characters合格
- 破壊的なツールがラベル付けされている未チェック
- リモートエンドポイントが MCP ハンドシェイクに応答HTTPS endpoint answered 401 (sign-in required)合格
README
GitHubで見る1Social 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のよくある質問
1Social MCPをClaude Codeに追加するには
ターミナルでclaude mcp add --transport http facebook https://mcp.1social.dev/mcp/facebookを実行します。すべてのプロジェクトで利用するには--scope userを追加します。
1Social MCPをCursorに追加するには
~/.cursor/mcp.jsonを開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
1Social MCPが提供するツールは
10個のツールを提供しており、list_accounts, preview_post, publish_post, list_posts, update_postなどがあります。
1Social MCPのインストール方法は?
このサーバーはOAuthで保護されたリモートサーバーであるため、パッケージのインストールやAPIキーは不要です。クライアントのMCP設定にサーバーURLを追加するだけで利用できます。
投稿の予約はできますか?
はい、publishツールを使用することで、最大30日先までの投稿を予約できます。
アシスタントにSNSのログイン情報は渡されますか?
いいえ、アシスタントが保持するのは1Socialアカウント用のトークンのみです。各SNSのネットワークトークンは1Social内で安全に管理されます。