> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryquibble.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your coding agent

> Let your agent read quibbles with their page context and evidence.

Connect your coding agent to Quibble's MCP server so it can read the comments
you can see. Your agent runs in your own development environment.

## Connect your agent

**1. Find the MCP server**

In Quibble, open **Settings** and find **MCP server**. The Help menu's **Connect your coding agent** link takes you there.

**2. Follow the setup instructions**

Follow the instructions for your agent. The server address is:

```text theme={"theme":"github-light"}
https://tryquibble.com/api/mcp
```

**3. Authorize**

Sign in and review the authorization request in the browser.

For an agent not listed in Settings, use the linked
[Quibble review instructions](https://tryquibble.com/skill.md).

## Ask for a change

Tell your agent which change you want. For example:

> Read the open quibbles for my checkout project. Fix the clipped checkout
> button, run the relevant tests, and reply with what changed. Leave it open
> until I verify it.

The agent can read your note, replies, page and element context, and attached
evidence. It can reply as you, with the agent identified. It should resolve or
reopen feedback only when you tell it to.

## Verify the result

1. Review the code and test results.
2. Open the changed product and check the original problem.
3. Resolve the quibble when you are satisfied.

An agent's completion message does not itself verify the result.

> [!NOTE]
>
> MCP access is separate from a **Send to agent** handoff through GitHub. That
> handoff requires repository setup and the chosen agent's own integration;
> connecting MCP alone does not configure it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.