Set up OpenCode
- 01
Open the file
Edit opencode.json in your project or your global OpenCode config.
- 02
Add the server
Add the remote entry below under mcp. Turn off the automatic sign-in when you use a key.
- 03
Or sign in
Use the sign-in address with no headers, then run opencode mcp auth 1post.
- 04
Check the connection
Start OpenCode and ask it to list your 1Post accounts.
The OpenCode settings
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"1post": {
"type": "remote",
"url": "https://api.get1post.com/v1/mcp",
"enabled": true,
"oauth": false,
"headers": {
"Authorization": "Bearer op_live_YOUR_KEY"
}
}
}
}{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"1post": {
"type": "remote",
"url": "https://api.get1post.com/v1/mcp/oauth",
"enabled": true
}
}
}OpenCode detects a sign-in requirement from a 401 reply and handles it, so the sign-in entry needs no oauth block.
A request and its reply
Once connected, OpenCode sends tool calls like this one when you ask it to schedule a post. Account ids come from list_accounts.
{
"name": "create_post",
"arguments": {
"accounts": [
"ACCOUNT_ID"
],
"text": "Doors open at nine.",
"schedule_at": "2026-11-02T15:00:00Z"
}
}{
"id": "POST_ID",
"status": "scheduled",
"scheduled_at": "2026-11-02T15:00:00.000Z",
"accounts": [
{
"account_id": "ACCOUNT_ID",
"status": "queued"
}
]
}What the connection can do
| Tool | What it does | Needs |
|---|---|---|
| list_accounts | Lists connected accounts and their state | Read |
| create_post | Saves, schedules or publishes a post | Write |
| get_post | Reads one post and the result for each account | Read |
| cancel_post | Cancels a post that has not started | Write and confirm: true |
The connection acts with the role of the member who made the key or signed in, so a contributor's posts still go to review. The full tool list is on the MCP page.