---
title: "Connect Cursor to 1Post over MCP"
url: "https://get1post.com/assistants/cursor.md"
canonical_url: "https://get1post.com/assistants/cursor"
last_updated: "2026-10-26"
type: "how-to"
summary: "Add the 1Post MCP server to Cursor: the exact settings, how to sign in or use a key, and a request and reply to check it works."
related: ["https://get1post.com/assistants.md", "https://get1post.com/docs/mcp.md", "https://get1post.com/docs/mcp-oauth.md", "https://get1post.com/docs/api-authentication.md"]
---

# Connect Cursor to 1Post over MCP

Add the 1Post MCP server to Cursor: the exact settings, how to sign in or use a key, and a request and reply to check it works.

Connect Cursor to 1Post by adding the MCP server at https://api.get1post.com/v1/mcp with your API key, or at https://api.get1post.com/v1/mcp/oauth to sign in. Cursor then lists your accounts, schedules posts and reads results with your role. The steps and the exact Cursor settings are below; actions that cancel or reply need confirmation.

## Set up Cursor

1. Make a key. In 1Post, make a key with write scope under Settings, then API keys.
2. Open the file. Edit ~/.cursor/mcp.json to make the server available in every project, or .cursor/mcp.json inside one project.
3. Add the server. Add the entry below under mcpServers and save.
4. Check the connection. Ask the Cursor agent to list your 1Post accounts.

## The Cursor settings

**~/.cursor/mcp.json**

```json
{
  "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.

**Tool call**

```json
{
  "name": "create_post",
  "arguments": {
    "accounts": [
      "ACCOUNT_ID"
    ],
    "text": "Doors open at nine.",
    "schedule_at": "2026-11-02T15:00:00Z"
  }
}
```

**Reply, abridged**

```json
{
  "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](https://get1post.com/docs/mcp.md).

## Questions

**Where should the key live?**

In the global file under your home folder, so it never lands in a repository.

**What can Cursor do once it is connected?**

It can list your accounts, create and update posts, read results and analytics, and cancel or reply when you confirm. It cannot do more than the member behind the key or sign-in.

## Sources

- [Cursor documentation: Model Context Protocol](https://cursor.com/docs/context/mcp), read 2026-10-26

## Related

- [Connect an assistant to 1Post over MCP](https://get1post.com/assistants.md)
- [The MCP server: 1Post docs](https://get1post.com/docs/mcp.md)
- [MCP sign-in with OAuth: 1Post docs](https://get1post.com/docs/mcp-oauth.md)
- [API authentication and keys: 1Post docs](https://get1post.com/docs/api-authentication.md)