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
Zenifra MCP for agents and assistants
Connect MCP-compatible clients to Zenifra with OAuth and inspect projects, builds, deployments, logs, metrics, health, usage, and costs with read-only access.
Zenifra context for your agent
MCP provides current account information so agents can answer questions and assist analysis without receiving a shared API key.
Zenifra MCP remote endpoint
Use this address when configuring an MCP-compatible client. Authentication and permissions are requested through the OAuth flow.
MCP URL
https://mcp.zenifra.com/mcpProjects, builds, and deployments
Inspect authorized projects, current details, build history with logs, the latest build failure, and deployments.
Logs, health, and incidents
Read and search application logs, and check health, healthcheck failures, recent incidents, and running instances.
Metrics, network, and autoscaling
Read current metrics, network traffic, and autoscaling settings and events.
Storage and Valkey
List Storage buckets and files, and check the status of Valkey projects.
AI usage
Follow AI keys and usage within the permissions you grant.
Costs and transactions
Inspect project billing and transactions only when financial access is authorized separately.
Connection through OAuth
Each authorization keeps identity, organization, resources, and permissions explicit.
01
Add the endpoint
Enter the remote endpoint in your compatible MCP client configuration.
02
Authorize access
Sign in and choose the organization, resources, and access the client needs.
03
Ask through the agent
Use the enabled tools to retrieve current Zenifra context in read-only mode.
Scoped access
The client receives only the data and tools included in the current authorization.
Read only
MCP retrieves information; it does not create, change, publish, or remove resources.
Selected resources
Authorization scopes the organization, projects, AI keys, and available access.
No shared API key
The connection uses personal OAuth instead of giving the client a generic organization key.
Separate financial permission
Organization transactions require explicit financial consent in addition to other access.
MCP questions
Direct answers to understand MCP before connecting a client.
Do I need to provide an organization API key?
No. The connection uses personal OAuth and requests only the access selected during authorization.
Which clients can I use?
Use a client that supports remote MCP and OAuth. Check the official documentation for the current setup procedure for each client.