FoPost pour DeepSeek Harness

## 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