ownpost.Get the kit
Documentation/Deploy & connect
DEPLOY & CONNECT

Bring your assistant along.

Give your AI client access to your workspace through a private, authenticated MCP connection.

5 min read

What the connection does

The kit includes a private MCP server, ready to connect to a compatible HTTP MCP client after deployment. Create a connection key and add your workspace endpoint to the client. Your assistant can read context, work with ideas and drafts, prepare replies and news briefs, record results, and propose writing-style changes within the permissions you grant.

The workspace does not include model usage. Your assistant runs in its own client with your own account or API credentials.

1. Create an agent connection

  1. Sign in to your deployed workspace.
  2. Open Settings → Connections → Codex & Claude.
  3. Create an agent connection and choose its scope.
  4. Copy the connection details immediately. The raw key is only shown when created.
Connection details
Name: OwnPost
URL: https://YOUR_DOMAIN/api/mcp
Header name: Authorization
Header value: Bearer xpl_YOUR_GENERATED_KEY

Use the URL of your own deployment. Never paste an API key into a public repository or share a screenshot containing it.

2. Connect and verify

In your client, add an HTTP MCP server using the endpoint and authorization header above. Follow that client’s current setup instructions.

Ask the assistant to read the workspace. Return to Connections and refresh the status to confirm the key has been used. Creating a key alone does not verify a connection.

Give each connection the right access

Use a restricted Assistant connection for bounded scheduled preparation. A full-access connection can perform broader workspace actions. Publication access is a separate explicit grant; connecting an assistant does not authorize every publishing action.

Create separate keys for separate clients. Revoke an unused or compromised key from Connections and create a new one if needed.

Choose permissions and an account deliberately

Use an Assistant-scoped connection for scheduled preparation. It can read context and complete or fail claimed work; it cannot change your routines or create arbitrary drafts. The separate Allow approved publication grant permits eligible publication work only when the owner has also approved it in the workspace.

For multiple accounts, ask the assistant to call list_accounts and pass the returned local profile ID as workspaceAccountId on each relevant call. Calls without an ID use Main account. Switching accounts in the browser does not change the assistant's destination.

A saved routine, selected client, or copied request does not start an AI model or create a client schedule. Run the request in your connected client or configure that client's scheduling separately.

Make the first conversation useful

Try this prompt
Set up my OwnPost posting preferences.
Ask me one question at a time.

Then help me turn one of my ideas into a draft
that sounds like me. Keep it for my review.
Your workspace should feel like yours. Start small, then make it fit.