AI & MCP

Bring your AI to SchemAlign. Keep SchemAlign in control.

SchemAlign MCP gives compatible AI assistants a governed, read-only path to live SchemAlign context. Developers can use the AI tooling they prefer to understand integrations while SchemAlign remains authoritative for identity, organization access, and permissions.

Read-only today Compatible MCP clients RBAC-aware Organization-scoped
Compatible AI assistant connected via MCP Authorized
“Explain this pipeline.”
Authorized context Project → Pipeline Read-only pipeline metadata and sanitized definition
Signed-in SchemAlign user Current organization access Organization MCP policy
AI with integration context

Give developers useful context where they already work.

Instead of manually copying pipeline details into a separate assistant, authorized users can let compatible MCP clients read the SchemAlign context they are already allowed to see.

01

Inspect organizations and projects

See only the organizations and projects currently available to the signed-in SchemAlign user through MCP.

02

Understand pipelines

List pipeline metadata and inspect sanitized read-only definitions to reason about structure, nodes, and configuration.

03

Document and troubleshoot

Use authorized integration context to aid documentation and troubleshooting without giving the AI assistant mutation or execution capability.

SchemAlign stays authoritative

AI access does not become a shortcut around your controls.

SchemAlign evaluates protected MCP requests using the current user and organization boundaries. An AI connection can remain active while an administrator independently changes organization visibility in SchemAlign.

The AI client is not a separate permission system. Effective access continues to come from the SchemAlign account and organization MCP policy.

Read about MCP permissions
1
Authenticated userThe user signs in to SchemAlign.
2
Organization access & RBACNormal SchemAlign permissions still apply.
3
Organization MCP policyAdministrators choose which read-only MCP capabilities are available.
Effective MCP access Only the authorized intersection is returned.

Read-only by design today

  • Identify the current SchemAlign user and connected AI client
  • List authorized organizations and projects
  • List pipeline metadata
  • Read sanitized pipeline definitions
  • Keep credential secret material outside MCP responses
A controlled first surface

Useful context without mutation or execution.

The current MCP toolset is intentionally read-only. It cannot create, edit, or execute pipelines, change organization membership, alter RBAC, or modify credentials.

This provides a practical surface for AI-assisted understanding, documentation, and troubleshooting while operational changes remain inside SchemAlign.

Client identity

Know what is asking for access.

SchemAlign does not treat an application name alone as proof of identity. When a supported client can be verified during authorization, SchemAlign can present that distinction to the user; other clients remain clearly unverified.

Verified when supported

Client identity at authorization

Compatible AI clients can connect through MCP without being granted trust solely because of a self-reported application name.

Verification is client-specific. A compatible client that cannot be verified is still identified as unverified rather than inheriting trusted branding.
Bring your own AI

Use compatible AI tooling to aid the developers behind your integrations.

See how SchemAlign combines practical integration operations with governed, read-only AI access for higher education teams.