Mcp Server Typescript
DataForSEO API modelcontextprotocol server
An open-source MCP server for the Publer social media management API
{
"mcpServers": {
"publer-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An open-source MCP server for the Publer social media management API
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 9 days ago. 6 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationNo known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
DataForSEO API modelcontextprotocol server
📜 An MCP server for conversation history search and retrieval in Claude Code
A Model Context Protocol (MCP) server that gives Claude direct control over Strudel.cc for AI-assisted music generation and live coding.
Official MiniMax Model Context Protocol (MCP) server that enables interaction with powerful Text to Speech, image generation and video generation APIs.
MCP Security Weekly
Get CVE alerts and security updates for Publer Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An open-source Model Context Protocol (MCP) server for the Publer social media management API.
Schedule posts, upload media, pull analytics, and manage accounts across 15+ social networks — all from your AI assistant.
Created by Kess Media
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"publer": {
"command": "npx",
"args": ["-y", "publer-mcp-server"],
"env": {
"PUBLER_API_KEY": "your-api-key-here",
"PUBLER_WORKSPACE_ID": "your-workspace-id-here"
}
}
}
}
Restart the app — Publer will appear under Connectors → Desktop.
Add to ~/.claude/mcp.json:
{
"mcpServers": {
"publer": {
"command": "npx",
"args": ["-y", "publer-mcp-server"],
"env": {
"PUBLER_API_KEY": "your-api-key-here",
"PUBLER_WORKSPACE_ID": "your-workspace-id-here"
}
}
}
}
Or via the CLI:
claude mcp add publer -- npx -y publer-mcp-server \
--env PUBLER_API_KEY=your-key \
--env PUBLER_WORKSPACE_ID=your-workspace-id
Deploy as a Cloudflare Worker and connect from any Claude interface without installing anything locally. One deployment, multiple users.
Deploy:
git clone https://github.com/alexkess/publer-mcp-server.git
cd publer-mcp-server/worker
npm install
npx wrangler deploy
npx wrangler secret put PUBLER_API_KEY
npx wrangler secret put PUBLER_WORKSPACE_ID
Your server is now live at https://publer-mcp.<your-subdomain>.workers.dev/mcp.
Connect from Claude Code (~/.claude/mcp.json):
{
"mcpServers": {
"publer": {
"type": "http",
"url": "https://publer-mcp.<your-subdomain>.workers.dev/mcp"
}
}
}
Connect from Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
The Desktop app's Connectors UI doesn't support custom HTTP MCP servers directly. Use the Claude Code config above, or add the URL via the custom connector flow in Settings → Connectors → +.
Security note: The Worker URL acts as your access credential — keep it private. Each user deploys their own Worker with their own Publer API key, so there's no shared access risk.
Add to .cursor/mcp.json:
{
"mcpServers": {
"publer": {
"command": "npx",
"args": ["-y", "publer-mcp-server"],
"env": {
"PUBLER_API_KEY": "your-api-key-here",
"PUBLER_WORKSPACE_ID": "your-workspace-id-here"
}
}
}
}
| Variable | Required | Description |
|---|---|---|
PUBLER_API_KEY | Yes | Your Publer API key |
PUBLER_WORKSPACE_ID | Yes | Your Publer workspace ID |
Option 1: From the API
curl -H "Authorization: Bearer-API YOUR_API_KEY" https://app.publer.com/api/v1/me
Your workspace IDs are in the workspaces array in the response.
Option 2: From the Publer URL
Log in to Publer, open your browser's developer tools (F12), go to the Network tab, and look for any API request — the `Publer-Workspa