| name | bifrost-code-intelligence |
| description | Use Bifrost MCP tools to search, navigate, read, summarize, and analyze code with analyzer-backed symbol and file context. |
Bifrost Code Intelligence
Use this Amp skill when you need Bifrost's analyzer-backed code intelligence in
the active workspace. The bundled mcp.json starts the Bifrost MCP server and
keeps its tools scoped to this skill.
The sections below are generated from the canonical Bifrost code-intelligence
skills in this repository.
Navigation
Source: plugins/bifrost-agent/skills/bifrost-code-navigation/SKILL.md.
Bifrost Code Navigation
Use these Bifrost MCP tools when you need to find where code is defined,
where it is used, or which source files are related to a starting point.
The Bifrost agent plugin receives its workspace boundary from standard MCP
roots, Codex sandbox-state metadata, or an explicit launcher override. Do not
call workspace lifecycle tools such as activate_workspace for the default
plugin install.
Tools
| Tool | Purpose |
|---|
search_symbols | Find classes, methods, fields, functions, modules, and other indexed declarations by name |
get_symbol_locations | Get project-relative file paths and line ranges for known symbols |
scan_usages_by_location | Find references, call sites, usages, callers, and related tests for known symbols or declaration locations |
most_relevant_files | Rank project files related to a set of seed files using imports and git history |
Tips
- Start with
search_symbols for partial names. It matches indexed symbol
names and accepts include_tests: true when tests matter.
- Use
get_symbol_locations when you need exact definition coordinates before
opening or editing a declaration.
- Use
scan_usages_by_location instead of text search when changing behavior and callers
or references matter. Pass fully qualified symbols from search_symbols
where possible, or use source-location targets when you only know the file
and declaration line.
- Use
most_relevant_files after finding one useful file to discover adjacent
implementation, tests, or related modules.
- For arbitrary text that is not an indexed code symbol, use the host shell
with
rg or another built-in grep/search tool. The default Bifrost plugin
does not expose raw text-search MCP tools.
Code Reading
Source: plugins/bifrost-agent/skills/bifrost-code-reading/SKILL.md.
Bifrost Code Reading
Use these Bifrost MCP tools to read code at the right level of detail before
opening larger files directly.
The default Bifrost agent plugin exposes structured analyzer tools, not raw
file-content tools. For non-source files, build files, README files, generated
code, or exact raw contents, use the host's built-in file-reading tools.
Tools
| Tool | Purpose |
|---|
get_summaries | Summarize matching source files, globs, classes, or modules with line ranges and compact declaration outlines when needed |
get_symbol_sources | Read exact source blocks for known symbols or flat top-level symbol outlines for file/glob inputs |
Tips
- Start with
get_summaries when you need the API shape, neighboring types,
or file structure before choosing exact definitions to inspect.
- Use
get_symbol_sources when you already know the symbol and need the body.
Fully qualified names from search_symbols are the least ambiguous inputs.
- If a summary is degraded because the response would be too large, narrow the
target or switch to
get_symbol_sources for exact bodies.
- Do not rely on
list_symbols in the default plugin install. It is an
internal helper used by Bifrost output budgeting and is not exposed by the
symbol|extended toolset.
Codebase Search
Source: plugins/bifrost-agent/skills/bifrost-codebase-search/SKILL.md.
Bifrost Codebase Search
Use these Bifrost MCP tools to find code in the active workspace. Pick the tool
that matches the thing you are looking for.
Tools
| Goal | Tool |
|---|
| Find a symbol by name | search_symbols |
| Find callers, references, or usages | scan_usages_by_location |
| Find language-neutral code shapes | query_code |
| Find files by path or glob | find_filenames |
| List files under a directory | list_files |
| Expand from seed files to related code | most_relevant_files |
| Find arbitrary text | Host shell with rg or another built-in grep/search tool |
Tips
- Use
search_symbols for questions like "where is parseRequest defined?"
or "which services match .*Service?". Pass include_tests: true when test
declarations are relevant.
- Use
scan_usages_by_location for references and call sites. It is the structured
analyzer-backed path and should be preferred over grep for code references.
- Use
query_code for normalized syntactic shapes such as calls by callee,
assignments by left/right roles, imports, decorators, containment, or
captures. Version 2 also supports typed enclosing-declaration, reference-site,
semantic-user, hierarchy/member, and direct import-file steps. Use
references_of, used_by, or uses when a structural seed should continue
through exact indexed symbol identities; use scan_usages_by_location for a
location-first lookup or usage_graph for the narrower whole-workspace graph. The schema reference
is https://bifrost.brokk.ai/code-query-json/.
- Use
find_filenames for path globs, basename searches, and repository file
discovery.
- Use
list_files when you need a bounded directory listing that respects the
workspace file walker.
- Use
most_relevant_files to broaden context from one known file into related
source and tests.
- For log messages, string literals, comments, config keys, or any other text
that is not an indexed declaration or reference, use
rg through the host
shell. The default Bifrost plugin does not expose the raw text MCP toolset.
