FoPost for DeepSeek Harness

DeepSeek Harness, the open source agent from DeepSeek, connects to remote MCP servers over streamable HTTP. Add FoPost with an API key header and the agent can plan posts, fill the queue, and report on delivery.

Paste this into DeepSeek Harness

Set up FoPost from fopost.com/agents/deepseek

Hosted MCP server
33 networks
API key in a header

All agents

Setup

The agent can write its own config. Give it the link.

Paste the line above into DeepSeek Harness. It reads this page and sets up the connector, then asks for an API key you create in the dashboard. Rather do it by hand? This is the whole config.

Harness MCP client entry

- id: mcp-fopost
  name: '@deepseek-ai/dsh-mcp-client'
  config:
    serverName: fopost
    transport: streamable-http
    url: https://api.fopost.com/mcp
    expandTemplates: true
    headers:
      X-API-Key: '${credential:FOPOST_API_KEY}'

Instructions for AI agentsPlain markdown version

## For AI agents reading this page

You are reading https://fopost.com/agents/deepseek. FoPost schedules and publishes social posts on 33 networks, and its hosted MCP server gives DeepSeek Harness tools for posts, the calendar, the inbox and analytics. Follow these steps to connect DeepSeek Harness to it.

- Server: https://api.fopost.com/mcp
- Transport: streamable HTTP
- Auth: DeepSeek Harness cannot run the OAuth sign-in for a remote server, so it sends an API key in the X-API-Key header. The user creates the key; you never see it in chat.

### 1. Register the server

The official harness MCP client sends static headers only and has no OAuth sign-in, so this client uses an API key. Add this entry to the harness MCP client config (or Settings > MCP in npx @deepseek-ai/dsh web), with the key read from a credential named FOPOST_API_KEY.

Harness MCP client entry:

```
- id: mcp-fopost
name: '@deepseek-ai/dsh-mcp-client'
config:
serverName: fopost
transport: streamable-http
url: https://api.fopost.com/mcp
expandTemplates: true
headers:
X-API-Key: '${credential:FOPOST_API_KEY}'
```

### 2. Sign in

Ask the user to create an API key in the FoPost dashboard (https://fopost.com/dashboard/api-keys) and store it as the FOPOST_API_KEY credential themselves. Never ask them to paste the key into the chat. 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 harness lists the fopost tools, and list_accounts returns data. 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.

### References

- This block as markdown: https://fopost.com/agents/deepseek/agent.md
- Every client: https://fopost.com/agents
- Docs: https://fopost.com/docs

Hosted server

Nothing to run locally. The harness talks to the hosted URL.

Key kept out of config

A credential template means the key lives in the credentials store, not the file.

Approval first

Publishing goes through a proposal you accept. Drafts never go out alone.

Setup

Add the server in Settings

Create an API key in the FoPost dashboard. Start the harness with npx @deepseek-ai/dsh web, open Settings, and add an MCP server with transport streamable-http, the URL https://api.fopost.com/mcp, and an X-API-Key header that reads the key from a credential. The same entry can go in your profile's cordis.patch.yml.

Start free

Terminal

npx @deepseek-ai/dsh web

Scoped key

Start with read scopes, and add publish when you trust the agent.

One workspace per key

The agent sees one workspace, never another client’s accounts.

Check first

Ask the agent to list your connected accounts.

Plan

From a brief to a week of posts

Ask for a week of posts about a launch. The agent drafts each one with create_draft_post, shapes them with draft_post_variants, finds times with get_queue_slots, and finishes with propose_publish for you to accept.

Plan your week

A month of scheduled posts on the publishing calendar

create_draft_post

Every post starts as a draft.

repurpose_url

An article becomes a run of posts.

get_queue_slots

Your next open times.

Check

Ask whether it landed

The read tools report what published, which accounts need a reconnect, and what came back in the inbox.

Start free

Session

> Did yesterday's posts go out?

Agent: list_posts shows 4 of 4 published.
get_account_health: all accounts connected.

list_posts

get_account_health

Which accounts need a reconnect.

list_inbox

Comments and mentions to answer.

DeepSeek Harness questions, answered

Does this work in the DeepSeek chat app?

This page covers DeepSeek Harness, the open source agent that DeepSeek publishes. It is in developer preview, so settings may change between releases.

Why an API key instead of a sign-in?

The harness sends fixed headers to remote servers and does not run a sign-in flow, so it authenticates with a scoped API key.

Where does the key go?

In the harness credentials store. The X-API-Key header reads it through a credential template, so the config never holds the key itself.

Will it post without asking?

No. Publishing goes through a proposal you approve before anything is sent.

Does it use my AI credits?

Only the FoPost tools that write with AI do. Listing and scheduling do not.

Other agents

Run FoPost from DeepSeek Harness

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