MCP Tools - Vibely

When MCP is enabled, the build agent gains two additional tools.

Two tools, any MCP server

`mcp_list`

Lists all tools from all connected MCP servers.

Agent: "What tools do I have access to?"
→ mcp_list()
→ [
    { server: "linear", tool: "linear_search_issues", ... },
    { server: "linear", tool: "linear_create_issue", ... },
    { server: "supabase", tool: "supabase_query", ... },
  ]

`mcp_call`

Invokes a specific tool on a specific server.

Agent: "Create a Linear issue for this bug"
→ mcp_call({
    server: "linear",
    tool: "linear_create_issue",
    arguments: { title: "Fix login redirect", ... }
  })

Tool discovery

The agent discovers available tools at the start of each turn by calling mcp_list. It caches the tool list for the session — if you add a server mid-build, the agent will pick it up on the next turn.

Security

MCP servers run in the same network as the build agent
Server credentials are stored in .mana/mcp.json (never committed)
The agent only calls tools the user’s prompt implicitly or explicitly requests
mcp_call arguments are logged and visible in the turn transcript