PostFiber for Paperclip

Made by Paperclip

Paperclip hands MCP to the runtime of each agent: add the MCP server to the runtime of the agent that should use PostFiber, with your API key.

Connect over MCP

MCP server address

https://www.postfiber.com/mcp

Create an API key in PostFiber under API keys. It is shown once, and it can be limited to one project, to read-only access or to the permissions you choose.

Create an API key in PostFiber under API keys.
Add the server to Paperclip with the settings below.
Ask Paperclip to list your PostFiber channels to check the connection.

For an agent on the Hermes adapter, add this to ~/.hermes/config.yaml on the host, give the agent your key as a Paperclip secret named POSTFIBER_API_KEY in its env block, and keep mcp in the toolsets of the adapter:

mcp_servers:
  postfiber:
    transport: http
    url: https://www.postfiber.com/mcp
    headers:
      Authorization: "Bearer ${POSTFIBER_API_KEY}"

For an agent on the Claude Code adapter, register the server at user scope, as the OS user that runs the agent, with the command in the Claude Code guide. Claude Code and Hermes are the adapters whose MCP path Paperclip documents.

Try it

List my connected channels.
Draft a post about our launch for tomorrow at 9:00 and save it as a draft.
Show me what is scheduled for this week.

Keep a person in the loop. An agent works with the permissions of the key, or of the person who connected it. Ask it to save drafts or schedule posts, look at the calendar before anything goes out, and give each key only the project and the permissions it needs. A key or a connected app you revoke stops working at once.

Read the documentation of Paperclip MCP server guide The command line and the skill