Set up Cursor
- 01
Make a key
In 1Post, make a key with write scope under Settings, then API keys.
- 02
Open the file
Edit ~/.cursor/mcp.json to make the server available in every project, or .cursor/mcp.json inside one project.
- 03
Add the server
Add the entry below under mcpServers and save.
- 04
Check the connection
Ask the Cursor agent to list your 1Post accounts.
The Cursor settings
{
"mcpServers": {
"1post": {
"url": "https://api.get1post.com/v1/mcp",
"headers": {
"Authorization": "Bearer op_live_YOUR_KEY"
}
}
}
}The global file serves every project; the project file serves one. Keep a project file out of version control when it holds a key.
A request and its reply
Once connected, Cursor 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.