Zenifra MCPCopy Anchor Link

Zenifra MCP connects compatible AI clients to your Zenifra account for authorized queries about projects, metrics, builds, usage, and payments. The connection uses browser-based OAuth and remains read-only.

What Zenifra MCP isCopy Anchor Link

The Model Context Protocol (MCP) lets an AI client query information from a connected service. Zenifra's public endpoint is:

https://mcp.zenifra.com/mcp

Zenifra MCP does not create, change, or delete projects. It exposes only the data that the connected account is authorized to view. Authorization selects one organization per connection and lets you review access before confirming.

Before connectingCopy Anchor Link

Have an active Zenifra account, access to the organization you want to query, and a client that supports remote HTTPS MCP servers with OAuth. Always use the complete endpoint ending in /mcp.

You do not need to create a manual token or provide a static credential to the client. Sign-in happens in the browser when the client starts the OAuth flow.

Verify the connectionCopy Anchor Link

The verification flow is the same in every client:

1. Add the HTTPS endpoint ending in /mcp.
2. Start OAuth from the action documented by the client.
3. Sign in to Zenifra in the browser.
4. Select one organization and review the requested access.
5. Authorize the connection.
6. Return to the client and confirm that Zenifra tools are available.
7. Make a first query for the connected context or authorized project list.

Before OAuth is complete, an unauthenticated request returns 401. This is the expected challenge that starts authorization. Consider the connection verified only after OAuth completes and a read-only query returns data that your account can view.

Permissions and reconnectionCopy Anchor Link

Each OAuth connection is associated with the organization selected during consent. To query another organization, reconnect the account and select the new organization when the client starts the flow again.

The consent screen also shows the requested resources and access. Financial access is separate and must be explicitly approved. If you change the organization or access you want, use the client's reconnect action and review consent again.

Next steps and official referencesCopy Anchor Link

• Use the Zenifra CLI for terminal operations, including supported create and change actions.
• Zenifra authentication to learn about the platform's login methods.
• Codex MCP
• Claude Code MCP
• Stable/1.x OpenCode MCP servers
• OpenCode V2 MCP servers
• pi-codemcp
• Hermes Agent MCP