For Continue users

Continue runs on config. Add a block that knows your repo.

Continue’s agent works from the context you give it and the tools its config allows. Maguyva indexes the whole repo and serves it over MCP, so agent mode asks where code lives before it reads file after file.

Start free Read the Continue setup

Free tier: 3 repos, 50K indexed lines, no card.

One YAML block: a URL, a header, and a secret from your .env.

What Continue needs to know

Four facts specific to Continue.

// config file

A YAML block

Save the block as .continue/mcpServers/maguyva.yaml in your workspace, or add its mcpServers entry to ~/.continue/config.yaml. config.json is deprecated.

// transport

streamable-http

Continue connects to Maguyva’s endpoint over Streamable HTTP; the header sits under requestOptions. No local process, no Node.js.

// key

A secret reference

${{ secrets.MAGUYVA_API_KEY }} resolves from ~/.continue/.env, then the workspace .continue/.env and .env, then the process environment. The block itself holds no key.

// mode

Agent mode only

Continue offers MCP tools in agent mode, not in chat. JSON configs from other clients also work: drop them into .continue/mcpServers/.

Rules are a working agreement. Use them.

# .continue/rules/testing.md
---
globs: "src/**/*.ts"
---
Run the package's tests before you call a change done.

Continue loads Markdown rules from .continue/rules/. A rule can apply always, only when matching files are in context (globs), or when the agent decides its description fits. Use rules for:

Build, test, and lint commands.
Conventions per language or folder.
Directories the agent should not touch.

A rule tells the agent how to work. It cannot tell it what the code says after this morning’s merge.

Where hand-picked context runs out

Three gaps agent mode fills with file reads.

// context is what you pick

You add the files you think matter. The implementation the agent needs is often in the one you did not think of.

// callers aren’t in the file

“What breaks if I change this?” is a graph question. Without an index, the agent reads files one at a time to answer it.

// local models have small windows

Continue can run local models with tight context limits. One ranked answer with file:line fits where ten exploratory reads do not.

Maguyva as a Continue MCP block

One mcpServers block gives agent mode:

11 tools over your indexed repo semantic, structural (AST), graph, and text search, plus symbol lookup, dependents, and file retrieval.
Answers with file paths and line numbers across 285+ languages, so a small model gets the right file instead of a long listing.
Tools that only read Maguyva’s tools query the index. None of them edit your files.

Rules tell Continue how to work.
Maguyva gives Continue a map of the code.

Two workflows

Ask the map first, then edit.

// workflow 01

Find the right file without adding ten to context

continue agent> where do we verify webhook signatures?

semantic_search("verify webhook signature")
  src/webhooks/verify.ts:17   verifySignature()
  docs/webhooks.md:40   ← prose

→ The agent reads verify.ts and nothing else.
[exit 0]

A search by meaning finds the implementation even when its name does not match your words.

// workflow 02

List importers before retiring a client

continue agent> what still imports the legacy billing client?

dependency_search("LegacyBillingClient", dependents)
  4 importers in 3 packages

→ The agent migrates all four, then removes the client.
[exit 0]

The list of importers is complete before the delete, not discovered by the build afterwards.

Setup in Continue

Three steps. Free tier: 3 repos, 50K indexed lines, no card.

// step 01

Index a repo at maguyva.ai

Pick one you already know, so you can grade the answers.

// step 02

Save the block as .continue/mcpServers/maguyva.yaml

.continue/mcpServers/maguyva.yaml

name: Maguyva
version: 0.0.1
schema: v1
mcpServers:
  - name: maguyva
    type: streamable-http
    url: https://maguyva.tools/mcp
    requestOptions:
      headers:
        Authorization: Bearer ${{ secrets.MAGUYVA_API_KEY }}

// step 03

Add your key and switch to agent mode

Put MAGUYVA_API_KEY= followed by your key in ~/.continue/.env. Switch to agent mode and ask one question whose answer you already know.