Sythe Labs MCP server
Connect a compatible coding agent to your Sythe Labs account, then inspect controls, manage evidence, upload documents, and author policy drafts with your existing access.
One remote server URL, no manual secret.
Use a client that supports remote Streamable HTTP MCP servers and OAuth discovery. The endpoint below automatically matches the staging or production environment serving this page.
https://api.sythelabs.com/api/mcp- 01
Add a standard remote MCP server named Sythe Labs to your coding agent.
- 02
Use the server URL shown below. Do not add an API key, bearer token, or custom header.
- 03
Start the connection. Your client should discover OAuth and open Sythe Labs in a browser.
- 04
Sign in to Sythe Labs and grant access.
- 05
Ask the agent to call grc_list_organizations. A successful organization list confirms the connection.
OAuth uses your existing Sythe Labs identity.
The client discovers the protected resource and authorization server from the MCP URL, opens browser sign-in, and manages access and refresh tokens after consent. Do not paste a bearer token into client configuration.
Agent actions have the same permissions as the signed-in user.
All 22 available tools.
Tool inputs are strict. Unknown fields, malformed IDs, and missing required values are rejected. List tools accept their documented filters and pagination fields.
Discovery and reads
Discover the organizations, people, controls, evidence, and policies you can access.
Organization details
Populate organization profile fields from verified public sources and user-provided information.
Evidence writes
Build an evidence record, connect its artifacts and controls, and request human review.
Policy authoring
Create and edit authored policy drafts while preserving version and review controls.
Document uploads
Move document bytes through a signed upload without sending them through MCP context.
Upload evidence and send it to a human reviewer.
- 01
List organizations and select an organizationId.
- 02
List controls and organization members to resolve controlId, ownerId, and approverId values.
- 03
Create a metadata-only evidence record.
- 04
Prepare the document upload with file metadata and the file's SHA-256 hash.
- 05
Presign the upload, then immediately PUT the exact file bytes to uploadUrl with every requiredHeaders entry.
- 06
Complete the upload using uploadId and the latest uploadAttemptId.
- 07
Attach the completed document, link the required controls, and set the human approver.
- 08
Submit the evidence for review and retain the returned evidence, document, and review-request IDs.
Author HTML drafts with conflict protection.
- 01
List policies in the selected organization, then get the policy you want to edit.
- 02
For inline content, preserve the exact versionId and contentHash returned by grc_get_policy.
- 03
Call grc_update_policy with the full replacement HTML, versionId, and expectedContentHash.
- 04
For large content, download and upload the complete HTML through the returned transfer URLs.
- 05
If the version or hash is stale, get the policy again and decide how to apply your changes to the current draft.
- 06
Leave review, approval, and publication to the existing human workflow.