Every MCP Tool, by Product

One MCP server carries both ZopDev products, so a single connection reaches 289 tools. This page names all of them, grouped by the product they answer for and split into what reads and what writes. For how to connect, see MCP Server: A Practical Guide.

Your own list is shorter than this one, and deliberately so. tools/list is filtered at the gateway: a tool is advertised if and only if the gate would let you invoke it, so nothing you can see will fail with a permission error when you call it. Ask your assistant what ZopDev tools it has and you get the answer for your token, not the catalogue.

The catalogue at a glance

Category	Tools	Read	Write
Introspect	4	4	0
Explore	24	20	4
Cost	58	48	10
Optimize	21	10	11
Operate	55	24	31
Govern	94	36	58
Ship	24	14	10
Diagnose	9	9	0
Total	289	165	124

Those are ZopDev’s own categories, regenerated on every server release. The rest of this page groups the same 289 tools a second way, by the product you are likely to be asking about.

Product	Tools	Read	Write
ZopNight	139	91	48
ZopDay	38	20	18
Shared platform	112	54	58
Total	289	165	124

Reads need no permission beyond your role. Writes need three things at once: your organisation’s write-access setting must admit the tier, your live role must permit the underlying action, and your token must carry the matching capability. Any one missing is a refusal. The tiers are set out in Read and write.

ZopNight tools

Cloud cost and FinOps: what is running, what it costs, what is wasted, and when it should be switched off. 139 tools: 91 read, 48 write.

Inventory

Resources and their parent/child topology, filters, discovery status, per-account permission verdicts, live Kubernetes objects, manifests, pod logs, blast-radius analysis.

Reads (25)
`count_cloud_accounts`	`get_resource_count`
`get_blast_radius`	`get_resource_filters`
`get_cloud_account`	`get_resource_metrics`
`get_cloud_account_permissions`	`get_resource_overview`
`get_discovery_status`	`get_resource_summary`
`get_discovery_summary`	`get_resources_by_ids`
`get_k8s_manifest`	`get_resources_last_synced`
`get_k8s_resource`	`list_budget_cloud_account_entities`
`get_kubernetes_cluster_workloads`	`list_cloud_accounts`
`get_live_metrics`	`list_k8s_events`
`get_pod_logs`	`list_k8s_resources`
`get_resource`	`list_resources`
`get_resource_activity`

Writes (6)
`add_resource_to_group`	`restart_k8s_workload`
`delete_k8s_resource`	`set_group_start_stop_order`
`remove_resource_from_group`	`update_k8s_manifest`

Cost

Overview, trends, breakdowns by provider, region, account, service and resource; per-resource cost history; billing sync health; Kubernetes cluster cost splits.

Reads (12)
`get_billing_sync_status`	`get_cost_trends`
`get_cost_breakdown`	`get_costs`
`get_cost_by_provider`	`get_kubernetes_cluster_cost_breakdown`
`get_cost_by_resources`	`get_kubernetes_cluster_costs`
`get_cost_by_tag`	`get_report_snapshots`
`get_cost_overview`	`get_resource_cost_history`

Writes (0). None in this group.

Attribution

Showback by team and by tag, tag coverage and values, smart tags, unit economics.

Reads (8)
`get_cost_by_team`	`get_team_cost_detail`
`get_tag_cost_trends`	`get_team_cost_trends`
`get_tag_value_resources`	`get_unit_economics`
`get_tag_values`	`list_smart_tags`

Writes (9)
`accept_smart_tag`	`ingest_unit_metric_values`
`apply_smart_tags`	`revoke_smart_tag`
`create_unit_metric`	`test_pull_unit_metric`
`delete_all_unit_metric_values`	`update_unit_metric`
`delete_unit_metric`

Waste

Recommendations with the evidence that fired them, per-rule and per-resource summaries, the rule catalogue, anomalies with root-cause analysis.

Reads (12)
`count_recommendation_resources`	`get_recommendation_filters`
`count_recommendation_rules`	`get_recommendation_rules`
`count_recommendations`	`get_recommendation_summary`
`get_anomalies`	`get_recommendations`
`get_recommendation`	`list_recommendation_resources`
`get_recommendation_by_provider`	`preview_remediation`

Writes (5)
`apply_recommendation_policy`	`start_remediation`
`export_recommendations`	`update_recommendation_status`
`share_recommendation`

