Turnfeed logo

ChatGPT connection details

Use this advanced page only when ChatGPT asks for the Turnfeed server URL. Most visitors do not need it; Turnfeed itself runs inside ChatGPT when connected.

How Turnfeed works in ChatGPT

Turnfeed is built for normal ChatGPT conversation. The browser preview is a support route, not the main product surface.

Use chat first

When Turnfeed is connected, ask ChatGPT to catch you up, show active threads, read replies before you answer, publish exact user-supplied words, reply with exact user-supplied words, or update your profile.

Browser preview

The /social route is a standalone support preview of the social feed. ChatGPT remains the main app surface.

Paste this into ChatGPT

Use the server details below only when ChatGPT explicitly asks for connection details.

ChatGPT connection URL

Use this exact URL when ChatGPT asks for the Turnfeed server.

https://turnfeedapp.com/mcp
First test prompts

After connecting, start with the read-only catch-up flow in a fresh ChatGPT chat.

Use Turnfeed. Catch me up on Turnfeed. Use Turnfeed. Read the replies on the most active Turnfeed thread before I reply.
Sign-in mode

Choose No Authentication. In plain language: Turnfeed has no separate sign-in or password. ChatGPT provides a pseudonymous account identifier that keeps your posts and settings attached to you; Turnfeed does not see your ChatGPT email or login.

If ChatGPT unexpectedly asks you to sign in, an old configuration is cached. Remove the old Turnfeed connector and add this URL again.

Transport

The connector uses Streamable HTTP.

Server URL: https://turnfeedapp.com/mcp.

Check the public routes

Use these routes to tell whether the website, ChatGPT connection, or service health is the issue.

Standalone browser preview

Open the browser preview to confirm the support surface is live outside ChatGPT.

https://turnfeedapp.com/social
Human status

Use the status page to confirm whether Turnfeed is online.

https://turnfeedapp.com/status

Operator checks

These checks are for Turnfeed operations after deploys or when ChatGPT seems to show old connector behavior.

1. Verify the live connector

The setup page, health route, and server URL all describe the same chat-first app.

  • Server URL https://turnfeedapp.com/mcp
  • Main surface chat-first
  • Inline ChatGPT visuals disabled
2. Run the refresh check

The refresh workflow verifies the public connector surfaces before reconnecting the server by hand.

npm run connector:refresh -- --origin=https://turnfeedapp.com

That check confirms /health, /mcp, no separate OAuth sign-in, and the chat-first app surface.

3. Reconnect only when needed

If checks pass but ChatGPT still shows older behavior, reconnect the Turnfeed MCP server in ChatGPT and open a fresh chat.

If the refresh check fails, fix the live service first.

Health and support

Use these when setup still fails after the server URL and browser preview look correct.

Authentication mode

Turnfeed currently connects without OAuth or a separate website sign-in. Viewer-specific and public write flows still use Turnfeed session identity, explicit approval, and private safety controls.

No Authentication
Health JSON

Use the raw health payload when you need the public origin, server URL, app surface, and availability status.

https://turnfeedapp.com/health?format=json
Need help?

If the connector still fails after the preview and health page look good, use the support page.

https://turnfeedapp.com/support