Postproxy MCP sunucusu
Commit 13 Kas 2026Postproxy API kullanarak başlıca platformlarda sosyal medya gönderileri yayınlayın, planlayın ve yönetin.
Ayrıca bilinen adı postproxy/postproxy-mcp, postproxy-mcp
- Yıldızlar
- 4
- Araçlar
- —
- İndirmeler, 30 gün
- —
- En son sürüm
- 1.10.0
- Son commit
- 13 Kas 2026
- Lisans
- MIT
Postproxy MCP nedir?
Postproxy bir MCP sunucusudur. Postproxy API kullanarak başlıca platformlarda sosyal medya gönderileri yayınlayın, planlayın ve yönetin.
Özet, projenin README dosyasından oluşturuldu
Postproxy MCP sunucusu hakkında
Postproxy, Claude Code kullanan geliştiricilerin sosyal medya varlıklarını tek bir arayüz üzerinden yönetmelerini sağlar. Bu MCP server, yapay zeka istemcinizi Postproxy API'ye bağlayarak Instagram, LinkedIn, X ve WhatsApp gibi çeşitli ağlarda içerik yayınlamanıza, planlamanıza ve izlemenize olanak tanır. Kurulum sırasında ortam değişkenleri (environment variables) aracılığıyla yapılandırılan bir Postproxy API anahtarı ve temel URL gerektiren yerel bir köprü görevi görür.
Kullanıcılar, auth_status ile kimlik doğrulama durumunu kontrol etmek veya summary_get kullanarak kapsamlı bir etkinlik özeti almak gibi karmaşık sosyal medya iş akışlarını gerçekleştirebilirler. Sunucu; profil gruplarını listeleme, Facebook veya LinkedIn için belirli yerleşimleri belirleme ve profiles_stats aracılığıyla takipçi büyüme trendlerini görüntüleme dahil olmak üzere profil yönetimi üzerinde ayrıntılı kontrol sağlar. İçerik dağıtımı için post_publish aracı; planlama, medya ekleri ve TikTok veya YouTube gibi servisler için platforma özel yapılandırmaları destekler.
Neler yapabilirsiniz
- 1Sosyal medya aktivitelerini izleyinBağlı tüm hesaplardaki son etkileşimlerin, yorumların ve doğrudan mesajların bir özetini isteyin.
- 2Yeni sosyal medya hesapları bağlayınYeni bir profesyonel profili belirli bir profil grubuna bağlamak için bir OAuth bağlantı URL'si oluşturun.
Projenin README dosyasından alınmıştır. Her kullanım durumu, oradaki bir alıntı ile kontrol edilir.
Postproxy MCP nasıl yüklenir
Biçimler 10 Kas 2026 tarihinde doğrulandıCursor'a ekleGoose'a eklePostproxy MCP'yi Claude Code içine yükleyin
$ claude mcp add --transport http postproxy-mcp https://mcp.postproxy.dev/mcpPostproxy MCP'yi Cursor içine yükleyin
~/.cursor/mcp.json
{
"mcpServers": {
"postproxy-mcp": {
"url": "https://mcp.postproxy.dev/mcp"
}
}
}Postproxy MCP'yi VS Code içine yükleyin
.vscode/mcp.json
{
"servers": {
"postproxy-mcp": {
"type": "http",
"url": "https://mcp.postproxy.dev/mcp"
}
}
}Postproxy MCP'yi VS Code CLI içine yükleyin
$ code --add-mcp '{"name":"postproxy-mcp","type":"http","url":"https://mcp.postproxy.dev/mcp"}'Postproxy MCP'yi Codex içine yükleyin
$ codex mcp add postproxy-mcp --url https://mcp.postproxy.dev/mcpPostproxy MCP'yi Codex config.toml içine yükleyin
~/.codex/config.toml
[mcp_servers.postproxy-mcp] url = "https://mcp.postproxy.dev/mcp"
Postproxy MCP'yi Gemini CLI içine yükleyin
$ gemini mcp add -s user --transport http postproxy-mcp https://mcp.postproxy.dev/mcpPostproxy MCP'yi Gemini settings.json içine yükleyin
~/.gemini/settings.json
{
"mcpServers": {
"postproxy-mcp": {
"url": "https://mcp.postproxy.dev/mcp",
"type": "http"
}
}
}Otomatik kontroller
Çalıştırıldı 14 Kas 2026Tam rapor →Henüz doğrulanmadı. Bir sunucunun 80 puana, ciddi bir bulgu olmamasına ve kontrol edebilmemiz için yeterli veriye ihtiyacı vardır. Kontroller nasıl çalışır · Daha fazla puan için nelerin düzeltileceği
- Kaynak deposu bağlantılı ve erişilebilirpostproxy/postproxy-mcp is public and reachablegithub.com/postproxy/postproxy-mcp ↗Geçti
- Paket, bu depoyu kaynağı olarak gösteriyorKontrol edilmedi
- Derleme kökeni (Sigstore onayı)Kontrol edilmedi
- Açık kaynak lisansı (OSI)MITspdx.org/licenses/MIT.html ↗Geçti
- Son bir yıl içinde commit veya sürüm mevcutLast commit or release 2026-11-13github.com/postproxy/postproxy-mcp ↗Geçti
- OpenSSF ScorecardKontrol edilmedi
- Paket adı popüler bir pakete yakın değilKontrol edilmedi
- Pakette veya bağımlılıklarında kritik uyarı yokKontrol edilmedi
- Modele yönelik gizli talimat yok0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersGeçti
- Yıkıcı araçlar etiketlenmişKontrol edilmedi
- Uzak uç nokta MCP el sıkışmasına yanıt veriyorinitialize answered with protocol 2025-03-26 in 238 msGeçti
Postproxy MCP Server
MCP (Model Context Protocol) server for integrating Postproxy API with Claude Code. This server provides tools for publishing posts, checking statuses, and managing social media profiles through Claude Code.
Installation
Global Installation
npm install -g postproxy-mcp
Local Installation
npm install postproxy-mcp
Claude Code stores MCP server configuration under ~/.claude/plugins/.
After installing postproxy-mcp, Claude will automatically detect the server on restart.
Configuration
Register MCP Server
After installing postproxy-mcp, register it with Claude Code using the claude mcp add command:
claude mcp add --transport stdio postproxy-mcp --env POSTPROXY_API_KEY=your-api-key --env POSTPROXY_BASE_URL=https://api.postproxy.dev/api -- postproxy-mcp
Replace your-api-key with your actual Postproxy API key.
The configuration will be automatically saved to ~/.claude/plugins/. After running this command:
- Restart your Claude Code session
- Test the connection by asking Claude: "Check my Postproxy authentication status"
- If tools are available, Claude will be able to use them automatically
Alternative: Interactive Setup
For non-technical users, you can use the interactive setup command:
postproxy-mcp setup
or
postproxy-mcp-setup
This will guide you through the setup process step by step and register the server using claude mcp add automatically.
Available Tools
Authentication Tools
auth_status
Check authentication status, API configuration, and workspace information.
Parameters: None
Returns:
{
"authenticated": true,
"base_url": "https://api.postproxy.dev/api",
"profile_groups_count": 2
}
Account Overview
summary_get
Answer "what's the status?" in one call — an activity snapshot for a time window instead of separate history_list / comments_list / dm_chats_list round trips.
Parameters:
window(string, optional):24h(default),7d, or30dfrom(string, optional): ISO 8601 timestamp or bare date starting an explicit range. Overrideswindow, and the*_previouscounts come backnullto(string, optional): End of the explicit range. Defaults to now when onlyfromis givenprofile_group_id(string, optional): Report on a single group. Omit to cover every group the key can reach
Returns:
{
"window": {
"label": "24h",
"from": "2026-08-17T09:00:00Z",
"to": "2026-08-18T09:00:00Z",
"previous_from": "2026-08-16T09:00:00Z",
"backlog_from": "2026-07-19T09:00:00Z"
},
"posts": {
"published": 4,
"published_previous": 3,
"failed": 1,
"scheduled_ahead": 6,
"next_scheduled_at": "2026-08-18T14:00:00Z",
"by_platform": { "instagram": { "published": 4, "failed": 0 } }
},
"engagement": {
"total": { "impressions": 48210, "likes": 1204 },
"by_platform": { "instagram": { "impressions": 31002, "likes": 900 } },
"posts_with_insights": 14
},
"comments": { "received": 96, "received_previous": 71, "awaiting_reply": 12, "by_platform": { "instagram": 61 } },
"reviews": { "received": 7, "received_previous": 4, "awaiting_reply": 3 },
"dms": { "inbound": 41, "outbound": 33, "chats_awaiting_reply": 5, "reply_window_closing": 2 },
"api": { "calls": 812, "calls_previous": 640 }
}
Notes:
- Post counts are posts, so a post sent to three networks counts once and a thread counts once.
by_platformcounts per-network deliveries, so a 3-item X thread is 3 undertwitter. engagementis lifetime-to-date for posts published in the window, not engagement earned during it — it sums each post's newest stats snapshot. A post published minutes ago may have no snapshot yet and won't be inposts_with_insights. Keys are the normalized metrics listed in Stats Fields by Platform.- The
awaiting_replycounts describe current state, not the window — they don't change when you changewindow. They look back 30 days, returned aswindow.backlog_from. A comment counts as replied only when the reply came from you (via Postproxy or the profile itself);chats_awaiting_replyis derived from message timestamps, since Postproxy has no read/unread state. reply_window_closingcounts chats with under 6 hours of their 24h messaging window left. Networks without a window (Telegram, Bluesky) are excluded.engagementisnullwhen insights are off for the account;dmsisnullwhen DMs are off.- Scoped like every other tool: a group-scoped key reports only its group.
Profile Management
profile_groups_list
List all profile groups accessible with your API key. Profile groups are organizational containers (e.g. per brand or client) that hold related profiles. Use a group's id to filter profiles_list by profile_group_id.
Parameters: None
Returns:
{
"profile_groups": [
{
"id": "grp123abc",
"name": "Main Brand",
"profiles_count": 4
}
]
}
profile_groups_initialize_connection
Generate a connect URL for a new profile in a profile group. The user opens the URL to finish the OAuth flow.
Parameters:
profile_group_id(string, required): Profile group IDplatform(string, required): Platform to connect (e.g.instagram,linkedin,whatsapp)onboarding(string, optional): Instagram and WhatsApp only. Instagram:instagram(default) uses Instagram Login;facebookuses Facebook Login, for an Instagram professional account linked to a Facebook Page you manage. The profile isplatform: "instagram"either way, and reconnecting with the other method updates the existing profile in place. WhatsApp:apiorbusiness_app(see WhatsApp Business Management).identifier+app_password(Bluesky) /bot_token(Telegram): credentials, local server only
profiles_list
List all available social media profiles for posting.
Parameters:
profile_group_id(string, optional): If provided, only profiles in this group are returned (useprofile_groups_listto find group IDs)
Returns:
{
"profiles": [
{
"id": "profile-123",
"name": "My Twitter Account",
"platform": "twitter",
"profile_group_id": "group-abc"
}
]
}
profiles_placements
List available placements for a profile. For Facebook profiles, placements are business pages. For LinkedIn profiles, placements include the personal profile and organizations. For Pinterest profiles, placements are boards. For Telegram profiles, placements are channels the bot can post to. For Google Business profiles, placements are locations, returned as full resource paths (accounts/X/locations/Y) to pass as location_id. For WhatsApp profiles, placements are the phone numbers on the Business Account — the placement id is the phone_number_id every whatsapp_* tool and dm_chat_create take. Available for facebook, linkedin, pinterest, telegram, google_business, and whatsapp profiles.
Parameters:
profile_id(string, required): Profile hashid
Returns (LinkedIn example):
{
"placements": [
{
"id": null,
"name": "Personal Profile"
},
{
"id": "108520199",
"name": "Acme Marketing"
}
]
}
Notes:
- If no placement is specified when creating a post:
- LinkedIn: defaults to the personal profile
- Facebook: defaults to a random connected page (if only one page is connected, no need to set a placement ID)
- Pinterest: it fails
- Telegram: it fails —
chat_idis required on every post - Google Business: it fails —
location_idis required on every post and on everygoogle_business_*tool
profiles_stats
Get the follower/engagement timeseries for a profile. Snapshots are captured roughly every 23 hours, so you can plot follower growth and other trends over time. The stats fields are platform-native (not normalized) — see Stats Fields by Platform in the post_stats section for shape and add-on profile-level keys (followers_count, followersCount, etc.) per network.
Parameters:
profile_id(string, required): Profile hashidplacement_id(string, conditional): Required forfacebook,linkedin,telegram, andgoogle_businessprofiles. Get it fromprofiles_placements. Omit forinstagram,threads,youtube,twitter,tiktok,pinterest, andbluesky.from(string, optional): ISO 8601 timestamp — only include snapshots recorded at or after this timeto(string, optional): ISO 8601 timestamp — only include snapshots recorded at or before this time
Returns (LinkedIn example):
{
"data": {
"profile_id": "prof_li_001",
"platform": "linkedin",
"placement_id": "108520199",
"records": [
{ "stats": { "followerCount": 4500, "shareCount": 8, "likeCount": 80 }, "recorded_at": "2026-05-09T08:00:00Z" },
{ "stats": { "followerCount": 4520, "shareCount": 9, "likeCount": 90 }, "recorded_at": "2026-05-10T08:00:00Z" }
]
}
}
For non-placement networks (e.g. Bluesky), omit placement_id:
{
"data": {
"profile_id": "prof_bsky_001",
"platform": "bluesky",
"placement_id": null,
"records": [
{ "stats": { "followersCount": 8800, "postsCount": 40 }, "recorded_at": "2026-05-09T08:00:00Z" }
]
}
}
Post Management
post_publish
Publish a post to specified social media profiles.
Parameters:
-
content(string, required): Post content text -
profiles(string[], required): Array of profile IDs (hashids) or platform names (e.g.,"linkedin","instagram","twitter"). When using platform names, posts to the first connected profile for that platform. -
schedule(string, optional): ISO 8601 scheduled time -
media(string[], optional): Array of media URLs or local file paths -
idempotency_key(string, optional): Idempotency key for deduplication -
require_confirmation(boolean, optional): If true, return summary without publishing -
draft(boolean, optional): If true, creates a draft post that won't publish automatically -
queue_id(string, optional): Queue ID to add the post to. The queue will automatically assign a timeslot. Do not use together withschedule. -
queue_priority(string, optional): Priority when adding to a queue:high,medium(default), orlow -
platforms(object, optional): Platform-specific parameters. Key is platform name (e.g., "instagram", "youtube", "tiktok"), value is object with platform-specific options. See Platform Parameters Reference for full documentation.Example:
{ "instagram": { "format": "reel", "collaborators": ["username1", "username2"], "first_comment": "Link in bio!" }, "youtube": { "title": "My Video Title", "privacy_status": "public" }, "tiktok": { "privacy_status": "PUBLIC_TO_EVERYONE", "auto_add_music": true } }
Returns:
{
"post_id": "job-123",
"accepted_at": "2024-01-01T12:00:00Z",
"status": "pending",
"draft": true
}
Note on draft posts: If you request a draft post (draft: true) but the API returns draft: false, a warning field will be included in the response indicating that the API may have ignored the draft parameter. This can happen if the API does not support drafts with certain parameters (e.g., media attachments) or under specific conditions. Check the warning field in the response for details.
post_status
Get status of a published post by job ID.
Parameters:
post_id(string, required): Post ID from post.publish response
Returns:
{
"post_id": "job-123",
"overall_status": "complete",
"draft": false,
"status": "processed",
"content": "Full post body as submitted...",
"scheduled_at": "2024-01-02T09:00:00Z",
"created_at": "2024-01-01T12:00:00Z",
"source": "postproxy",
"queue_id": null,
"platforms": [
{
"platform": "twitter",
"status": "published",
"url": "https://twitter.com/status/123",
"post_id": "123",
"error": null,
"attempted_at": "2024-01-01T12:00:00Z"
}
]
}
scheduled_at is null for posts published immediately. Platform url is the published permalink (null until published).
Status values:
overall_status:"draft","pending","processing","complete","failed"- Platform
status:"pending","processing","published","failed","deleted" - Platform
error: Error message if publishing failed (null if successful)
post_publish_draft
Publish a draft post. Only posts with draft: true status can be published using this endpoint.
Parameters:
post_id(string, required): Post ID of the draft post to publish
Returns:
{
"post_id": "job-123",
"status": "processed",
"draft": false,
"scheduled_at": null,
"created_at": "2024-01-01T12:00:00Z",
"message": "Draft post published successfully"
}
post_delete
Delete a post by job ID.
Parameters:
post_id(string, required): Post ID to delete
Returns:
{
"post_id": "job-123",
"deleted": true
}
post_stats
Get stats snapshots for one or more posts. Returns all matching snapshots so you can see trends over time. Supports filtering by profiles/networks and timespan.
Parameters:
post_ids(string[], required): Array of post hashids (max 50)profiles(string, optional): Comma-separated list of profile hashids or network names (e.g.instagram,twitterorabc123,def456or mixed)from(string, optional): ISO 8601 timestamp — only include snapshots recorded at or after this timeto(string, optional): ISO 8601 timestamp — only include snapshots recorded at or before this time
Returns:
{
"data": {
"abc123": {
"platforms": [
{
"profile_id": "prof_abc",
"platform": "instagram",
"records": [
{
"stats": {
"impressions": 1200,
"likes": 85,
"comments": 12,
"saved": 8
},
"recorded_at": "2026-02-20T12:00:00Z"
}
]
}
]
}
}
}
Stats fields by platform:
| Platform | Fields |
|---|---|
impressions, likes, comments, saved, profile_visits, follows |
|
impressions, clicks, likes |
|
| Threads | impressions, likes, replies, reposts, quotes, shares |
impressions, likes, retweets, comments, quotes, saved |
|
| YouTube | impressions, likes, comments, saved |
impressions |
|
| TikTok | impressions, likes, comments, shares |
impressions, likes, comments, saved, outbound_clicks |
Notes: Instagram stories do not return stats. TikTok stats require the post to have a public ID.
Queue Management
queues_list
List all posting queues. Queues automatically schedule posts into recurring weekly timeslots with priority-based ordering.
Parameters:
profile_group_id(string, optional): Filter queues by profile group
Returns:
{
"queues": [
{
"id": "q1abc",
"name": "Morning Posts",
"description": "Daily morning content",
"timezone": "America/New_York",
"enabled": true,
"jitter": 10,
"profile_group_id": "pg123",
"timeslots": ["Monday at 09:00 (id: 1)", "Wednesday at 09:00 (id: 2)"],
"posts_count": 5
}
]
}
queues_get
Get details of a single posting queue including its timeslots and post count.
Parameters:
queue_id(string, required): Queue ID
queues_create
Create a new posting queue with weekly timeslots.
Parameters:
profile_group_id(string, required): Profile group ID to connect the queue to (useprofiles_listto find this)name(string, required): Queue namedescription(string, optional): Optional descriptiontimezone(string, optional): IANA timezone name (e.g.America/New_York). Default:UTCjitter(number, optional): Random offset in minutes (0–60) applied to scheduled times for natural posting patterns. Default:0timeslots(array, optional): Initial weekly timeslots. Each object hasday(0=Sunday through 6=Saturday) andtime(24-hourHH:MMformat)
Example:
{
"profile_group_id": "pg123",
"name": "Weekday Mornings",
"timezone": "America/New_York",
"jitter": 10,
"timeslots": [
{ "day": 1, "time": "09:00" },
{ "day": 2, "time": "09:00" },
{ "day": 3, "time": "09:00" },
{ "day": 4, "time": "09:00" },
{ "day": 5, "time": "09:00" }
]
}
queues_update
Update a queue's settings, timeslots, or pause/unpause it. Changes to timezone or timeslots trigger rearrangement of all queued posts.
Parameters:
queue_id(string, required): Queue ID to updatename(string, optional): New queue namedescription(string, optional): New descriptiontimezone(string, optional): IANA timezone nameenabled(boolean, optional): Set tofalseto pause the queue,trueto unpausejitter(number, optional): Random offset in minutes (0–60)timeslots(array, optional): Timeslots to add or remove. To add:{ "day": 1, "time": "09:00" }. To remove:{ "id": 42, "_destroy": true }.
queues_delete
Delete a posting queue. Posts in the queue will have their queue reference removed but will not be deleted.
Parameters:
queue_id(string, required): Queue ID to delete
queues_next_slot
Get the next available timeslot for a queue.
Parameters:
queue_id(string, required): Queue ID
Returns:
{
"next_slot": "2026-03-11T14:00:00Z"
}
Adding Posts to a Queue
When publishing a post with post_publish, you can add it to a queue instead of scheduling it manually:
queue_id(string, optional): Queue ID to add the post to. The queue will automatically assign a timeslot. Do not use together withschedule.queue_priority(string, optional): Priority level:high,medium(default), orlow. Higher priority posts get earlier timeslots.
Example:
{
"content": "Queued post content",
"profiles": ["twitter", "linkedin"],
"queue_id": "q1abc",
"queue_priority": "high"
}
Comment Management
comments_list
List comments on a published post. Returns paginated top-level comments with nested replies.
Parameters:
post_id(string, required): Post IDprofile_id(string, required): Profile ID to identify which platform's comments to retrievepage(number, optional): Page number, zero-indexed (default: 0)per_page(number, optional): Number of top-level comments per page (default: 20)from(string, optional): ISO 8601 date/time — only comments received at or after this pointto(string, optional): ISO 8601 date/time — only comments received at or before this point
from/to filter on when Postproxy received the comment, not the platform's posted_at (which isn't always populated). A bare date such as 2026-03-25 means that date's start of day. The filter applies to top-level comments only — a comment in range still returns its full replies array.
Returns:
{
"total": 42,
"page": 0,
"per_page": 20,
"data": [
{
"id": "cmt_abc123",
"external_id": "17858893269123456",
"body": "Great post!",
"status": "synced",
"author_username": "someuser",
"like_count": 3,
"is_hidden": false,
"posted_at": "2026-03-25T10:00:00.000Z",
"replies": [
{
"id": "cmt_def456",
"body": "Thanks!",
"author_username": "author",
"parent_external_id": "17858893269123456"
}
]
}
]
}
Comment objects may also include an attachments array (media on the comment — image, video, audio, gif, external, file), each with id, type, url, status, and external_id. Populated for Facebook, Threads, and Bluesky; Instagram, YouTube, and LinkedIn comments are text-only. The array is empty when there is no media.
comments_get
Get a single comment with its replies.
Parameters:
post_id(string, required): Post IDcomment_id(string, required): Comment ID (Postproxy ID or platform external ID)profile_id(string, required): Profile ID
comments_create
Create a comment or reply on a published post. The comment is published to the platform asynchronously.
Parameters:
post_id(string, required): Post IDprofile_id(string, required): Profile IDtext(string, required): Comment text contentparent_id(string, optional): ID of comment to reply to (Postproxy ID or external ID). Omit to comment on the post itself.
Returns:
{
"id": "cmt_ghi789",
"body": "Thanks for the feedback everyone!",
"status": "pending",
"external_id": null
}
The comment is created with status: "pending". Once published to the platform, it becomes "published". If publishing fails, it becomes "failed".
comments_delete
Delete a comment from the platform asynchronously. Supported on Instagram, Facebook, YouTube, and LinkedIn. Not supported on Threads.
Parameters:
post_id(string, required): Post IDcomment_id(string, required): Comment ID (Postproxy ID or external ID)profile_id(string, required): Profile ID
comments_edit
Edit the text of a comment you published, asynchronously. Supported on Facebook and YouTube only. Returns { accepted: true }; the outcome arrives via comment.edited / comment.edit_failed webhooks.
Parameters:
post_id(string, required): Post IDcomment_id(string, required): Comment ID (Postproxy ID or external ID)profile_id(string, required): Profile IDbody(string, required): New comment text
comments_hide
Hide a comment on the platform asynchronously. Supported on Instagram, Facebook, and Threads.
Parameters:
post_id(string, required): Post IDcomment_id(string, required): Comment IDprofile_id(string, required): Profile ID
comments_unhide
Unhide a previously hidden comment. Supported on Instagram, Facebook, and Threads.
Parameters:
post_id(string, required): Post IDcomment_id(string, required): Comment IDprofile_id(string, required): Profile ID
comments_like
Like a comment on the platform asynchronously. Currently only supported on Facebook.
Parameters:
post_id(string, required): Post IDcomment_id(string, required): Comment IDprofile_id(string, required): Profile ID
comments_unlike
Remove a like from a comment. Currently only supported on Facebook.
Parameters:
post_id(string, required): Post IDcomment_id(string, required): Comment IDprofile_id(string, required): Profile ID
Platform Support
| Action | Threads | YouTube | |||
|---|---|---|---|---|---|
| List | Yes | Yes | Yes | Yes | Yes |
| Reply | Yes | Yes | Yes | Yes | Yes |
| Delete | Yes | Yes | No | Yes | Yes |
| Hide/Unhide | Yes | Yes | Yes | No | No |
| Like/Unlike | No | Yes | No | No | No |
Postproxy MCP soruları
Postproxy MCP'yi Claude Code'a nasıl eklerim?
Terminalinizde claude mcp add --transport http postproxy-mcp https://mcp.postproxy.dev/mcp komutunu çalıştırın. Her projede kullanılabilir olması için --scope user ekleyin.
Postproxy MCP'yi Cursor'a nasıl eklerim?
~/.cursor/mcp.json dosyasını açın ve yukarıdaki yükleme bölümünde gösterilen Cursor yapılandırmasını kullanarak sunucuyu mcpServers altına ekleyin.
Gönderileri daha sonraki bir zaman için planlayabilir miyim?
Evet, post_publish aracındaki schedule parametresini kullanarak ISO 8601 formatında planlanmış bir zaman belirtebilirsiniz.
Kimlik doğrulamanın çalışıp çalışmadığını nasıl kontrol edebilirim?
Claude'a "Check my Postproxy authentication status" diyerek bağlantıyı test edebilirsiniz.