Use the same remote NIYAM MCP endpoint from a Claude conversation while NIYAM continues to enforce workspace scope and confirmation.
Assisted setup · Founding BetaUse assisted setup in the provider interface, or add the remote endpoint to a server-side API request.
An eligible Claude user or workspace owner adds NIYAM's HTTPS endpoint, then enables the connector in a conversation.
Declare the remote server and matching MCP toolset in a server-side Claude Messages request.
https://mcp.niyam.app/mcpStart on your server. Replace only environment values; keep the permission and confirmation controls visible.
import Anthropic from "@anthropic-ai/sdk";
const client = new Anthropic();
const message = await client.beta.messages.create({
model: process.env.CLAUDE_MODEL!,
max_tokens: 1024,
messages: [
{
role: "user",
content: "Summarise today's site risks and cite the source records.",
},
],
betas: ["mcp-client-2025-11-20"],
mcp_servers: [
{
type: "url",
url: process.env.NIYAM_MCP_URL!,
name: "niyam",
authorization_token: process.env.NIYAM_MCP_TOKEN!,
},
],
tools: [{ type: "mcp_toolset", mcp_server_name: "niyam" }],
});
console.log(message.content);Plain-language prompts that keep source context and review close to the work.
“Summarise today's site risks and show the source records.”
“Prepare this reviewed bill as an expense; wait for my approval.”
“Draft a project update from the latest reviewed records.”
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 one remote MCP endpoint for Claude custom connector and Messages API MCP connector paths. Founding Beta users receive assisted setup today.
No. NIYAM enforces the active member, workspace, role, selected connection grant and confirmation boundary for each supported tool.
No. Supported sensitive finance actions are prepared first and require an explicit confirmed action before NIYAM saves them.