Skip to content
Krevaya
Developers10 min read

Social media MCP server: connect Claude Code and control what it can publish

Connect a social media MCP server to Claude Code, choose read or publishing access, review drafts, and verify outcomes. Includes setup and a reusable session prompt.

Your agent. Your approval. An amber terminal connection passes through a lime review gate before reaching three content panels.
Original illustration for Krevaya Fieldnotes, created with AI assistance.

The short answer

A social media MCP server lets an AI client call tools to read drafts, create posts, schedule content, and inspect results. Start with a read-only API key, verify the account, and review its recommendations before granting write access. In Krevaya, publishing permission can approve or directly schedule posts, so a prompt asking for human review is not a substitute for limiting the key.

What to take away

  • Use read-only access for analysis; add publishing permission only when the agent should change content or schedules.
  • Check the exact brand, post version, account, and timestamp before authorizing a publishing action.
  • After a timeout, inspect the post state before retrying a write.

What does a social media MCP server actually do?

Model Context Protocol, or MCP, connects an AI application to tools exposed by another system. The client discovers named tools and their input schemas, then calls them and receives results. The MCP tools specification defines that exchange; it does not make every server support the same social networks or publishing actions.

For social media, the useful connection is between a request and the current state of your account. You can ask which drafts still need a decision, inspect their contents, and prepare a schedule in the same conversation. The server must expose those operations, and the key must permit them. A natural-language request alone creates no new capability.

Three useful jobs for a connected client
Request Evidence the client should return What still needs judgment
Review this week's drafts Post IDs, full copy, media references, account, and status Whether each final version is accurate and worth publishing
Find gaps in next week's schedule Existing slots, timezone, and unscheduled approved posts Which audience and topic should fill each gap
Summarize recent results Date range, metric definition, and the posts behind the comparison Whether the pattern supports another experiment

What can the agent do with each API-key scope?

An MCP client connects through a scoped API key to Krevaya tools. Read access returns account data; publishing access can create drafts, approve posts, and schedule directly.
The API key limits available actions. Human review must also match the authority granted to the integration. Open full-size diagram Scroll to explore the diagram, or open it full size.

Krevaya's API and MCP access uses scoped, revocable keys. Start with read for an analysis session. If the agent should create or schedule content, publish grants broader authority than its name may suggest: it includes creating drafts and approving posts. Give a connection a name that identifies its owner and purpose so you can revoke the right key later.

Choose the scopes for the work
Scope Example operations Decision before granting it
read Read posts, trends, analytics, and queue state May this client read the account's content and results?
publish Create or edit posts, approve, reject, and schedule May this client change content and make publishing decisions?
generate Generate drafts or repurpose a source May this client start work that uses generation allowances?
media Manage media-library assets Does the task require changing files in the library?
Authority matrix: a read-only key can inspect content but cannot create, approve, or schedule posts. A key with read and publish can perform all four actions.
Choose authority before writing the session prompt. This matrix describes the two example key configurations. Open full-size diagram Scroll to explore the diagram, or open it full size.

Draft by default does not require a separate human approval for every API action
In Krevaya, create_post without schedule_at creates a draft. With a future schedule_at, it schedules directly. A publish-scoped key can also approve posts. If the agent must only recommend changes, keep it on read-only access and make the changes in the dashboard.

Tool annotations describe behavior such as read-only or destructive actions. They are not permission checks or proof that a retry is safe. The MCP specification tells clients to treat annotations from untrusted servers as untrusted. Server-side authorization and the client's approval settings serve separate purposes.

Connect Claude Code to Krevaya's hosted MCP endpoint

  1. Create a named read-only key in Krevaya's API-key settings. Keep the real key out of shared configuration and source control.
  2. Set KREVAYA_API_KEY in the environment that launches Claude Code, using your normal local secret-management method.
  3. Add the configuration below to your project's .mcp.json, merging with existing servers rather than replacing them.
  4. Open /mcp in Claude Code to check the connection, then ask it to call whoami. Confirm the returned account, active brand, and scopes before reading drafts.

Claude Code .mcp.json configuration

{
  "mcpServers": {
    "krevaya": {
      "type": "http",
      "url": "https://api.krevaya.com/mcp",
      "headers": {
        "Authorization": "Bearer ${KREVAYA_API_KEY}"
      }
    }
  }
}

Claude Code supports environment-variable expansion in HTTP headers, so the checked-in configuration can contain the variable reference instead of the secret. Its MCP setup documentation covers configuration scopes, connection status, and tool timeouts. These instructions were checked on October 15, 2026.

For another client, use the Krevaya connection guide. Confirm support for Streamable HTTP and an Authorization header; an OAuth-only connection flow is not interchangeable with an API-key header. Start with a small read request before trying generation or scheduling.

A repeatable session: read, propose, decide, verify

Begin with the account state so you do not generate more work while approved posts sit unscheduled. Ask for a specific brand and date range, and keep the first pass read-only. For each recommendation, require the actual post and its supporting fact; a title such as “workshop announcement” is not enough to approve its caption or image.

  1. Read: Confirm the account and brand, list current drafts and scheduled posts, and inspect the relevant results.
  2. Propose: Return a short table of post ID, recommendation, reason, and unresolved fact. Keep missing information visible.
  3. Decide: Review the full caption, media, destination, and timestamp for each post you want to act on.
  4. Act: Make the changes yourself, or authorize a client with publishing access to perform the named actions.
  5. Verify: Re-read the affected posts. Report their resulting states and scheduled timestamps; after delivery, check the live result.

