Docs · Integrations

Use Codex CLI and Claude Code with Feature1 MCP

Connect your preferred coding agent to Feature1 workflows and run AC-by-AC implementation with full platform context.

Prerequisites

  • Active Feature1 account with your workspace subdomain (for example acme.feature1.ai)
  • Access to your MCP endpoint: http://{subdomain}.feature1.ai/mcp
  • Logged into your CLI agent environment (Codex CLI or Claude Code)

1) Codex CLI Setup

Codex CLI
$ codex mcp add feature1 --url http://{subdomain}.feature1.ai/mcp
$ codex
> /mcp

You should see feature1 with tools listed (for example load_workflow, get_next_ac, implement_ac, create_feature_draft).

2) Claude Code Setup

Claude Code
$ claude mcp add --transport http feature1 http://{subdomain}.feature1.ai/mcp
$ claude
> /mcp

After connecting, use /mcp to confirm Feature1 tools are available.

3) Recommended Workflow

Plan

Create or load formal work in Feature1 (create_feature_draft, create_user_story_draft, load_workflow).

Implement

Use get_next_ac → generate_ac_prompt → implement_ac in Driver-Navigator mode.

Finalize

Mark and approve criteria (mark_implementation_done, approve_criterion), then open PR via create_pr.

Troubleshooting

  • No tools listed: verify MCP URL and check tools/list response on the MCP server.
  • 401 Invalid token: refresh JWT and reset FEATURE1_MCP_BEARER_TOKEN.
  • Works local, fails in Docker: use container network hostnames (for example http://mcp-server:3004/mcp from backend container).
  • SSL host mismatch: ensure MCP backend API base URL and cert hostname match.