[ MCP SERVER SUMMARY ]
Detailer MCP server summary
Detailer helps AI assistants visualize and explore codebases through an MCP-compatible interface. Bifrost fronts the connection so codebase exploration tools inherit your gateway's RBAC and logging.
| Property | Details |
|---|---|
| Company | Detailer |
| Connection type | HTTP |
| Authentication | As documented by Detailer |
| Package or endpoint | https://detailer.ginyill.com/ |
| Capabilities | Codebase visualization, Structural exploration, Architecture navigation |
| Official documentation | Detailer MCP documentation |
Before you start
- Detailer account or hosted endpoint access
- MCP URL from Detailer docs
What you can do with Detailer
- Give new engineers agent-assisted codebase tours under governance
- Restrict exploration tools that may expose sensitive paths
- Share one Detailer connection across multiple AI clients
[ HOW TO CONNECT ]
Connect Detailer to Bifrost in three steps
Install Bifrost
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Add Detailer in MCP Gateway
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose HTTP. Or register via the API below.
• Confirm the exact MCP path and auth scheme on the Detailer site before production.
• Catalog link uses detailer.ginyill.com — verify spelling against the vendor if connection fails.
Point clients at Bifrost /mcp
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Detailer.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Register Detailer via API
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "detailer",
"connection_type": "http",
"connection_string": "https://detailer.ginyill.com/mcp",
"auth_type": "oauth",
"tools_to_execute": [
"*"
]
}'[ WHY BIFROST ]
Run Detailer through one governed gateway
Access control
Virtual keys, RBAC, and tool allowlists per team or agent.
Cost governance
Attribute MCP tool spend alongside LLM usage in one view.
Observability
Log every tool call with latency, server, and virtual key metadata.
Credential isolation
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Common questions
What does the Detailer MCP server do?
Detailer exposes codebase visualization, structural exploration, architecture navigation to MCP-compatible AI clients. Bifrost connects to it as an upstream MCP client and exposes approved tools through one governed /mcp endpoint.
How does Detailer authenticate when used with Bifrost?
Detailer uses As documented by Detailer. Store credentials in Bifrost's environment or credential configuration so they stay at the gateway instead of being copied into every AI client.
Can Claude Desktop, Cursor, or Claude Code use Detailer through Bifrost?
Yes. After registering Detailer in Bifrost, point any HTTP MCP-compatible client at the Bifrost /mcp endpoint and authenticate with a virtual key. The client sees only the tools allowed for that key.
[ RELATED SERVERS ]
