1Social MCP server
2026년 10월 27일 커밋AI 어시스턴트가 Instagram, TikTok, X, LinkedIn, Bluesky, Threads, Facebook, YouTube Shorts에 걸쳐 게시물을 게시, 예약 및 관리할 수 있도록 합니다.
다른 이름 sultanlive/1social-mcp, linkedin
- 스타
- 0
- Tools
- 10
- 다운로드, 30일
- —
- 최신 버전
- 1.0.1
- 마지막 커밋
- 2026년 10월 27일
- 라이선스
- MIT
1Social MCP란?
1Social은(는) MCP server입니다. 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 보안 원격 서버입니다. 사용자는 streamable HTTP 전송 방식을 통해 Claude, ChatGPT, Cursor 또는 VS Code와 같은 클라이언트를 서버에 연결할 수 있습니다. 자연어 명령을 사용하여 Instagram, TikTok, X, LinkedIn, Bluesky, Threads, Facebook, YouTube Shorts에 콘텐츠를 게시하고 예약할 수 있습니다.
이 시스템은 보안 인증을 위해 PKCE를 포함한 OAuth 2.1을 사용하므로 어시스턴트가 사용자의 소셜 미디어 계정 정보를 절대 볼 수 없습니다. 대신 어시스턴트는 1Social 계정과 상호작용하여 게시물을 관리합니다. 서버는 글자 수 제한 및 미디어 요구 사항을 확인하기 위한 게시물 미리보기, 최대 30일 전 콘텐츠 예약, 전송 영수증 처리 등의 특정 도구를 제공합니다. 또한 특정 네트워크에서 실패한 전송을 재시도하거나 플랫폼 API가 허용하는 범위 내에서 게시물을 삭제하는 특화된 기능도 포함되어 있습니다.
활용 사례
- 1교차 플랫폼 콘텐츠 예약단일 메시지를 미래의 특정 시간에 여러 소셜 네트워크에 게시되도록 예약합니다.
- 2게시 전 유효성 검사게시물을 전송하기 전에 각 소셜 네트워크의 특정 글자 수 및 미디어 요구 사항을 충족하는지 확인합니다.
- 3대상별 전송 복구이미 성공적으로 전송된 네트워크에는 콘텐츠를 중복 게시하지 않고, 전송에 실패한 특정 네트워크에서만 게시물을 재시도합니다.
- 4게시물 상태 감사이전 게시물의 전송 결과와 참여 지표를 확인하여 의도한 목적지에 도달했는지 점검합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
1Social MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 1Social MCP 설치
$ claude mcp add --transport http linkedin https://mcp.1social.dev/mcp/linkedinCursor에 1Social MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"linkedin": {
"url": "https://mcp.1social.dev/mcp/linkedin"
}
}
}VS Code에 1Social MCP 설치
.vscode/mcp.json
{
"servers": {
"linkedin": {
"type": "http",
"url": "https://mcp.1social.dev/mcp/linkedin"
}
}
}VS Code CLI에 1Social MCP 설치
$ code --add-mcp '{"name":"linkedin","type":"http","url":"https://mcp.1social.dev/mcp/linkedin"}'Codex에 1Social MCP 설치
$ codex mcp add linkedin --url https://mcp.1social.dev/mcp/linkedinCodex config.toml에 1Social MCP 설치
~/.codex/config.toml
[mcp_servers.linkedin] url = "https://mcp.1social.dev/mcp/linkedin"
Gemini CLI에 1Social MCP 설치
$ gemini mcp add -s user --transport http linkedin https://mcp.1social.dev/mcp/linkedinGemini settings.json에 1Social MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"linkedin": {
"url": "https://mcp.1social.dev/mcp/linkedin",
"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 linkedin https://mcp.1social.dev/mcp/linkedin를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
1Social MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
1Social MCP는 어떤 도구를 제공하나요?
10개 도구를 제공합니다. 예: list_accounts, preview_post, publish_post, list_posts, update_post.
1Social MCP를 어떻게 설치하나요?
설치할 패키지가 없는 OAuth 보안 원격 서버입니다. 클라이언트의 MCP 설정에 서버 URL을 추가하면 됩니다.
게시물을 미리 예약할 수 있나요?
네, publish 도구를 사용하여 최대 30일 전까지 게시물을 예약할 수 있습니다.
어시스턴트가 제 소셜 미디어 계정 정보를 볼 수 있나요?
아니요, 어시스턴트는 1Social 계정에 대한 토큰만 보유하며, 네트워크 토큰은 1Social 내에 안전하게 보관됩니다.