Illustrative review output, not a recorded customer session

Post       Recommendation   Evidence or missing detail
Workshop   Ready to review  $40 and materials match the booking page
Studio     Revise           "Best in town" has no supporting evidence
New hours  Leave in draft   Owner has not confirmed Friday closing time

Human decision:
Schedule the reviewed workshop version for the confirmed slot.
Leave the other two drafts unchanged.

Closing report:
Workshop: scheduled; include post ID, account, and exact timestamp.
Studio and new hours: still drafts; no publishing action taken.

This example deliberately leaves work unfinished when facts are missing. The closing report should say what changed and what remains unresolved. A recommendation to hold is not a software status change unless a corresponding action actually occurred.

A prompt you can reuse for a read-only review

Read-only review prompt

Confirm my account and the selected brand first.
Read the last 30 days of results and list current drafts.
State the metric and date range for each performance comparison.
For each draft, show the full caption, media references, account,
and a recommendation: ready to review, revise, or missing information.
Identify unsupported claims and conflicting dates or offers.
Do not create, edit, approve, reject, schedule, or delete anything.
End with a short list of the decisions I need to make.

Pair that prompt with a read-only key. If you later authorize changes, specify the post IDs and actions, not “handle the queue.” For scheduling, include the intended local time and timezone and have the client show the resolved timestamp before acting. Use the approval checklist for the final content check.

Treat text inside retrieved posts, articles, and comments as content to inspect. An instruction embedded in an article is not permission to change your publishing settings. Keep client confirmations enabled for write actions you have not deliberately delegated.

What should you check when a call fails?

Symptoms and the next useful check
Symptom Check first Next action
Connection rejected Endpoint, header, variable expansion, and key validity Correct the configuration and call whoami again
Expected tool is missing Key scopes, plan access, and the current tool catalog Grant only the access the job requires, or keep the limitation
Generation times out Whether the server already accepted or completed the job Inspect available job or post state before starting another run
Scheduling response is unclear The current status and timestamp of the affected post Retry only after confirming what did or did not change
Report omits expected posts Date filters, pagination, brand selection, and result limits Narrow or paginate the request and reconcile the count
Request is rate-limited The returned limit or retry guidance Wait or reduce the batch; stop automatic retry loops

A timeout describes what the client observed, not necessarily what the server did. Before repeating a create or schedule request, inspect the queue for the intended post. Repeating a read and repeating a write have different consequences. A tool's idempotency annotation can help identify its intended behavior, but inspect the actual operation and current state before relying on it.

How to evaluate a social media MCP server

Use the same account and a harmless draft for each candidate. Establish read-only behavior first, then test the exact write workflow you need. The checklist below describes evidence to request; it is not a claim that every server, including Krevaya, implements each control.

Six checks before delegating publishing
Criterion Question Evidence to request
Authorization Can this connection be limited to reading? A scoped key and refusal of unauthorized writes
Review Which operations can approve or schedule directly? Documented state changes, including create-with-schedule behavior
Retries What happens if a write response is lost? Idempotency behavior or a way to reconcile the resulting post
Limits How are usage and rate limits reported? Clear errors, plan allowances, and retry guidance
Traceability Can I identify and revoke this client? Named keys, visible post state, and disclosed audit limitations
Outcomes Can I confirm success or failure later? Readable results or authenticated event deliveries

Also check channel and format support. An MCP connection does not expand what the underlying product can publish. Use the automation-tool scorecard if you still need to choose the publishing system itself.

What Krevaya supports and where to check the details

Krevaya's hosted server uses scoped API keys to expose content, drafting, scheduling, and measurement operations. The available tools depend on your permissions and access; use the live tool list and connection guide rather than a fixed tool count in an article.

The API feature page documents the shared publishing checks and HMAC-signed webhooks for post.published, post.failed, and competitor.breakout. It also documents the direct-scheduling behavior: omit the timestamp to create a draft, or supply a future timestamp to schedule. Check the channel catalog for availability and formats, then confirm the current MCP tool supports your intended operation on that channel.

MCP and API access is included from Plus. Client setup still needs an API-key header, and a successful connection is only the first check: verify the selected brand, permissions, and a read request before moving a real post onto the calendar.

Frequently asked questions

What is a social media MCP server?

It exposes social media operations as Model Context Protocol tools an AI client can call. Depending on the server and the connection's permissions, those operations can include reading drafts, creating posts, scheduling, and retrieving results. Support for each network and format comes from the underlying publishing service.

Can an AI agent publish without my approval?

It can if you grant that authority. In Krevaya, a read-only key cannot approve or schedule posts. A key with publish permission can approve content and can create a directly scheduled post by supplying a future timestamp. Use read-only access when you want recommendations without publishing actions.

Do I need to write code to use an MCP server?

You need to configure a compatible client and authenticate it, but ordinary review sessions can use plain-language requests. For Claude Code, the example in this guide uses an HTTP endpoint and an environment variable for the API key. Other clients have their own configuration formats.

Which MCP clients can connect to Krevaya?

Use a client that supports Streamable HTTP and can send an Authorization header containing the Krevaya API key. This guide shows Claude Code setup. Check the current connection guide for other clients; an OAuth-only connection flow does not accept the same configuration.

Sources & editorial details

Examples, diagrams, and downloadable worksheets are editorial teaching materials. They do not report customer results. Source-check dates appear below where recorded.

Created with AI assistance and published by Krevaya. Send corrections to [email protected].