# Use DevTune with Pi

Canonical: https://devtune.ai/integrations/pi

Connect Pi to your DevTune project, then ask it what AI platforms say about your product, what to fix next, and whether a shipped fix moved the numbers.

## Before you start

- A DevTune project on a plan that includes API access. No account yet? [Let your agent set one up](https://docs.devtune.ai/getting-started/agent-setup).
- A Pi version with the `pi mcp` command. Run `pi mcp --help`; if Pi prints its general help instead, update Pi or use [the skills route](#skills).
- For the API key route: a project API key from **API Keys** in the account sidebar. DevTune shows the key once, so copy it when you create it.

## Connect by signing in

Add the server and sign in:

```bash
pi mcp add devtune --url https://devtune.ai/api/mcp
pi mcp login devtune
```

Sign in to DevTune in the browser, select the project, choose the scopes the connection may use, and approve. Over SSH, paste the redirected URL into the sign-in screen.

`pi mcp add` writes to `~/.pi/agent/mcp.json`. Add `--local` to write to `.pi/mcp.json` in the project, which Pi reads once you trust the project.

The connection reaches the project you select, with your own DevTune permissions.

## Connect with an API key

Use a key for scripts, scheduled runs and machines without a browser.

Put the key in an environment variable and add the server. Pi saves the variable name, not the key:

```bash
export DEVTUNE_API_KEY='dtk_live_YOUR_KEY'
pi mcp add devtune --url https://devtune.ai/api/mcp --bearer-token-env-var DEVTUNE_API_KEY
```

A key reaches the one project it was created for, with the scopes you gave it. A change made with a key acts as the member who created it.

## Check the connection

Run `pi mcp list`. It connects to each server and prints its state, tools and errors. In a session, `/mcp` shows the same; run `/reload` after changing servers outside the session.

Then ask Pi:

```text
Which DevTune project are you connected to?
```

It answers with your project's name, read with `devtune_get_connection_context`. If it names the wrong project, connect again and select the right one.

## Measure

Ask Pi what AI platforms say and what AI systems fetch from your site:

```text
What is our share of voice across AI platforms over the last 30 days, and how has it changed?
```

```text
Which pages and domains do AI platforms cite for our topics, and which competitors get cited where we are not?
```

```text
What are AI systems fetching from our site, and which pages do they ask for that do not exist?
```

Pi answers from `devtune_get_visibility_summary`, `devtune_get_visibility_diff`, `devtune_get_competitive_position`, `devtune_get_top_citation_pages`, `devtune_get_content_gaps`, `devtune_get_traffic_summary` and `devtune_get_404_demand`. Measurement windows are 30 or 90 days.

## Fix

Ask for the ranked fixes, then work one through:

```text
List the top five actions DevTune suggests for this project, with the evidence behind each.
```

```text
Accept the first action, generate its brief and show me the brief.
```

```text
Mark that action live. The page is published at https://example.com/your-page.
```

1. `devtune_get_actions` lists the queue with its evidence.
2. `devtune_change_action_status` accepts an action, and `devtune_generate_action_brief` writes its brief. Generating a brief spends credits.
3. Pi reads the brief with `devtune_get_action_brief`. Writing and publishing the page is your work and the agent's, in your own repository or content system. DevTune drafts and never publishes.
4. `devtune_change_action_status` with `mark_live` and the published URL starts the before/after measurement.

## Prove

```text
Which of our shipped actions have results, and what moved?
```

`devtune_get_outcomes_ledger` returns each measured action as improved, mixed, no clear change, declined, still measuring or unmeasured. Results show what moved after a fix shipped, not what caused it. Results windows are 7, 30, 90 or 365 days.

## What needs your approval

- Reading never changes your project or spends credits.
- Accepting an action, changing prompts or competitors, and every other change acts as you. Have the agent say what it will change before it does.
- Briefs, drafts, managed-agent runs, Agent Picks tests and prompt-set analysis spend credits. Approve the spend before the agent starts one.
- DevTune steers suggestions around locked pages and says when it did.

## How Pi runs DevTune tools

Pi offers the DevTune tools to the model alongside its own.

## Skills

The DevTune skills tell the agent which DevTune tool answers which question and how to report the numbers the way DevTune measures them.

Pi loads skills from `~/.pi/agent/skills/`, `~/.agents/skills/`, `.pi/skills/` and `.agents/skills/`. On a Pi version without `pi mcp`, use the skills instead. With `DEVTUNE_API_KEY` set, they call the DevTune REST API.

```bash
npx skills add devtunehq/skills
```

## Limits

- A connection reaches one project. Connect again, or use another key, for a second project.
- Tools your connection has no scope for do not appear in the agent. A connection never gains scopes added later. Edit the key, or disconnect and sign in again.

## If something goes wrong

| Symptom                                            | What to do                                                                                                                                                                        |
| -------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Pi lists no DevTune tools                          | Check the connection as described above. With an API key, confirm the key is active under **API Keys** and has not expired.                                                       |
| A tool is missing, or a call is refused with `403` | The connection lacks that tool's scope, or the plan lacks the feature. Ask the agent which scopes the connection has, then edit the key or sign in again with the scope selected. |
| Changes are refused but reads work                 | The connection has read scopes only, or the project is paused. Add the scope to the key or sign in again with it selected; resume a paused project in DevTune.                    |
| A figure comes back empty or as `Unmeasured`       | DevTune has no measurement for that window. Report it as unmeasured, not as zero.                                                                                                 |

## Next steps

- [Pi documentation](https://docs.pi.dev/latest/mcp): how Earendil Works documents connecting outside tools
- [MCP server](https://docs.devtune.ai/api-reference/mcp-server): every tool, its inputs and its scope
- [Code mode](https://docs.devtune.ai/api-reference/mcp-server#code-mode): two tools in place of the full list, for agents short on context
- [API authentication](https://docs.devtune.ai/api-reference/authentication): keys and scopes
- [Use DevTune with your agent](https://devtune.ai/integrations): setup guides for other agents