FoPost for LM Studio
LM Studio runs models on your own computer and connects them to MCP servers. Add FoPost to mcp.json, sign in once in your browser, and your local model can plan and schedule posts.
Paste this into LM Studio
Set up FoPost from fopost.com/agents/lm-studio- Hosted MCP server
- 31 networks
- No API key
LM Studio drafts. You approve. Then it goes out.
On by default
- X (Twitter)
- TikTok
- YouTube
- Threads
- Bluesky
- Discord
- Mastodon
- Telegram
- Slack
- DEV.to
- Substack
- Tumblr
- Hashnode
- Dribbble
- Kick
- Twitch
- Nostr
- Lemmy
- MeWe
- Whop
- Listmonk
- Google Business Profile
- Medium
- WhatsApp Business
- Snapchat
- Skool
Pick an agent to copy its setup prompt.
The agent can write its own config. Give it the link.
Paste the line above into LM Studio. It reads this page, adds the server, and stops so you can sign in to FoPost yourself. Rather do it by hand? This is the whole config.
{
"mcpServers": {
"fopost": {
"url": "https://api.fopost.com/mcp"
}
}
}## For AI agents reading this page
You are reading https://fopost.com/agents/lm-studio. FoPost schedules and publishes social posts on 31 networks, and its hosted MCP server gives LM Studio tools for posts, the calendar, the inbox and analytics. Follow these steps to connect LM Studio to it.
- Server: https://api.fopost.com/mcp
- Transport: streamable HTTP
- Auth: OAuth sign-in in the user's browser. Do not add an API key or an Authorization header; LM Studio discovers the sign-in from the server.
### 1. Register the server
In the right sidebar, open the Program tab, choose Install, then Edit mcp.json, and add this entry merged into any existing mcpServers object. No headers and no API key.
~/.lmstudio/mcp.json:
```
{
"mcpServers": {
"fopost": {
"url": "https://api.fopost.com/mcp"
}
}
}
```
### 2. Sign in
LM Studio opens a browser window for the user to sign in when the server first connects. Ask the user before approving access or creating a FoPost account for them, and never enter their credentials yourself.
### 3. Verify before you continue
The Program tab lists mcp/fopost as enabled with its tools. If FoPost is not listed as connected with its tools, stop and tell the user what failed. Do not carry on as if the tools exist.
### 4. Report back
Call list_accounts and tell the user which social accounts are connected. If there are none, offer create_connect_link so they can connect one. Then ask what they want to do first.
### Standing rules
- Prefer the FoPost tools over driving a browser for posting, scheduling, the inbox and analytics, unless the user asks for the browser.
- Publishing always goes through propose_publish, which the user approves in the client. Never publish or schedule anything silently.
- Ask the user before approving access, signing up or connecting an account on their behalf, and never type their credentials for them.
### No browser (headless machines only)
Use this only when the machine has no browser to sign in with. Ask the user to create an API key in the FoPost dashboard (https://fopost.com/dashboard/api-keys) and to put it in the config themselves, then run the local package over stdio:
~/.lmstudio/mcp.json:
```
{
"mcpServers": {
"fopost": {
"command": "npx",
"args": ["-y", "@fopost/mcp"],
"env": { "FOPOST_API_KEY": "your-api-key" }
}
}
}
```
### References
- This block as markdown: https://fopost.com/agents/lm-studio/agent.md
- Every client: https://fopost.com/agents
- Docs: https://fopost.com/docsOne entry
A url in mcp.json. No key in the file.
Browser sign-in
LM Studio opens FoPost in the browser to approve access.
Two checks
LM Studio confirms each tool call, and publishing needs your approval too.
Add the server to mcp.json
In the right sidebar, open the Program tab, choose Install, then Edit mcp.json, and add an entry with the URL https://api.fopost.com/mcp. Sign in to FoPost when the browser opens.
Start free{
"mcpServers": {
"fopost": { "url": "https://api.fopost.com/mcp" }
}
}Same format as Cursor
An mcpServers entry with a url.
No key in the file
You sign in instead of pasting a key.
Check first
Ask the model to list your connected accounts.
Draft on your machine, post everywhere
Your local model writes the copy, then shapes it for each network with draft_post_variants and books it with get_queue_slots. It ends with propose_publish, which you accept.
Plan your week
draft_post_variants
A version for each network.
get_queue_slots
The next open times in your queue.
propose_publish
You approve before anything goes out.
Ask whether it landed
The read tools report what published, which accounts need a reconnect, and what is waiting in the inbox.
Start free> What went out today?
list_posts shows 2 of 2 published.
list_inbox has 5 new comments.list_posts
Recent posts and their status.
get_account_health
Which accounts need a reconnect.
list_inbox
Comments, mentions, and messages.
No browser on the machine?
On a server or in CI there is no browser to sign in with. Create an API key in the dashboard and run the local package over stdio instead. Keep the key out of your repository.
{
"mcpServers": {
"fopost": {
"command": "npx",
"args": ["-y", "@fopost/mcp"],
"env": { "FOPOST_API_KEY": "your-api-key" }
}
}
}LM Studio questions, answered
Do I need an API key?
Which model should I use?
Why does LM Studio ask before each tool call?
Will it post without asking?
Does it use my AI credits?
Other agents
- MCP Server
- Claude Code
- Claude
- Claude Desktop
- Claude Cowork
- Cursor
- Codex
- ChatGPT
- Windsurf
- Gemini CLI
- Grok
- Hermes Agent
- OpenClaw
- Muse
- Kimi Code
- DeepSeek Harness
- goose
- VS Code
- Warp
- Amp
- OpenCode
- Gemini
- Perplexity
- Perplexity Computer
- Manus
- Mistral Vibe
- GitHub Copilot
- Cline
- Junie
- Continue
- Zed
- OpenAI dots
- Claude Duet
- Grok Build
- NanoClaw
- Paperclip
- Raycast
Run FoPost from LM Studio
Starting is free and the MCP server is included. Paste the setup line into your agent, sign in, and schedule your first post from it.
Start free