Bring authorised NIYAM project context and controlled actions into a ChatGPT conversation through one remote MCP connection.
Assisted setup · Founding BetaUse assisted setup in the provider interface, or add the remote endpoint to a server-side API request.
NIYAM guides an eligible user or workspace admin through the remote app setup, then ChatGPT can request only the tools your grant allows.
Add NIYAM as a remote MCP tool in a server-side Responses request and keep approval enabled.
https://mcp.niyam.app/mcpStart on your server. Replace only environment values; keep the permission and confirmation controls visible.
import OpenAI from "openai";
const client = new OpenAI();
const response = await client.responses.create({
model: process.env.OPENAI_MODEL!,
input: "What needs attention across my sites today?",
tools: [
{
type: "mcp",
server_label: "niyam",
server_description: "Permission-scoped NIYAM project operations.",
server_url: process.env.NIYAM_MCP_URL!,
authorization: process.env.NIYAM_MCP_TOKEN!,
require_approval: "always",
},
],
});
console.log(response.output_text);Plain-language prompts that keep source context and review close to the work.
“What needs attention across my active sites today?”
“Find the latest approved material request for Tower A.”
“Prepare a task for the waterproofing issue; do not save it yet.”
Start with the daily jobs your team already understands.
See priorities, risks, unread items and authorized audit activity in chat.
See the daily workflowRead-only by defaultSearch permission-visible work and get evidence-backed answers without changing records.
See how access worksUses only visible evidencePrepare sites, tasks, attendance, materials and plans; approve before NIYAM saves sensitive changes.
Explore field operationsReview, then confirmAsk in chat. NIYAM checks access. You confirm sensitive changes.
MCP never widens what the active NIYAM member can access.
The connection grant must allow each supported tool and permission.
NIYAM prepares the exact change and waits for explicit confirmation.
The short version of access, confirmation and current availability.
NIYAM exposes a remote Streamable HTTP MCP endpoint with OAuth discovery. Founding Beta users receive assisted setup while the durable OAuth rollout is completed.
No. NIYAM enforces the active member, workspace, role, selected connection grant and confirmation boundary for each supported tool.
The repository includes an OpenAI Responses API path using a remote MCP tool and bearer authorisation. Availability still follows the NIYAM beta and access gates.