Can Zenifra MCP change my projects?
No. The current integration is read only and provides no tools to create, change, publish, or delete resources.
Integration for agents
Connect MCP-compatible clients to Zenifra through OAuth and inspect projects, builds, metrics, usage, and costs with read-only access.
MCP provides current account information so agents can answer questions and assist analysis without receiving a shared API key.
Use this address when configuring an MCP-compatible client. Authentication and permissions are requested through the OAuth flow.
https://mcp.zenifra.com/mcpInspect authorized projects, current details, and recent build history.
Read current metrics and follow AI usage within the permissions you grant.
Inspect project billing and transactions only when financial access is authorized separately.
Each authorization keeps identity, organization, resources, and permissions explicit.
Enter the remote endpoint in your compatible MCP client configuration.
Sign in and choose the organization, resources, and access the client needs.
Use the enabled tools to retrieve current Zenifra context in read-only mode.
The client receives only the data and tools included in the current authorization.
MCP retrieves information; it does not create, change, publish, or remove resources.
Authorization scopes the organization, projects, AI keys, and available access.
The connection uses personal OAuth instead of giving the client a generic organization key.
Organization transactions require explicit financial consent in addition to other access.
Direct answers to understand MCP before connecting a client.
No. The current integration is read only and provides no tools to create, change, publish, or delete resources.
No. The connection uses personal OAuth and requests only the access selected during authorization.
Use a client that supports remote MCP and OAuth. Check the official documentation for the current setup procedure for each client.