Nakisa MCP is now supported across the Nakisa product suite at no additional cost, with enterprise authentication, role-based permissions, approval workflows, and full audit trails applied to every MCP and agent action.
MONTREAL, June 21, 2026 — Nakisa MCP lets any MCP-compatible AI agent connect to Nakisa applications and take real action: querying data, creating records, updating workflows, completing multi-step processes using plain-language instructions, with no UI navigation required.
Built on an open standard
MCP (Model Context Protocol) is the open industry standard for how AI agents connect to and act inside applications. Any MCP-compatible AI agent can connect to any MCP-enabled application without requiring custom integration.
Because MCP is supported across the entire Nakisa product suite, customers can choose how they want to use AI agents, whether through their preferred AI tool, a custom-built agent, or Nakisa Decision Intelligence, to update workflows, and complete multi-step processes inside Nakisa Lease Accounting, IWMS, and Workforce Planning — using plain-language instructions, with no UI navigation required.
MCP in action across the enterprise
Facility management: A team member uploads a photo of a broken door. The agent inspects the image, identifies the issue, and creates a correctly categorized, routed work order — no manual data entry, no UI navigation required.
Procurement: A user asks for a purchase requisition. The agent creates the PR, generates the related purchase order, creates the invoice, and marks goods as received — an end-to-end workflow, completed from a single instruction. One sentence. Four Systems. Done.
Workforce planning: An HR leader says, "Move Sarah Chen from Marketing Analyst to Senior Marketing Manager, effective July 1, with a 12% salary increase." The agent updates the position, reassigns the reporting line, adjusts compensation, triggers the approval workflow, and notifies payroll — all from one sentence, across modules the leader never has to open.
Real estate / IWMS: A portfolio manager asks, "Which leases hit their renewal notice window in the next 90 days, and what's the financial exposure if we hold over?" The agent scans the active lease portfolio, flags the leases approaching their notice deadline, calculates holdover rent and renewal options against current market terms, drafts notice letters for review, and routes them to the right approvers — turning a multi-day spreadsheet exercise into a single conversation.
Enterprise-grade from the start
Connecting agents is only half the challenge. Securing every action is the harder part, and Nakisa built MCP with that in mind.
Every agent action runs under the initiating user's identity. Role-based access control is enforced, so an agent can only do what its user is permitted to do. Every operation is classified by risk level. Create, update, and delete actions are handled differently from read-only queries. Sensitive operations trigger existing human approval workflows. Every agent action is logged with user identity, timestamp, and operation detail, the same audit record captured for any UI action.
This isn't new infrastructure built for an AI announcement. MCP is exposed on top of Nakisa's existing cloud-native platform — the same authentication, RBAC, and audit foundation that has supported regulated industries, public sector deployments, and Fortune 500 customers for years. While much of the market is now retrofitting security around agent layers built in isolation, Nakisa took the opposite path: the security, identity, and governance model is built-in, and MCP simply inherits it. Agents get no special privileges, no parallel access paths, and no bypass routes.
What's interesting about MCP is that it goes both ways. We publish MCP so external agents can act on Nakisa data. And NDI consumes MCP from other systems, data warehouses, third-party platforms, so it can pull external context into a decision running inside Nakisa. The same protocol, working in both directions.
Faraz Ahmed
Chief Technology Officer at Nakisa
In practice, this means a lease renewal decision inside Nakisa can incorporate live market data from a Snowflake warehouse, a workforce plan can factor in headcount signals from a third-party HRIS, and a procurement workflow can reach into a supplier risk system — without custom integrations, exports, or middleware. Wherever an MCP interface exists, Nakisa can consume it; wherever a Nakisa application runs, external agents can act on it.
MCP frameworks, which expand the interoperability layer through which agents can access and act across multiple systems, accelerate the shift from standalone applications to interconnected agent ecosystems. In this environment, vendors that fail to evolve beyond ‘systems of record’ risk rapid commoditization, while those that position themselves as marketplaces for AI agents (embedding orchestration, distribution and governance) stand to capture disproportionate value.
Reece Hayden
Senior Analyst
Chris Sayers
Senior Manager
Verdantix, Rethinking SaaS Pricing Models In An AI Age, 2026
About Nakisa
Nakisa is a global leader in enterprise decision intelligence and business application software, serving Fortune 500 and public sector organizations across more than 50 countries. Headquartered in Montreal, Canada, Nakisa delivers cloud-native solutions for Lease Accounting, Integrated Workplace Management (IWMS), and Workforce Planning, all powered by Nakisa Decision Intelligence (NDI) — an MCP-enabled AI platform built for regulated, audit-grade environments. For more information, visit nakisa.com.
Frequently Asked Questions
What is Nakisa MCP?
Nakisa MCP is Nakisa's implementation of the Model Context Protocol (MCP), the open industry standard that lets AI agents connect to and act inside enterprise applications. With Nakisa MCP, any MCP-compatible AI agent can query data, create records, update workflows, and complete multi-step processes inside Nakisa Lease Accounting, IWMS, and Workforce Planning — using plain-language instructions, with no UI navigation required.
Which Nakisa products support MCP?
MCP is available across the entire Nakisa product suite, including Nakisa Lease Accounting, Nakisa IWMS (Integrated Workplace Management), Nakisa Workforce Planning, and Nakisa Decision Intelligence (NDI). It is included with existing subscriptions at no additional cost.
Which AI agents work with Nakisa MCP?
Any AI agent that supports the Model Context Protocol can connect to Nakisa. That includes commercial AI tools like Claude, ChatGPT, and Microsoft Copilot, custom agents built against the published Nakisa MCP interface, and Nakisa Decision Intelligence (NDI) — Nakisa's natively MCP-enabled AI platform.
Is Nakisa MCP secure for enterprise and regulated environments?
Yes. Every agent action runs under the initiating user's identity, enforces role-based access control, and is logged in the same audit trail as any UI action. Sensitive operations trigger existing human approval workflows. Nakisa MCP runs on Nakisa's existing cloud-native platform, which supports regulated industries, public sector deployments, and Fortune 500 customers.
How does Nakisa MCP work with external data sources like Snowflake or Databricks?
MCP works in both directions. External AI agents can act on Nakisa data, and NDI can consume MCP from other systems — including data warehouses like Snowflake and Databricks, and third-party enterprise platforms — pulling external context into decisions running inside Nakisa, without custom integrations or middleware.
Media Contact
Rudolf Melik
Head of Marketing & AI Innovation, Nakisa
rudolf.melik@nakisa.com
