Threads by 1Social

Name: Threads by 1Social
Author: sultanlive

by sultanliveversion 1.0.1i★ –iRuns in the cloud

Registry namedev.1social/threads

Install

Overview

Description from the maker (original English)

Publish and schedule Threads posts from your AI assistant.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.1social.dev/mcp/threads

Run this in your terminal

claude mcp add --transport http threads https://mcp.1social.dev/mcp/threads

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "threads": {
      "url": "https://mcp.1social.dev/mcp/threads"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "threads": {
      "type": "http",
      "url": "https://mcp.1social.dev/mcp/threads"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.1social.dev/mcp/threads

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain 1social.dev (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32455 servers in this category
Published to the registry more recently than 78% of the other 32455 servers in this category
Basic checks equal to or better than 100% of the other 32455 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Threads by 1Social safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 10 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, SSTracker free youth training

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

SSTracker free youth training

by sstracker.app

Free youth sports drills, practice plans and age-group answers for parents and coaches.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

Threads by 1Social

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

SSTracker free youth training

README from the maker

1Social MCP

Install

Quick start

What you can do from chat

Tool surface

It tells you when it doesn't know

What deletion can and cannot do

Plans & access

Supported clients

Cursor plugin

Example prompts

Authorization

Troubleshooting

Marketplace listings

Project links

License