Mufal for Codex

Your meetings already know what to build.

Bring the full history of every Mufal project into Codex — goals, dated meetings, decisions, action items, speakers, transcripts, and saved context.

Connect Mufal to Codex See how it works

Read-onlyOAuth protectedCloud-synced context

PROJECT CONTEXT

Project Atlas

Ship the new onboarding before Q4

12 linked meetingsMay 8 — July 11, 2026

Decision

Keep progressive onboarding and move billing after activation.

Open action

Faouzi to validate the migration plan before July 18.

Evidence

Product sync — July 11, 2026 · transcript

A project is more than one transcript.

Mufal groups conversations into durable projects. Codex can follow what changed over time, separate confirmed decisions from open questions, and trace every conclusion back to a meeting and date.

Project timeline

Load the goal, persistent memory, meeting count, first and latest meeting, and the complete dated history.

Grounded search

Search project memory, summaries, structured notes, and transcripts without mixing unrelated projects.

Decisions and actions

Surface key points, commitments, owners, contradictions, and unresolved next steps.

Repository context

Compare requirements discussed in meetings with the code that actually exists in the current repository.

HOW IT WORKS

From conversation to working context in three steps.

Organize in Mufal

Attach each meeting to its project. Mufal keeps the goal, durable memory, summaries, and transcripts together.

Connect once with OAuth

Authorize read-only access to your own Mufal account. Codex never receives your password.

Ask from your repository

Name the project and desired outcome. Codex retrieves the right dated evidence before working on the code.

TRY ASKING

Use natural language. Keep the evidence.

Give me the current status of Project Atlas with dated evidence and open actions.

Build a chronological timeline of decisions and flag any contradictions.

Compare the requirements from this project's meetings with the current repository.

Prepare my next meeting: latest decisions, risks, owners, and unresolved questions.

SETUP GUIDE

Connect in less than a minute.

Run these commands in a terminal with Codex installed. Your browser opens the secure Mufal authorization page, then Codex stores the OAuth connection locally.

Run both commands in the terminal.
Sign in to Mufal and approve read-only access.
Open a new Codex task and mention a Mufal project by name.

codex mcp add mufal --url https://admin.mufal.com/api/mcp
codex mcp login mufal

Clear boundaries by design.

The integration only reads meetings and projects from the connected account. Local-only meetings and document contents remain on your device. Mufal tools cannot edit or delete your data.

Questions

Does Codex receive my Mufal password?

No. Authentication uses OAuth. Your password stays with Mufal and Codex receives a scoped access token.

Can Codex change my meetings or projects?

No. Every exposed Mufal tool is read-only and marked as non-destructive.

Why is a meeting missing?

It must be synced to Mufal Cloud and attached to the expected project. Content that exists only on one device is not exposed.

Can it use the context while coding?

Yes. Open your repository in Codex and ask it to compare the implementation with decisions or requirements from a named Mufal project.

Turn every meeting into project memory.

Connect Mufal, open your repository, and let Codex work with the decisions that shaped it.

Set up Mufal for Codex