Skip to content
Log inGet started
NIYAM · Codex

Turn a clear request into scoped, reviewable work.

Use NIYAM tools alongside your team’s technical work, with the same project records and permission checks.

Explore the examplePlan your setup

Start with one workflow. Use your own access. Review the result.

Assisted setup · Confirm the supported workflow for your account before relying on it. The examples below explain the review process; they are not a provider recording.

A project like yours

Palm Residence fitout

Actual NIYAM screens
Fictional project · Example prompts

Explore the assisted workflow in four steps
Example prompt
For Palm Residence, what is the next stage and who owns the next task?
01 / 04

Begin with a source record.

Palm Residence has three milestones. Living-room and kitchen carpentry is the current stage; the site record keeps its lead and next task together.

02 / 04

Make the next step specific.

Prepare a follow-up task with the exact site, title, responsible person and due date.

03 / 04

Keep the decision with the team.

Check the person and date. Edit the proposal or leave it unsaved until the team agrees.

04 / 04

Check what was actually saved.

After confirmation, reopen the task in NIYAM and check its saved details.

Daily work in NIYAM
Actual NIYAM site overview for the fictional Palm Residence fitout, showing the lead, target and three milestones.
Actual NIYAM screen · Fictional demo data Open full screenshot (new tab)

This is the NIYAM source view. The steps illustrate a supported review pattern; they do not run an assistant or change a record.

What if I cancel or the connection fails?

Leave a proposal unconfirmed to keep the proposed change unsaved. If a save response is lost, check the record or recover the original request before trying a new one. Reconnect expired access, and use NIYAM’s direct workflow when needed.

Codex + NIYAM

Connect once, then start small.

  1. 1

    Check NIYAM access and choose the Codex host your team uses.

  2. 2

    Add the NIYAM Streamable HTTP endpoint in MCP settings with assisted setup.

  3. 3

    Authenticate as yourself and check the selected workspace and available tools.

  4. 4

    Read a source record first. Review a prepared action, then reopen its saved result in NIYAM.

Connection details for your setup person

NIYAM’s public MCP endpoint uses Streamable HTTP:

https://mcp.niyam.app/mcp

The desktop app, CLI and IDE extension can share MCP configuration on the same Codex host. For a CLI setup:

codex mcp add niyam --url https://mcp.niyam.app/mcp
codex mcp login niyam

Follow the sign-in and consent flow. Your NIYAM membership and grant still decide which tools you can use.

Keep private connection credentials out of prompts, shared screenshots and client-side code.

Official Codex MCP guidance

Documentation checked 8 September 2026. Provider settings and eligibility can change.

Made for a team

Shared records. Individual responsibility.

Each person uses their own identity. The assistant’s access follows their membership, role, site access and connection grant.

Owner

Checks priorities across the sites they can access and decides what needs attention.

Which site decisions need me today?
Explore the role

Supervisor

Works from assigned sites and prepares a task, progress record or attendance update.

Prepare today’s update for my site.
Explore the role

Accounts

Reviews bills, duplicates and payment evidence before operational money records change.

Which bills need review, and what is missing?
Explore the role

Client

Receives selected progress and reports through the client view. Internal records stay with the team.

Review the progress shared with me.
Explore the role

The client example is the shared NIYAM client view. It does not promise a client MCP connection or access to internal records.

Clear before you connect

Access, approval and cost stay visible.

Your access

Use an active NIYAM membership with AI Assistance enabled and a small grant for the agreed tools.

Access and controls

Your decision

Review the exact site, values and effect of each sensitive proposal. Check the saved result before moving on.

How MCP works

Your agreement

Confirm MCP inclusion in your NIYAM agreement and the provider plan separately. API usage and custom integration work can carry separate charges.

Review plans
A few useful answers

Know what to expect.

Will the assistant change records without me?

Reads use the permitted records. Sensitive actions use a prepared proposal and confirmation. Review the exact site, values and downstream effect before you approve.

Does everyone share one connection?

Each person connects with their own identity. NIYAM checks membership, role, site access and the connection’s tool grant. Team rollout and provider availability depend on your workspace policy.

What happens if I cancel or lose the connection?

Leaving a proposal unconfirmed does not save the proposed operational change. If a save response is uncertain, check the record or recover the existing request before creating another one. Reconnect expired or revoked access as appropriate.

Is the AI subscription included in NIYAM?

Check your NIYAM agreement for MCP access and your provider’s plan for the assistant. A ChatGPT or Codex subscription and separately billed API usage are different products. New integrations are scoped separately.

Can I still do the work directly in NIYAM?

Yes. Sites, tasks, materials, money and reviewed reports have their own NIYAM screens. Connected assistance is an additional way to use supported work, subject to setup and permissions.

Is this a recording of ChatGPT or Codex?

The screenshots are actual NIYAM screens with fictional project data. Example prompts explain the intended workflow. They are not recordings of a provider conversation or proof that every provider supports every action.

A manageable first step

Pick one project. Try one useful request.

Agree the workflow and access, connect with support, then check the result together.

Plan your setupExplore the demo project