Claude Tag Plugins
Claude Tag Plugins link the @claude agent to Jira, Notion, Datadog, Salesforce, BigQuery and 14 more services, one plugin each
- 77 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Scripts call service APIs with your credentials and can create and change records, for example in Salesforce and Jira
- SQL queries to BigQuery, Redshift and Snowflake run with the rights of the connected account
Install
- Works in
Manual install
claude plugin marketplace add anthropics/claude-tag-pluginsThen `claude plugin install jira@claude-tag-plugins` or another service plugin; skills activate by themselves when relevant.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Scripts call service APIs with your credentials and can create and change records, for example in Salesforce and Jira
- SQL queries to BigQuery, Redshift and Snowflake run with the rights of the connected account
This is third-party code. Review the repository files before installing.
What it does
An Anthropic repository of plugins for the @claude agent: each service has its own plugin so a workspace connects only what it uses. The list covers Asana, BigQuery, Confluence, Datadog, Google Drive, Grafana, HubSpot, Jira, Linear, Notion, PagerDuty, Redshift, Salesforce, Sentry and Snowflake, plus `enterprise-search` across connected sources. There are three helper plugins. `claude-tag-data-viz` composes charts from tables as PNG, SVG or self-contained interactive HTML. `claude-tag-oncall` triages alerts and incidents in Slack, writes sitreps and postmortems and hands over the rotation. `claude-tag-troubleshoot` configures and debugs @claude agents: scopes, profiles, connections and plugin and skill loading. Service plugins share one layout: a `.claude-plugin/plugin.json` manifest and a `skills/<service>-api/` folder with `SKILL.md`, an endpoint reference in `references/` and scripts. The runtime handles authentication: it injects credentials into outbound requests, and variables like `$DD_API_KEY` only keep requests well formed.
Who it is for. Teams connecting a Claude agent to work services: the issue tracker, monitoring, data warehouses and CRM.
Good fit when
- An agent should triage a Datadog alert and draft an incident sitrep
- Results and table schemas from BigQuery or Snowflake queries are needed without custom scripts
- In Jira you need to search by JQL, create issues and move them across statuses
- Table metrics have to become a PNG chart or interactive HTML
Not a fit when
- An environment with no credential injection: scripts expect a token in a header and answer 401
- You need a connected service MCP server: here the work goes through skills and scripts
- You need a service outside the list: the repository has no plugin for it
Example request
Connect the jira plugin and find the open sprint issues assigned to me using JQLLimitations
- The plugins target a runtime that injects credentials, and without it requests get 401.
- The plugins hold no authentication setup instructions, which stay on the runtime side.
- Real tokens must not be committed and come from the runtime secret mechanism.
- Each service plugin is installed separately with `claude plugin install`, and there is no install everything bundle.
- The `claude-tag-oncall` and `claude-tag-troubleshoot` plugins target @claude agents in Slack and are of little use outside that setup.
How to disable. Run `claude plugin uninstall <service>@claude-tag-plugins` for each installed plugin.
FAQ
Which services do the plugins support?
Asana, BigQuery, Confluence, Datadog, Google Drive, Grafana, HubSpot, Jira, Linear, Notion, PagerDuty, Redshift, Salesforce, Sentry, Snowflake and `enterprise-search`.
Does the plugin need authentication setup?
No, the runtime does it by injecting credentials into outbound requests. Outside such a runtime the script token is unset and the service answers 401.
How do I install a plugin for one service?
Add the marketplace with `claude plugin marketplace add anthropics/claude-tag-plugins` then `claude plugin install datadog@claude-tag-plugins` or another service.
What does claude-tag-oncall do?
It triages alerts and incidents in Slack, writes sitreps and postmortems and hands over the on-call rotation.
Does Anthropic maintain this repository?
Yes, the README status is active, Anthropic maintains it and contributions follow `CONTRIBUTING.md`.
Discussion
No questions or reviews yet.
Related
PluginsYandex ecosystem plugin marketplace
claude-yandex-skills
Fifteen Claude Code plugins for Yandex services sharing one OAuth token: Metrica, Webmaster, Wordstat, Direct, Disk, Tracker and more
A plugin that makes Claude Code a background assistant: scheduled tasks, Telegram, Discord and Slack replies, a web dashboard.
Awesome Claude Skills by Composio
Awesome Claude Skills
A curated list of Claude skills and plugins, plus Composio's own automation skills for 78 SaaS apps
An agent on your Claude or Codex subscription finds jobs, tailors resumes and applies, with every status shown on a web dashboard.
Upgrade for the official Claude Code Telegram plugin: voice messages, live progress, buttons, memory and an agents board
The Corezoid plugin links Claude Code and Codex to the process platform over MCP with skills to build and review processes
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Claude Tag Plugins (this card) | no | 77 | |
| Notion Plugin for Claude Code | yes | 504 | an official single service Notion plugin with MCP, while this is a catalog of 19 plugins on skills and scripts |
| Datadog Agent Skills | no | 185 | Datadog skills from the vendor, while here Datadog is one of 19 plugins for a Claude agent |
README in short
The README opens with a plugin table covering each service, then shows marketplace and plugin install, the common folder layout, the authentication model and script security notes. It ends with the support status and links to contribution rules and the Apache 2.0 license.