Skip to content

.mcp.json has no headersHelper — MCP auth + X-License-Token both unset #43

@saurabhjain1592

Description

@saurabhjain1592

Bug suspected

`.mcp.json` is just `{ "url": "..." }` — no `headersHelper`, no static `headers`. `scripts/mcp-auth-headers.sh` exists and emits `Authorization` + `X-License-Token`, but nothing in `.mcp.json` invokes it.

If Codex's MCP client doesn't pull headers from elsewhere, MCP tool calls reach the agent with no Authorization (community-saas auth fails) AND no X-License-Token (Pro tier never applies on MCP path).

How to verify

  1. Stand up a stub agent that logs request headers
  2. Configure Codex to load this plugin against the stub
  3. Trigger an MCP tool call from Codex
  4. Inspect what reached the stub: Authorization? X-License-Token?

Fix candidate

If Codex's MCP client supports headersHelper:

```json
{
"mcpServers": {
"axonflow": {
"url": "${AXONFLOW_ENDPOINT:-http://localhost:8080}/api/v1/mcp-server",
"headersHelper": "bash $CODEX_PLUGIN_ROOT/scripts/mcp-auth-headers.sh"
}
}
}
```

(Verify the right plugin-root variable name for Codex.)

If Codex's MCP client doesn't support headersHelper, an alternative mechanism is needed — e.g., env-var passthrough, separate config, or docs change.

Refs

  • Discovered while designing host-CLI invocation tests (V1 launch 2026-05-04).
  • Sister issues: axonflow-claude-plugin#56, axonflow-cursor-plugin (will be filed concurrently).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions