
Clara by nOps
io.github.nops-ioPublished by GitHub account nops-iov1.0.0Updated Oct 29, 2026
FinOps assistant: query AWS, GCP and Azure cost, commitments, budgets and reports.
Overview
Clara by nOps is a remote FinOps MCP server that lets an assistant query AWS, GCP and Azure cost, commitments, budgets and reports.
- What you can do
- Query cloud cost data across AWS, GCP and Azure
- Review commitments and budgets
- Retrieve cost reports
- Connect from Claude, Cursor, Gemini CLI or any MCP-compatible client over HTTP
- When to use it
- Useful when you want an assistant to answer questions about multi-cloud spending, commitments, budgets or cost reports without opening the nOps console, and your client can connect to a remote HTTP MCP endpoint with OAuth.
- Requirements
- A remote MCP endpoint at over streamable HTTP; no local package or runtime. OAuth sign-in on first use. A supported client such as Claude, Cursor, Gemini CLI, or manual configuration in another MCP-compatible client.
Installation
In SourceWeft
- Open Clara by nOps in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.nops-io%2Fclara/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"clara-by-nops": {
"type": "http",
"url": "https://mcp.nops.io/"
}
}
}README
Clara MCP Plugins
Install packages and setup guides for connecting Clara to Claude, Cursor, and other AI clients.
Supported clients
Standalone MCP setup
The Claude and Cursor plugins above include the MCP server config and register it automatically. If you're using a different MCP-compatible client, add the following manually:
Claude Code — add to .mcp.json in your project root, or to ~/.claude/mcp.json for global access.
Cursor — add to .cursor/mcp.json in your project root, or to ~/.cursor/mcp.json for global access.
Gemini CLI — gemini extensions install https://github.com/nops-io/clara-mcp
Other clients — consult your client's MCP documentation for where to place server configuration.
Clara is also published to the official MCP Registry as io.github.nops-io/clara (see server.json).
Clara authenticates via OAuth on first use. See docs/auth.md for details.
Authentication
Clara authenticates via OAuth on first use. See docs/auth.md.
Troubleshooting
Source: README.md at commit 87ac8b7
Tools
0Version history
1- v1.0.0LatestOct 29, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts