Connect Stackyapper to ChatGPT, Claude, Codex, or another MCP client.

Short answer: ChatGPT uses https://mcp.stackyapper.dev. Claude, Claude Code, Codex, Hatz AI, and other compatible HTTP clients use https://mcp.stackyapper.dev/mcp.

Stackyapper MCP endpoint by client

The portal displays the canonical URL for your workspace under Settings → MCP URLs. Prefer the portal value if your workspace has a verified custom access domain.

Connect Stackyapper to ChatGPT

1. Open ChatGPT’s Apps settings. A workspace administrator may need to allow custom MCP apps and developer mode.
2. Create a custom app named Stackyapper and enter https://mcp.stackyapper.dev.
3. Complete the Stackyapper sign-in and consent flow.
4. Enable the app in a chat, then review any requested tool action before approving it.

ChatGPT’s availability and administrator controls vary by plan and can change while full MCP support remains in beta. Check the official ChatGPT developer-mode guide for the current interface and eligibility.

Connect Stackyapper to Claude

1. Open Claude → Settings → Connectors.
2. Choose Add custom connector. Team and Enterprise owners may first need to add it as an organization connector.
3. Name it Stackyapper and enter https://mcp.stackyapper.dev/mcp.
4. Select Connect, complete Stackyapper OAuth, and enable only the tools relevant to the conversation.

Anthropic currently describes remote custom connectors as beta and recommends connecting only to trusted servers. See Anthropic’s official remote MCP setup guide.

Connect Stackyapper to Claude Code

claude mcp add --transport http stackyapper https://mcp.stackyapper.dev/mcp

Run /mcp inside Claude Code, choose Stackyapper, and authenticate in the browser. Add --scope user if the connection should be available in every project.

Connect Stackyapper to Codex

Add the remote server to ~/.codex/config.toml:

[mcp_servers.stackyapper]
url = "https://mcp.stackyapper.dev/mcp"

Run codex mcp login stackyapper, complete OAuth in the browser, and then restart Codex. Update Codex first if the installed build does not recognize an HTTP url server configuration or the MCP login command.

What happens during OAuth?

Stackyapper shows the workspace, connecting client, and access being granted. After consent, every tool request is still checked against the selected workspace, app ceiling, group grants, user exceptions, and applicable risk controls.

Connecting a client does not expose every catalog app. Only tools that are available, connected, and granted to that user can appear. Review the security and authorization model for the control sequence.

Headless clients and API keys

For automation that cannot complete interactive OAuth, an administrator can create a key in Settings → MCP clients → Create. Send it as a bearer token to https://mcp.stackyapper.dev/mcp. Keys are shown once, inherit the workspace policy, and can be revoked from the same panel.

Troubleshooting

• Client cannot reach Stackyapper: verify the URL. ChatGPT uses the root; general Streamable HTTP clients use /mcp.
• OAuth loops: remove the client connection, add it again, and complete a fresh sign-in.
• No tools appear: ask an administrator to verify the user’s app and tool grants in the selected workspace.
• An app needs attention: reconnect that provider from the Stackyapper Apps page.

Frequently asked questions

Product endpoints and client guidance reviewed July 24, 2026. Client interfaces and plan eligibility are controlled by their respective vendors and may change.