Remote MCP server installs incompletely or not at all, even though initialize and tools/list succeed

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.601.21317

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Codex behaves inconsistently:

sometimes only one tool appears in-session (apmdb_transition_ticket)
in a fresh thread, no Structory MCP tools appear at all
the UI may show Plugin konnte nicht installiert werden

What steps can reproduce the bug?

Feedback ID: 019e8983-6a62-7e32-b7b2-d8b9d42eeae8

Set a Windows user environment variable:
STRUCTORY_MCP_PAT=apmdb_pat_...
Restart Codex completely.
Add a remote MCP server in Codex:
URL: https://mcp.structory.de
Bearer token environment variable: STRUCTORY_MCP_PAT
Observe that Codex may show an installation error:
Plugin konnte nicht installiert werden
In a chat thread, ask which tools are available from the MCP server.

What is the expected behavior?

Codex should successfully install/connect the remote MCP server and expose the full toolset returned by tools/list.

Additional information

Server-side Verification

Direct requests from WSL succeed.

1. Health

curl -i https://mcp.structory.de/health

1. Initialize

curl -i https://mcp.structory.de/mcp \
-H "Authorization: Bearer $STRUCTORY_MCP_PAT" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "initialize",
"params": {
"protocolVersion": "2024-11-05",
"capabilities": {},
"clientInfo": {
"name": "curl-test",
"version": "1.0.0"
}
}
}'
This returns 200 and a valid MCP initialize response.

1. tools/list

curl -i https://mcp.structory.de/mcp \
-H "Authorization: Bearer $STRUCTORY_MCP_PAT" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/list",
"params": {}
}'
This returns the full tool list, including:

apmdb_health
apmdb_list_accessible_projects
apmdb_set_active_project
apmdb_create_requirement
apmdb_create_ticket
apmdb_create_adr
apmdb_create_test_plan
apmdb_create_test_suite
apmdb_create_test_case
apmdb_transition_ticket
apmdb_validate_requirement
apmdb_validate_ticket
apmdb_get_artifact_contracts
Conclusion

The remote MCP server is healthy and returns the correct MCP tool list. The failure appears to be on the Codex client/plugin installation or MCP tool discovery side.