FoPost per goose

## For AI agents reading this page

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

- Server: https://api.fopost.com/mcp
- Transport: streamable HTTP
- Auth: OAuth sign-in in the user's browser. Do not add an API key or an Authorization header; goose discovers the sign-in from the server.

### 1. Register the server

Run goose configure, choose Add Extension, then Remote Extension (Streamable HTTP), and enter the name fopost and the URL https://api.fopost.com/mcp. In the desktop app: Extensions in the sidebar, then Add custom extension. To try it for one session only:

Terminal:

```
goose session --with-streamable-http-extension "https://api.fopost.com/mcp"
```

### 2. Sign in

goose registers itself and opens a browser window for the user to sign in. 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 fopost extension is enabled under Extensions, and asking goose which fopost tools it has returns them. 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.

### No browser (headless machines only)

Use this only when the machine has no browser to sign in with. Ask the user to create an API key in the FoPost dashboard (https://fopost.com/dashboard/api-keys) and to put it in the config themselves, then run the local package over stdio:

~/.config/goose/config.yaml:

```
extensions:
  fopost:
    name: fopost
    type: stdio
    cmd: npx
    args: ["-y", "@fopost/mcp"]
    envs:
      FOPOST_API_KEY: your-api-key
    enabled: true
```

### References

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