Connect AI to Sysero.
Keep your documents secure in Sysero.
SyseroMCP is a stateless cloud relay that lets MCP-compatible AI clients work with your Sysero platform — document search, conflict checking, record updates, reports, and workflow creation — without any document content ever leaving your Sysero environment.
Zero document storage
The relay is stateless. No document content, no search indexes, no bearer tokens, and no end-user data is ever persisted on the cloud.
Your identity, your permissions
Users sign in with your own identity provider via OAuth 2.1 and PKCE. Every tool call runs inside Sysero under that user’s own permissions.
No inbound firewall changes
The on-premises agent dials out to the relay on an outbound connection. Nothing needs to be opened up to the public internet at the firm.
How the connection works
A single, standards-based request path from your AI client to your own Sysero installation.
User signs in
The AI client walks the user through an OAuth 2.1 + PKCE flow against your enterprise identity provider.
Relay authenticates
Bearer tokens are validated on every request and the user is resolved to a tenant by their verified email domain.
Request forwarded
The relay forwards the operation over the persistent outbound channel the on-premises agent has already established.
Sysero executes locally
Your on-premises Sysero installation runs the operation under the user’s own permissions and streams the result back.
Everything your AI needs to be useful
Sixteen MCP tools covering search, conflict checking, record creation and editing, reporting, data actions, and projects. Every tool is self-describing and scoped to the user’s own Sysero permissions.
Search and retrieve
sysero_search
Full-text and metadata search across records and their attached documents, returning a shortlist with a permanent record link.
sysero_get_record
Read a record in full — extracted document text, metadata, attached files, and live form state.
sysero_conflict_check
Run a Sysero conflict check against a party, optionally scoped by company and matter type.
Create and update
sysero_start_workflow
Create a new item in a Sysero application and start its workflow.
sysero_edit_record
Save field values onto an existing record and progress the workflow decision it is waiting on.
sysero_upload_document
File a new supporting document against an existing record.
Application schema
sysero_list_applications
List the applications the user is permitted to create items in.
sysero_get_application_fields
Return an application’s field schema — types, options, validation rules, and conditional visibility.
Reports and data actions
sysero_list_reports
List the reports the user is permitted to run, with any runtime filters they accept.
sysero_run_report
Execute a report and return it as a spreadsheet download or as inline data to chart.
sysero_list_data_actions
List the data actions an administrator has explicitly enabled for MCP.
sysero_run_data_action
Run a data action — an external lookup, an email, or another configured operation.
Projects and identity
sysero_list_projects
List Sysero projects — curated groups of matters and items — the user can see.
sysero_get_project_content
Return the items inside a project, including a summary of each one’s attached files.
sysero_who_am_i
Resolve the caller’s identity against every connected Sysero tenant.
sysero_ping
Health check across all connected on-premises installations.
The AI never acts on your data alone
Approval is enforced by the protocol itself, not left to the goodwill of the AI client. The server rejects any write the user has not explicitly sanctioned.
Every write is confirmed first
Before creating an item, editing a record, or uploading a document, the AI must show the user exactly which record it has matched and wait for an explicit yes.
Workflow decisions stay with the user
Where a workflow is waiting on a decision, the AI presents the question and its options. It is never permitted to choose an option on the user’s behalf.
Hidden fields need named approval
A field that a form rule currently hides can only be written after the user has approved that specific field and value. The server refuses anything else.
Administrators decide what is reachable
Only the applications, reports, and data actions explicitly enabled for MCP are exposed — and then only to users whose Sysero role already permits them.
Built for security review
SyseroMCP implements the MCP Authorization Specification (2025-11-25) in full, with data-handling guarantees designed for law firms and their security teams.
Standards implemented
- OAuth 2.1 with mandatory PKCE (S256) — implicit and hybrid flows are not supported
- RFC 8414 Authorization Server Metadata published at the standard well-known path
- RFC 9728 Protected Resource Metadata with zero-configuration discovery
- RFC 7591 Dynamic Client Registration for MCP clients that support it
- HTTPS-only endpoints with HSTS asserted in production
Data handling guarantees
- No document content, search results, or tokens are ever written to disk on the relay
- Transient document and report outputs expire after five minutes and never survive a restart
- Tenant shared secrets are encrypted at rest and compared in constant time
- Fail-closed authorisation — without identity provider config, every request is denied
- Rate limiting, brute-force protection, and log sanitisation applied on every public endpoint