Scheduling

Schedules and cron windows, resource groups, overrides and override candidates, state history, schedule success rates, manual start and stop.

Reads (16)
`count_schedules`	`get_schedule`
`get_action`	`get_schedule_success`
`get_budget_spend_by_resource_groups`	`get_state_history`
`get_latest_bulk_action`	`list_budget_resource_group_entities`
`get_override`	`list_events`
`get_override_candidates`	`list_overrides`
`get_resource_group`	`list_resource_groups`
`get_resource_group_schedules`	`list_schedules`

Writes (17)
`attach_group_to_schedule`	`delete_schedule`
`attach_resource_to_schedule`	`detach_group_from_schedule`
`bulk_start_resources`	`detach_resource_from_schedule`
`bulk_stop_resources`	`schedule_event_readiness`
`create_override`	`start_resource`
`create_resource_group`	`stop_resource`
`create_schedule`	`update_resource_group`
`delete_override`	`update_schedule`
`delete_resource_group`

Automation

Autoscaler policies, events, smart defaults and required permissions; event-readiness plans, checks and cost previews.

Reads (18)
`count_autoscaler_policies`	`get_event_readiness`
`count_event_readiness_plans`	`get_event_readiness_check`
`get_autoscaler_events`	`get_event_readiness_logs`
`get_autoscaler_policy`	`get_event_readiness_plan`
`get_autoscaler_required_permissions`	`list_autoscaler_policies`
`get_autoscaler_smart_defaults`	`list_cloud_scaling_policies`
`get_event_cost_estimate`	`list_event_readiness`
`get_event_db_impact`	`preview_event_cost`
`get_event_db_sizing`	`preview_event_readiness`

Writes (11)
`apply_autoscaler_policy`	`pause_autoscaler_policy`
`cancel_event_readiness`	`remove_autoscaler_policy`
`create_autoscaler_policy`	`resume_autoscaler_policy`
`create_event_readiness`	`update_autoscaler_policy`
`delete_autoscaler_policy`	`update_event_readiness`
`delete_event_readiness`

ZopDay tools

Build and deploy: projects, services, environments, deploys, databases and cluster provisioning. 38 tools: 20 read, 18 write.

Delivery

Projects, environments, services, deploys, infrastructure, provisioning jobs, service config and diagnostics.

Reads (20)
`check_eligibility`	`list_branches`
`diagnose_service`	`list_deploys`
`get_autoscaler_infrastructure_status`	`list_environments`
`get_infrastructure`	`list_infrastructure`
`get_project_stats`	`list_jira_projects`
`get_provisioning_job_overview`	`list_projects`
`get_service_config`	`list_provisioning_jobs`
`get_service_events`	`list_repositories`
`get_service_overview`	`list_service_datastores`
`get_service_url`	`list_services`

Writes (18)
`connect_github`	`deploy_service`
`create_autoscaler_infrastructure`	`redeploy_service`
`create_environment`	`remove_service_database`
`create_project`	`retry_provisioning_job`
`create_provisioning_job`	`rollback_service`
`create_service_database`	`set_auto_deploy`
`delete_project`	`set_service_env_vars`
`delete_provisioning_job`	`update_service_config`
`delete_service`	`wait_for_deploy`

Shared platform tools

The platform plane underneath both products. These answer for your whole organisation, whichever product you came for. 112 tools: 54 read, 58 write.

Governance

Budgets and live spend, audit logs, the RBAC policy catalogue and effective permissions, tagging policies and violations, IaC policies and validation runs, watch and alerting policies.

Reads (27)
`get_budget_spend`	`list_audit_logs`
`get_budget_spend_by_resources`	`list_budget_resource_entities`
`get_budget_summary`	`list_budgets`
`get_iac_ci_status`	`list_iac_ci_tokens`
`get_iac_policy_catalog`	`list_iac_policies`
`get_iac_validation`	`list_iac_validations`
`get_iac_validation_audit`	`list_role_policies`
`get_policy`	`list_roles`
`get_policy_catalog`	`list_tagging_policies`
`get_tagging_policy_catalog`	`list_tagging_violations`
`get_workflow`	`list_users`
`list_alerting_policies`	`list_watch_policies`
`list_alerts`	`list_workflows`
`list_assignments`

