Skip to content

Connect Codex to AIMake with MCP

Give each Codex session the repository knowledge, decisions and unfinished work your project has already accumulated.

Give this to your agent

Give this to your agent

Before you start: Start with a working Codex CLI and an AIMake project in an active paid workspace. Use your harness’s repository access to bring source-linked context into AIMake. Compare plans.

Open Codex from your repository, then copy everything in the box below.

PROMPT FOR CODEX

Copy everything below

Read https://www.aimake.dev/agents/codex and https://www.aimake.dev/skills/aimake-mcp/SKILL.md. Follow the Codex setup steps to connect AIMake and install the skill in this repository. Preserve existing configuration. Start the browser authorization flow, show me its URL, and keep the login process running while I authorize. Wait for that process to complete, checking it periodically and giving brief progress updates; do not end the turn just because authorization is pending. Never approve access on my behalf. If login fails, expires, or is cancelled, report the exact blocker and help me retry. After successful login, verify access with an actual AIMake MCP call; configuration alone is not verification. If this session cannot load the tools, explain that limitation and the restart step. Once connected, use aimake-mcp to list my projects and confirm the right one with me. Prepare the work, recover decisions and unfinished tasks, and recommend one bounded next step. Save the planning outcome; wait for my decision before implementing.

What happens next: You authorize access in your browser and choose the organization, projects and permissions. Never paste tokens into chat.

Reference: Read the AIMake skill

Codex stores MCP configuration in its config.toml. AIMake authorization scopes project records; your Codex permissions govern code execution and tools.

Manual setup

  1. Add AIMake

    Run these commands in a terminal on the machine running Codex.

    codex mcp add aimake --url https://api.aimake.dev/mcp
codex mcp login aimake

  2. Authorize access

    Complete the browser flow. Choose the AIMake organization, projects and permissions to grant. Keep access tokens out of prompts.

  3. Check the connection

    Run codex mcp list to check configuration. In Codex, ask AIMake to list your projects; a successful response verifies access.

  4. Load the project skill

    Read the public skill, then save its complete contents at the path below in your repository. Start Codex there and ask it to use aimake-mcp.

    .agents/skills/aimake-mcp/SKILL.md
    Read the AIMake skill

What appears in AIMake

AIMake retains the work session and tool activity. Existing wins and tasks keep their state. Once you authorize implementation, ask Codex to attach actual PR and test evidence to the task for review in AIMake.

Troubleshooting

No projects
Check the authorized account, project selection, membership and active workspace subscription. Reauthorize if access changed.
Login incomplete
Rerun codex mcp login aimake and complete the browser flow on the machine running Codex.
Skill missing
Check the repository path and exact SKILL.md filename. Start a fresh session after installation.
Write rejected
Follow the tool error: prepare expired sessions again, authorize needed scopes, or supply the required review/proof. Only a human can provide a waiver.

Further reading