MCP integration

Connect Codex to PrompTessor MCP

Set up PrompTessor in Codex settings or with the Codex command line, then complete OAuth authorization.

Verified against the implementation ·

Codex, IDE extension, and ChatGPT desktop app

Codex, the Codex IDE extension, and the ChatGPT desktop app share MCP configuration for the same Codex host. Add PrompTessor once and authenticate with OAuth; a PrompTessor REST API key is not required.

No terminal setup required

Use this method in the ChatGPT desktop app or Codex IDE extension. Both surfaces use the same Codex MCP configuration, so you do not need to repeat the setup in each one.

Open Settings > MCP servers and select Add server.

Name
PrompTessor
Server URL
https://mcp.promptessor.com/mcp
Transport
Streamable HTTP
Authentication
OAuth
  1. 1

    Open MCP settings

    In the ChatGPT desktop app, open Settings > MCP servers. In the Codex IDE extension, open the gear menu and select MCP servers.

  2. 2

    Add a server

    Select Add server, enter PrompTessor as the name, and choose Streamable HTTP as the transport.

  3. 3

    Enter the server URL

    Paste https://mcp.promptessor.com/mcp in the URL field, then save the server.

PrompTessor custom MCP configuration. Leave Bearer token, headers, and environment-variable fields empty, then select Save.
  1. 4

    Restart the client

    Restart the ChatGPT desktop app or select Restart extension in the IDE so the new MCP server is loaded.

  2. 5

    Authenticate

    Select Authenticate beside PrompTessor, then sign in to PrompTessor and approve the OAuth connection in your browser.

After saving, find PrompTessor in the server list and select Authenticate to start OAuth.
  1. 6

    Review and allow access

    Confirm that the page says Connect to PrompTessor, review the requested permissions, and select Allow access. Only the permissions shown on this screen are granted.

Review the requested PrompTessor permissions before selecting Allow access. You can disconnect this Codex client later from PrompTessor Settings.
  1. 7

    Verify the connection

    Open /mcp to confirm that PrompTessor and its tools are available, then ask Codex to check your current PrompTessor usage.

Authenticate is missing after reinstall

Removing and adding PrompTessor again may leave the previous OAuth session stored on the shared Codex host. The client can therefore treat the server as already authenticated even when the saved refresh token has expired or been revoked. Restarting the app or extension does not clear that stored session.

codex mcp logout promptessor
codex mcp login promptessor
  1. 1

    Confirm the saved server

    Run codex mcp list and confirm that promptessor is present. Use the npx fallback when the codex command is not installed globally.

  2. 2

    Clear only the old PrompTessor session

    Run codex mcp logout promptessor. This clears the saved OAuth session for PrompTessor without removing the MCP server configuration.

  3. 3

    Authenticate again

    Run codex mcp login promptessor and complete sign-in in the browser. Alternatively, restart the app or extension after logout and select Authenticate when it reappears.

  4. 4

    Verify the repaired connection

    Open /mcp or run codex mcp list, then ask Codex to call get_usage. If login still fails, copy the exact OAuth error and send it to PrompTessor Support.

Do not delete the complete OAuth credential store

Use mcp logout promptessor instead of deleting Codex OAuth credential files manually. The shared credential store can contain sessions for other MCP servers.