Skip to main content

Codex, Claude Code, Cursor, and Other Agents

Connect OneUp to a coding agent to manage your social accounts and posts using natural-language requests.

Before You Start​

  • Install your preferred agent with support for remote HTTP MCP servers and OAuth.
  • Generate or manage a OneUp API key on the API Access page.

Use this server URL for OAuth connections:

https://feed.oneupapp.io/mcp/oneup

Leave the API key out of the URL. During authentication, OneUp opens a browser page where you enter your API key and approve the agent's access. OneUp stores the key encrypted; the agent receives an OAuth token instead of your API key.

Codex​

Add OneUp from your terminal:

codex mcp add oneup --url "https://feed.oneupapp.io/mcp/oneup"

Follow the browser authentication flow. If authentication does not start automatically, run:

codex mcp login oneup

Check the configuration:

codex mcp list

Start a new Codex session to use OneUp. Codex stores this configuration in ~/.codex/config.toml.

See the official Codex MCP documentation.

Claude Code​

Add OneUp for your user account so it is available across projects:

claude mcp add --transport http --scope user oneup "https://feed.oneupapp.io/mcp/oneup"

Open Claude Code and run:

/mcp

Select oneup and authenticate. Complete the browser flow to enter your OneUp API key and approve access.

To check the connection from your terminal:

claude mcp list

See the official Claude Code MCP documentation.

Cursor​

Add the following entry to ~/.cursor/mcp.json for access across projects, or .cursor/mcp.json for one project:

{
  "mcpServers": {
    "oneup": {
      "url": "https://feed.oneupapp.io/mcp/oneup"
    }
  }
}

If the file already contains other MCP servers, add oneup under the existing mcpServers object.

Open Cursor's MCP settings, enable oneup, and select its authentication option. Complete the browser flow to enter your OneUp API key and approve access. Setting labels can vary by Cursor version.

See the official Cursor MCP documentation.

Other MCP Clients​

In your client's MCP settings:

  1. Add a remote server named OneUp.
  2. Select Streamable HTTP (sometimes labeled HTTP) as the transport.
  3. Enter https://feed.oneupapp.io/mcp/oneup as the server URL.
  4. Select OAuth authentication if prompted, then complete the OneUp browser flow.

OneUp supports dynamic OAuth client registration, HTTPS callbacks, local HTTP loopback callbacks, and the desktop callback schemes cursor, vscode, vscode-insiders, windsurf, and claude. Clients using other desktop schemes or requiring a different registration mechanism may need additional setup. MCP support alone does not guarantee support for remote HTTP servers or OAuth.

For ChatGPT-specific instructions, see ChatGPT Setup.

Direct API-Key Connections​

For clients configured to use a direct API key, the alternative URL is:

https://feed.oneupapp.io/mcp/oneup?apiKey=YOUR_API_KEY

Replace YOUR_API_KEY with your OneUp API key and URL-encode special characters. Keep the full URL private: it contains your credential and may be stored in the client's configuration or shell history. Some clients automatically detect OAuth even when an API key is in the URL; use the OAuth setup above for those clients.

Check Your Connection​

Start a chat and ask:

Use OneUp to list my connected social accounts.

If the agent can list your accounts, both authentication and tool access are working.

Troubleshooting​

OneUp Is Already Configured​

To replace an older Codex configuration, remove it before running the add command again:

codex mcp remove oneup

For the user-scoped Claude Code configuration in this guide:

claude mcp remove --scope user oneup

In Cursor, edit the existing oneup entry instead of adding a duplicate.

Authentication Fails​

  • Update your MCP client and retry authentication.
  • Use the OAuth URL without ?apiKey=....
  • If registration reports invalid_redirect_uri, check the callback type against the supported types above. Include the client name, version, and error when contacting support; do not include your API key or OAuth tokens.
  • If the connection succeeds but tools are unavailable, start a new agent session and check that OneUp is enabled.

Manage Access​

Review and disconnect OAuth connections from the MCP Connections page. Removing the local server configuration stops that client from using the configured connection; use the connections page to revoke its access on OneUp.