# Bring your assistant along.

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

Canonical: https://ownpost.fyi/docs/mcp

## What the connection does

The kit includes a private MCP server, ready to connect to a compatible HTTP MCP client after deployment. Download a client package from /settings/plugins and authorize it through browser sign-in, or configure a separate connection key manually.

OwnPost supports browser OAuth for ChatGPT and compatible desktop clients, including public-client registration. The ChatGPT plugin references a registered MCP app; desktop packages include your workspace endpoint. Installing either package still requires you to authorize and verify access.

Your external assistant runs in its own client with your own account or API credentials. Separately, Write in OwnPost uses your saved OpenAI or Anthropic API key for in-app options. Both methods can stay configured; model usage is not included in the kit.

[Choose your client’s installation steps](https://ownpost.fyi/docs/plugins#choose-installation)

[Connect ChatGPT with OAuth](https://ownpost.fyi/docs/guides/connect-chatgpt)

## 1. Choose browser sign-in or a connection key

For the generated plugin, follow its browser sign-in instructions and approve access with your OwnPost owner login. Use the manual steps below when your client needs a bearer key, or when you want a separate connection with a chosen scope.

1. Sign in to your deployed workspace.

2. Open Settings → Connections → AI writing → AI assistant and choose your client.

3. Create an agent connection and choose its scope.

4. Copy the connection details immediately. The raw key is only shown when created.

```
Name: OwnPost
URL: https://YOUR_DOMAIN/api/mcp
Header name: Authorization
Header value: Bearer ownpost_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.

## 3. Add the OwnPost skills and your voice

MCP gives your agent authenticated access to your workspace. OwnPost skills supply the workflows for setup, writing, planning, and review. Install the ownpost skill in a client that supports agent skills; specialist skills are optional shortcuts.

Select ownpost in your client’s skill picker or supported invocation menu, then describe the result you want in ordinary language. The OwnPost plugin includes the entry and specialist skills, or you can install the entry skill directly. Installing instructions does not connect your account or grant publishing permission.

Save Voice, Topics, and Examples & Hooks in Settings → Writing style. Your agent uses that context before drafting and follows the built-in editorial review guidance. The writing-profile skill can make explicit owner-requested edits; inferred preferences still become pending Learning Notes for review.

Use the blog skills to start, pause, resume and revise articles, prepare editions and record manual publication. The prompt library supplies requests for these workflows; copied prompts still need to be run in your connected client.

```
Use the ownpost skill to turn my launch notes into three X drafts in my saved writing style. Save them for my review.

Launch notes: [paste your notes]
```

[OwnPost skills and installation](https://ownpost.fyi/docs/skills)

[Install the OwnPost plugin](https://ownpost.fyi/docs/plugins)

[Blog writing and editions](https://ownpost.fyi/docs/guides/blogs)

[Prompt library](https://ownpost.fyi/docs/guides/prompt-library)

[Assistant examples using skills](https://ownpost.fyi/docs/guides/assistant-workflows)

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

Routines track recurring tasks and completion. Saving a routine or marking an item done does not start an AI model or create a client schedule. Run preparation requests in your connected client or configure that client's scheduling separately.

## Make the first conversation useful

```
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.
```

## Related

- [Previous: Deployment reference](https://ownpost.fyi/docs/deployment)
- [Next: Integrations overview](https://ownpost.fyi/docs/integrations)