Skip to content

Quickstart

The fastest path from zero to a verified answer: get a key, index one repository you already know, connect your client, and ask one question you can already grade.

1. Get an API key#

Start free — no credit card required. Your API key (it starts with mgv_) lives in app.maguyva.ai.

2. Index a repository you already know#

Connect a GitHub repository from the portal and let it index. Pick a small repo you can sanity-check fast — that makes it obvious whether Maguyva is grounding the model, instead of trying to index your whole company on day one.

3. Connect your client#

For Claude Code, install the Maguyva plugin from the marketplace — run each command inside Claude Code:

/plugin marketplace add maguyva/claude-code-plugin
/plugin install maguyva@maguyva

The plugin authenticates with your key from the MAGUYVA_API_KEY environment variable. Set it in your shell (per-project direnv is recommended, since keys are repository-scoped):

export MAGUYVA_API_KEY=mgv_xxxx

Working on a team? Add --scope project to both /plugin commands to commit the plugin to the repository's .claude/settings.json so teammates get it automatically.

Most other clients (Cursor, VS Code, Windsurf, Zed, and friends) connect to the remote server directly — point them at the endpoint with a Bearer header, no bridge required. For example, Cursor's .cursor/mcp.json:

.cursor/mcp.json
{
  "mcpServers": {
    "maguyva": {
      "url": "https://maguyva.tools/mcp",
      "headers": {
        "Authorization": "Bearer mgv_xxxx"
      }
    }
  }
}

The shape varies slightly per client (VS Code nests under servers with type: "http", Windsurf uses serverUrl, Zed uses context_servers). Replace mgv_xxxx with your API key, then restart your client. The exact config for all 24 documented clients is in the Installation Guide.

4. Ask one question you can already grade#

Start with "What repositories do I have connected?" to confirm the connection, then ask one real question about your repo whose answer you already know — something like "How is authentication handled in this codebase?"

You should get back answers with file paths and line numbers. Open the cited files and check that the answer survives contact with the actual repo. That one graded answer tells you more than any feature list — make the tool earn trust before it joins your default loop.

No results, or connection errors? Head to Troubleshooting — most failures are an unset API key, a missing npx, or a repository that has not finished indexing.

Next steps#