Devopness MCP
Devopness
Transport not documentedTool names not enumerated6
About Devopness MCP
Devopness’s hosted remote MCP lets AI clients deploy applications and manage servers, environments, projects, and cloud infrastructure through the connected Devopness account.
What you can use it for
- Inspect projects, environments, applications, servers, and deployments.
- Deploy, roll back, restart servers, and manage environment configuration as allowed.
Connection and setup
- Hosting
- remote
- Transport
- Not documented
- Endpoint
- https://mcp.devopness.com/mcp/
- Authentication
- OAuth browser flow or personal access token; Devopness roles/environment scopes constrain actions.
Requirements
- Active Devopness account
- MCP-compatible client
- For PAT auth, create a personal access token in Devopness account settings
- Cloud provider and Git account connections are prerequisites for the corresponding infrastructure/deployment operations
Setup steps
- Add remote Streamable HTTP endpoint https://mcp.devopness.com/mcp/ to a supported client.
- Codex CLI: codex mcp add devopness --url https://mcp.devopness.com/mcp/; complete the OAuth browser flow, or run codex mcp login devopness if needed.
- Claude Code: claude mcp add --transport http devopness https://mcp.devopness.com/mcp/; in Claude Code run /mcp, authenticate and authorize.
- Gemini CLI alternative: configure httpUrl with Authorization Bearer PAT in ~/.gemini/settings.json (or project .gemini/settings.json), then restart and check /mcp.
- Other clients: follow the vendor's client-specific guide at the official MCP docs; use either OAuth or documented PAT header configuration.
- Verify with a read-only request such as listing projects or the current user profile before attempting changes.
Tools
No individual tool names are documented in the reviewed sources.
Current Devopness docs give infrastructure task examples and note an example authenticated instance with about 55 tools, but do not expose exact registered MCP identifiers. Tool visibility is user-role and account dependent; natural-language examples are not treated as tool names.
Limitations and notes
- Actions can change cloud infrastructure and deployments; permissions depend on Devopness role and environment. Keep operational writes review-gated.
Source discrepancies
- Devopness
Original sources
- official publisher documentation
Official client setup confirms hosted endpoint and OAuth.
- official publisher documentation
Official guide notes account-dependent tools and illustrates a 55-tool configured instance.
- official publisher documentation
Publisher or maintainer documentation reviewed 2026-10-28T19:30:00.000Z; capability and connection information recorded, with exact protocol tool identifiers added only when the source publishes them.
- official crawl4ai tool inventory audit
Publisher docs require account OAuth and refer to a user-profile tool by description, but do not publish the tool identifier.
Documentation checked 2026-10-28T19:30:00.000Z. Connection has not been runtime tested.
