All plugins

devtune

DevTune through its official hosted MCP server (Streamable HTTP at https://devtune.ai/api/mcp): what AI answer engines say about a product and who they cite instead, AI crawler and referral traffic, the ranked queue of fixes with briefs and drafts, before/after results for shipped fixes, and Agent Picks (which tools coding agents pick when asked to add a capability). Bundles two skills, devtune and agent-picks, that pick the right tool for each question and report rates in the units DevTune measures them. Agent Plugins v1 package (plugin.json + mcp.json + skills/), configuration only. Disclosure — hosted-only connector with no local code, hooks or background processes; every tool call goes to devtune.ai with the user's own project API key (DEVTUNE_API_KEY, sent as a bearer header), and the tool set is served by that server at runtime and is not covered by the pinned sha. Some tools change project data or spend DevTune credits (briefs, drafts, agent runs, Agent Picks tests); the package marks the server untrusted, so Hermes asks before every MCP tool not annotated read-only and refuses those tools in unattended runs, and paid Agent Picks tests also need a quote the user approves. When the MCP tools are unavailable, the bundled skills tell the agent to call DevTune's REST API (devtune.ai/api/v2) from the shell with DEVTUNE_API_KEY, where writes and credit spends are gated only by the skill's ask-first instructions, not by Hermes approval; with no DevTune account, they tell the agent to follow devtune.ai/auth.md to register one with the user's email and use the claimed access token.

DevTuneToolsv1.0.0Updated 3 hours ago

About

DevTune through its official hosted MCP server (Streamable HTTP at https://devtune.ai/api/mcp): what AI answer engines say about a product and who they cite instead, AI crawler and referral traffic, the ranked queue of fixes with briefs and drafts, before/after results for shipped fixes, and Agent Picks (which tools coding agents pick when asked to add a capability). Bundles two skills, devtune and agent-picks, that pick the right tool for each question and report rates in the units DevTune measures them. Agent Plugins v1 package (plugin.json + mcp.json + skills/), configuration only. Disclosure — hosted-only connector with no local code, hooks or background processes; every tool call goes to devtune.ai with the user's own project API key (DEVTUNE_API_KEY, sent as a bearer header), and the tool set is served by that server at runtime and is not covered by the pinned sha. Some tools change project data or spend DevTune credits (briefs, drafts, agent runs, Agent Picks tests); the package marks the server untrusted, so Hermes asks before every MCP tool not annotated read-only and refuses those tools in unattended runs, and paid Agent Picks tests also need a quote the user approves. When the MCP tools are unavailable, the bundled skills tell the agent to call DevTune's REST API (devtune.ai/api/v2) from the shell with DEVTUNE_API_KEY, where writes and credit spends are gated only by the skill's ask-first instructions, not by Hermes approval; with no DevTune account, they tell the agent to follow devtune.ai/auth.md to register one with the user's email and use the claimed access token.

DevTune agent skills

Agent skills for DevTune, which measures what AI tells
your buyers about your product and helps you change it.

| Skill | Ask your coding agent |
| --- | --- |
| devtune | What AI answers say about your product, who gets cited instead, what AI systems fetch from your site, what to fix next, and whether shipped fixes worked. |
| agent-picks | Which tool Claude Code, Codex and other coding agents pick when asked to add auth, payments, email or your category, how often they pick yours, and whether a fix moved it. |

Install

npx skills add devtunehq/skills

Add --skill devtune or --skill agent-picks to install one.

The skills use the DevTune MCP server when your agent has it, or the REST API
with a project API key in DEVTUNE_API_KEY. Without either, they walk you
through connecting. Without a DevTune account, your agent drafts the project
and you sign up and approve it in DevTune.

Hermes Agent

This repository is also a Hermes plugin: both skills plus the DevTune MCP
server.

  1. Create a project API key under API Keys in DevTune.

  2. Add it to ~/.hermes/.env:

    DEVTUNE_API_KEY=dtk_live_your_key_here

  3. Install and enable the plugin, then start a new session:

    hermes plugins install devtune
hermes plugins enable devtune

What the plugin does on your machine and over the network:

  • Every tool call goes to DevTune's hosted MCP server at devtune.ai, sending
    your API key as a bearer header. The tools are served by that server and
    follow the key's project and scopes.
  • Some tools change project data (prompts, competitors, actions) or spend
    DevTune credits (briefs, drafts, Agent Picks tests). The plugin marks the
    server untrusted, so Hermes asks before every tool not annotated read-only
    and refuses them in unattended runs. Agent Picks tests also need a quote
    you approve before they start.
  • No local code, hooks, background processes or telemetry. The plugin stores
    nothing beyond what Hermes keeps for any MCP server.

License

MIT. See LICENSE.md.

README from the reviewed commit bb38e20; it updates when the author re-pins.