MCP Server Integration

Model Context Protocol (MCP) lets your AI assistant call external tools — query databases, search the web, operate files. This guide shows how to configure and use MCP in Aino LifeOS.

Step 1: Understand Configuration Levels

Aino LifeOS supports three MCP configuration levels, from highest to lowest priority:

LevelConfig File LocationScope
Project<vault>/.mcp.jsonCurrent vault only
User~/.claude/mcp.jsonAll vaults for current user
App<userData>/mcp.jsonAll vaults for all users

Step 2: Add Your First MCP Server

Create a .mcp.json file in your vault root directory:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/dir"]
    }
  }
}

Save and restart Aino LifeOS — the server loads automatically.

Option B: User-Level Configuration

To make a tool available across all vaults, edit ~/.claude/mcp.json:

{
  "mcpServers": {
    "web-search": {
      "command": "npx",
      "args": ["-y", "@anthropic/mcp-server-web-search"]
    }
  }
}
Tip

If you already use Claude Code, your ~/.claude/mcp.json configuration is automatically recognized by Aino LifeOS — no duplicate setup needed.

Option C: App-Level Configuration

Edit <userData>/mcp.json (good for team-wide configs):

{
  "mcpServers": {
    "company-tools": {
      "command": "node",
      "args": ["./tools/mcp-server.js"]
    }
  }
}

Step 3: Verify Server Status

After configuration, open Aino LifeOS:

  1. Servers are auto-discovered and loaded at startup
  2. Check the MCP management panel — status should show "Running"
  3. Click a server name to see its tool list

If a server crashes, Aino LifeOS auto-restarts it.

Step 4: Use MCP Tools in AI Chat

Once MCP servers are loaded, AI chat automatically gains these tool capabilities:

  1. Open AI Smart Chat
  2. Ask normally — AI will automatically invoke MCP tools as needed
  3. For example, with web-search configured, ask: "Search for the latest React 19 changes"

The AI calls the search tool, gets results, and replies with organized information.

Transport Protocols

Runs as a subprocess, ideal for local tools:

  • Fast startup, low latency
  • No network configuration needed
  • Processes auto-managed by Aino LifeOS

HTTP

Connect to remote MCP servers, ideal for team sharing:

  • CORS support
  • Customizable via middleware

Built-in MCP HTTP Server

Aino LifeOS includes a built-in MCP HTTP server (default port 1478), allowing external tools to connect inbound. Uses include:

  • Browser extension connecting to Aino LifeOS via HTTP
  • Other apps integrating with your note data
  • Custom automation workflows

Common Configuration Examples

Filesystem Access

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/you/Documents"]
    }
  }
}
{
  "mcpServers": {
    "web-search": {
      "command": "npx",
      "args": ["-y", "@anthropic/mcp-server-web-search"]
    }
  }
}
Info

To add multiple servers, list them side by side in the mcpServers object, each with a unique key.

  • AI Smart Chat — MCP tools are automatically called by AI during chat
  • AI Code Agent — Code agent can use MCP tools for complex tasks