PostFiber for NanoClaw

Made by NanoClaw

Add the MCP server to a NanoClaw agent group, and keep your API key in the OneCLI vault.

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 NanoClaw with the settings below.
Ask NanoClaw to list your PostFiber channels to check the connection.

Run this on the host where NanoClaw runs, with your key in the POSTFIBER_API_KEY environment variable and the ID of the agent group in place of GROUP_ID:

onecli secrets create --name PostFiber --type generic --value "$POSTFIBER_API_KEY" --host-pattern www.postfiber.com --header-name Authorization --value-format "Bearer {value}"
ncl groups config add-mcp-server --id GROUP_ID --name postfiber --url https://www.postfiber.com/mcp
ncl groups restart --id GROUP_ID

NanoClaw keeps credentials out of the MCP settings: the OneCLI vault adds the Authorization header to the requests this agent group sends to PostFiber. If the group does not have the secret yet, grant it as the NanoClaw credentials guide describes.

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 NanoClaw MCP server guide The command line and the skill