Amp

Amp can use Bifrost as an MCP server. The recommended Amp pattern is to bundle MCP servers inside a skill so the tools stay hidden until the skill is loaded.

Install the Bifrost Amp skills from GitHub:

amp skill add BrokkAi/bifrost/plugins/bifrost-agent/amp-skills --global --overwrite

Bifrost must be available on PATH for the skill’s MCP server to start. For local testing, install Bifrost with Cargo or use an absolute binary path in your local skill copy.

Validate the Setup

Start Amp from the repository root so --root . points at the intended workspace:

amp

Then ask Amp to use the skill and call a Bifrost tool:

Use the bifrost-code-intelligence skill. Call the Bifrost get_summaries tool on src/analyzer/usages and summarize the package structure in five bullets.

Use a source directory or source file for validation. Avoid a prompt that only asks about README.md, because that can pass through ordinary file reading without proving the MCP server ran.

Can My Agent Run RQL?

The installed bifrost-code-intelligence skill starts MCP with symbol|extended, but its tools remain hidden until Amp loads that skill. After loading it, confirm that query_code is available. Ask Amp to call query_code with the inline JSON fields {"match":{"kind":"declaration"},"limit":1}. Then check a workspace file named bifrost-smoke.rql containing (limit 1 (declaration)) and call query_code with {"query_file":"bifrost-smoke.rql"}.

The inline call is canonical JSON. MCP does not accept inline RQL text; saved RQL is loaded through query_file. Installing some other skill without an MCP definition exposes instructions, not Bifrost tools. See MCP query and RQL availability for the full surface matrix and Agent Result Safety before making completeness claims.

Direct MCP Shape

Bifrost’s raw MCP command is:

bifrost --root /path/to/project --mcp "symbol|extended"

The skill wrapper above keeps the Bifrost tools hidden until the skill is loaded.

Use --mcp core only when you intentionally want navigation without query_code.