Macro is a shared workspace that brings email, chat, documents, tasks, AI agents, calls, and customer relationship management into one connected system. It is for teams that want work information and cross-references in a single searchable environment. The catalogue entries provide skills, instructions, MCP integrations, commands, settings, and an agent for working with Macro.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/macro-inc/macroWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/macro-inc/macro/grafana)<a href="https://agentmods.dev/mcp/macro-inc/macro/grafana"><img src="https://agentmods.dev/badge/mcp/macro-inc/macro/grafana/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/macro-inc/macro/grafana"><img src="https://agentmods.dev/badge/mcp/macro-inc/macro/grafana.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
grafana scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What else mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 17 lines scan A 5672bf6d13d4
grafana is an MCP server published in the GitHub repository macro-inc/macro (4,722 stars, last pushed today), licensed AGPL-3.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-02.
Other mcp servers, from other repositories
dataproc
MCP server "dataproc", hosted remotely at dataproc-$gcpregion.googleapis.com, as configured in gemini-cli-extensions/data-agent-kit-starter-pack. Needs 1 environment variable to run.
vastlint
MCP server "vastlint" as configured in aleksUIX/vastlint. Launched with https://github.com/aleksUIX/vastlint/releases/download/v0.9.1/vastlint-mcp-linux.
assay-mcp-server
MCP server "assay-mcp-server" as configured in Rul1an/assay. Launched with https://github.com/Rul1an/assay/releases/download/v6.9.0/assay-mcp-server-v6.9.0.
mcp-pve
Manage Proxmox VE through AI assistants. Runs locally from the @samik081/mcp-pve npm package. Needs 3 environment variables to run.
vllm-ops-mcp
Read-only ops/health MCP server for a local vLLM server (WSL2/systemd-managed): liveness vs real-completion health tiers, GPU/VRAM status, systemd service status, and live serve-flag introspection. No lifecycle-control tools in this release. Runs locally from the vllm-ops-mcp Python package.
prometheus-mcp
MCP server for Prometheus and Alertmanager — query metrics, inspect alerts, explore targets, check cardinality, and investigate incidents (read-only). Runs locally from the prometheus-mcp Python package. Needs 5 environment variables to run.