Writes (25)
`approve_workflow_step`	`reject_workflow_step`
`cancel_workflow`	`resolve_alert`
`create_alerting_policy`	`revoke_iac_ci_token`
`create_budget`	`update_alerting_policy`
`create_iac_policy`	`update_budget`
`create_role`	`update_iac_policy`
`create_tagging_policy`	`update_role`
`create_watch_policy`	`update_tagging_policy`
`delete_budget`	`update_team_member_role`
`delete_policy`	`update_watch_policy`
`delete_role`	`validate_iac_policy`
`ensure_iac_ci`	`validate_watch_policy`
`export_audit_logs`

Org

Teams and members, notification channels and subscriptions, integrations, dashboards, exports.

Reads (20)
`get_currency_exchange_rate`	`list_integrations`
`get_dashboard`	`list_jira_assignable_users`
`get_email_preferences`	`list_notification_channels`
`get_itsm_ticket`	`list_notification_event_types`
`get_my_permissions`	`list_notification_subscriptions`
`get_notification_read_cursor`	`list_organisations`
`get_organisation`	`list_resource_teams`
`get_team`	`list_team_members`
`get_team_resources`	`list_team_resources`
`list_dashboards`	`list_teams`

Writes (30)
`add_org_member`	`export_cost_report`
`add_team_member`	`mark_all_notifications_read`
`assign_resource_to_team`	`remove_org_member`
`bulk_update_subscriptions`	`remove_team_member`
`create_dashboard`	`set_default_dashboard`
`create_integration`	`set_email_preference`
`create_itsm_ticket`	`set_itsm_ownership`
`create_notification_channel`	`test_notification_channel`
`create_notification_subscription`	`unassign_resource_from_team`
`create_team`	`update_dashboard`
`delete_dashboard`	`update_integration`
`delete_integration`	`update_notification_channel`
`delete_notification_channel`	`update_notification_subscription`
`delete_notification_subscription`	`update_org_member`
`delete_team`	`update_team`

AI spend

LLM cost and usage by provider, model and team; virtual keys; AI budgets.

Reads (7)
`get_ai_budget_spend`	`list_ai_keys`
`get_ai_cost_summary`	`list_ai_models`
`get_ai_org_budget`	`list_budget_ai_entities`
`get_ai_usage`

Writes (3)
`add_ai_model`	`set_ai_org_budget`
`delete_ai_model`

Two tools worth leading with

get_cost_overview answers “where is the money going” in one call, and get_resource_overview answers everything about a single resource, including its metrics, cost history and open recommendations. Both replace a handful of narrower calls, so ask for them by name when you want a fast answer.

list_organisations is the only tool that takes no arguments, which makes it the cleanest test that a connection works at all. Every other tool needs an org_id that this one returns.

What is never here, at any tier

Roles and permissions, user management, organisation and cloud-account deletion, credential access, and bulk actions have no write tool at any level, and no setting adds them. get_service_config returns a service’s environment variable keys with every value redacted; no tool returns a value, for any role.

Where to go next

MCP Server: A Practical Guide covers connecting over OAuth or a token, the write-access tiers, and how permissions resolve. Per-product setup and troubleshooting live in the docs: ZopNight MCP server and ZopDay MCP server.

faq

Questions we get a lot.

If yours isn't here, email us and we'll answer directly.

Why is my tool list shorter than this page?

Because tools/list is filtered at the gateway to exactly what you may call. A tool is advertised if and only if the gate would let you invoke it, so your list reflects your role, your organisation's write-access setting and your token's capabilities. Nothing you can see will fail with a permission error.

Why is there a shared bucket rather than a clean ZopNight and ZopDay split?

Because 112 of the 289 tools answer for your whole organisation rather than one product: teams, roles, notifications, dashboards, audit logs, integrations and AI spend. Forcing them into one product would misrepresent what they do. One server and one connection carry all three groups.

Do these counts change?

Yes, on every server release. The catalogue was 122 tools before v1.40.0, 275 after it, and 289 from v1.41.0. The category totals on this page come from the generated table in the zopdev/mcp repository, which is rewritten on each release, and tools/list is always the authoritative answer for your own token.

Which tools need write access?

The 124 marked Write. A write call needs three things at once: your organisation's write-access setting must admit the tier, your live role must permit the underlying action, and your token must carry the matching capability. Any one missing is a refusal, and every organisation starts read-only.