Connect Tareno to Codex and ChatGPT
Use your own Tareno account through a personal MCP connection, without waiting for a public directory listing.
https://tareno.co/api/mcpCodex
- In Codex, open MCP server settings or the MCP-App creation option when available. Name the connection Tareno and enter the HTTPS endpoint below. Use Streamable HTTP with OAuth, not a manually pasted token.
- Save and choose Authenticate or Connect. Sign in on Tareno and check the account and requested permissions before approving. Alternatively, use the CLI commands below. If you already have an API-key connection named tareno, keep it or remove that configuration deliberately before setting up OAuth; do not mix both credential sources.
- Restart or refresh the client if requested, select Tareno in a new conversation, and run the read-only prompt below. A Tareno login alone does not install the connection on another device or in ChatGPT web.
codex mcp add tareno --url https://tareno.co/api/mcp
codex mcp login tareno
codex mcp get tarenoChatGPT
- In ChatGPT web, open Settings → Security and login and enable Developer mode if your account permits it. Menu labels may differ by version.
- Open ChatGPT Plugins, choose the plus button and the custom MCP creation option, then enter the Tareno endpoint below and select OAuth authentication. Use your own account, not reviewer credentials.
- Complete the redirect to Tareno, sign in, and approve the requested permissions. Install or enable the resulting personal plugin from your personal Plugins list.
- Start a new Work conversation, select Tareno using @, and run the read-only prompt. On mobile, check that the same personal plugin is available and enabled; local Codex settings are not copied into hosted ChatGPT.
First read-only check
Show the social accounts connected to my Tareno account. Read only; do not create, schedule, or publish anything.Account access and safety
Never paste API keys, access tokens, refresh tokens, or client secrets into chat. OAuth credentials are handled by the client. Access remains limited to your Tareno account, permissions, and plan. Scheduling, publishing, scheduled edits, and deletion require approval in Tareno. API keys remain supported for n8n, Make, and compatible clients.
If the connection does not work
If authorization repeats, check which Tareno account you approved. An older connection created before refresh-token support may need one disconnect and reconnect. Do not keep approving in a loop: record the time and the failing request and contact Tareno support. Missing social accounts must be connected in Tareno first; unavailable analytics are not zero performance.