sim-one-alpha

Astro Docs MCP

SIM-ONE Alpha includes a built-in connection to the public Astro Docs MCP server:

https://mcp.docs.astro.build/mcp

Runtime Ownership

src/engine/capabilities/builtin-mcp.ts connects the server during orchestrator initialization and returns the available MCP tools. The orchestrator merges those tools with explicitly attached product tools and enabled user MCP tools.

The built-in server exposes:

mcp__astro-docs__search_astro_docs

This is a focused framework-document lookup tool. It supports Astro development and provides a built-in example of Flue MCP integration.

Registry And Collision Behavior

The build-generated builtin-capabilities.json manifest reserves the astro-docs name under mcpServers. Runtime capabilities cannot reuse that id for a skill, tool, worker, or MCP server.

The built-in MCP connection is separate from runtime-added MCP records:

built-in astro-docs definition
-> connectBuiltinMcpServers()
-> MCP tools attached to orchestrator

enabled runtime MCP record
-> connectUserMcpServers()
-> authenticated MCP connection
-> MCP tools attached to orchestrator

Security Boundary

The built-in endpoint is fixed in product source.
A failed connection is reported and contributes no tools.
User-defined MCP servers require a capability record and enablement.
MCP tool attachment does not override protocols, trusted scope, or action-specific approval requirements.
The Researcher remains the owner of general web, current, external, and source-backed research.
The Coding Worker and its internal subagents do not receive this MCP connection in the current runtime.

Source Map

Responsibility	Source
Built-in MCP connection	`src/engine/capabilities/builtin-mcp.ts`
User MCP broker	`src/engine/capabilities/mcp-broker.ts`
Orchestrator attachment	`src/agents/orchestrator.ts`
Built-in manifest generation	`scripts/generate-builtin-registry.mjs`
Collision checks	`src/engine/capabilities/collision-check.ts`

This site is open source. Improve this page.