MCP SETUP
Connect VENRAC to your AI client safely
Choose your client, inspect the tools and permissions it can receive, then copy or download the official secret-free configuration.
WHY INSTALLGive your AI client current, structured business context instead of rebuilding it from fragmented pages on every task.
WHAT IT UNLOCKSPublic discovery reads plus verified provider context and additional role- and plan-eligible tools for authorized accounts.
HOW IT STAYS SAFETenant, entitlement, consent and write-approval checks are enforced by VENRAC, not trusted to the client.
CONNECTION ENDPOINT
Clients connect to /mcp
This is the human installation surface. Machine traffic uses the separate endpoint.
https://venrac.com/mcp
CLIENTS
Choose the surface you use
Every package shows its endpoint, protocol, authentication and write-safety boundary. Downloads contain no embedded token or secret.
supported
ChatGPT / OpenAI
Machine endpointhttps://venrac.com/mcp
- Public preview
- company.get and other public reads
- Authentication
- Anonymous public reads; OAuth for private tools and writes
- Permissions
- Server-bound tenant/provider, entitlement allowlist, consent, policy and approval
- Write safety
- demo.request requires authentication, consent, approval and Idempotency-Key
Machine endpointhttps://venrac.com/mcp
- Public preview
- company.get and other public reads
- Authentication
- Anonymous public reads; OAuth for private tools and writes
- Permissions
- Server-bound tenant/provider, entitlement allowlist, consent, policy and approval
- Write safety
- demo.request requires authentication, consent, approval and Idempotency-Key
Machine endpointhttps://venrac.com/mcp
- Public preview
- company.get and other public reads
- Authentication
- Anonymous public reads; OAuth for private tools and writes
- Permissions
- Server-bound tenant/provider, entitlement allowlist, consent, policy and approval
- Write safety
- demo.request requires authentication, consent, approval and Idempotency-Key
supported via openapi
Gemini
Machine endpointhttps://venrac.com/v1/openapi.json
- Public preview
- company.get and other public reads
- Authentication
- Anonymous public reads; OAuth for private tools and writes
- Permissions
- Server-bound tenant/provider, entitlement allowlist, consent, policy and approval
- Write safety
- demo.request requires authentication, consent, approval and Idempotency-Key
Machine endpointhttps://venrac.com/mcp
- Public preview
- company.get and other public reads
- Authentication
- Anonymous public reads; OAuth for private tools and writes
- Permissions
- Server-bound tenant/provider, entitlement allowlist, consent, policy and approval
- Write safety
- demo.request requires authentication, consent, approval and Idempotency-Key
Machine endpointhttps://venrac.com/v1/openapi.json
- Public preview
- company.get and other public reads
- Authentication
- Anonymous public reads; OAuth for private tools and writes
- Permissions
- Server-bound tenant/provider, entitlement allowlist, consent, policy and approval
- Write safety
- demo.request requires authentication, consent, approval and Idempotency-Key
Machine endpointhttps://venrac.com/.well-known/agent-card.json
- Public preview
- company.get and other public reads
- Authentication
- Anonymous public reads; OAuth for private tools and writes
- Permissions
- Server-bound tenant/provider, entitlement allowlist, consent, policy and approval
- Write safety
- demo.request requires authentication, consent, approval and Idempotency-Key
PUBLIC DISTRIBUTION
GitHub repository
Target: egnaflexinc/venrac-mcp
Publication pending - generated skeleton is ready; no public repository is claimed
README, configs, schemas, examples, compatibility, release metadata and CI are generated under the reviewed distribution package.
BEFORE INSTALLING
Sandbox and permissions check
Runs the local compatibility report. It never installs credentials or grants authority.
TROUBLESHOOTING
If the connection fails
- Use the exact HTTPS endpoint and supported protocol version.
- Public reads work without credentials; private tools require VENRAC OAuth.
- If a write is hidden, check plan entitlement, consent, workspace selection and approval state.
- Reauthorize after token expiry or permission loss. Never paste tokens into config files.
REMOVE OR REVOKE
Remove the connection
- Remove the VENRAC entry from the client.
- Revoke the linked client from VENRAC account settings to cut access immediately.
- Rotate credentials if exposure is suspected.
Uninstalling removes the connection. It does not automatically delete VENRAC customer data.
