aether-mcp-servers 0.1.0

Built-in MCP tool servers for the Aether AI agent framework
Documentation

mcp-servers

Pre-built MCP tool servers for Aether agents. Each server runs in-process and is gated behind a feature flag so you only compile what you need.

Feature Server What it provides
coding CodingMcp File read/write/edit, bash, grep, find, LSP integration, web fetch/search
skills SkillsMcp Slash commands and reusable skill prompts
tasks TasksMcp Hierarchical task management with dependencies
subagents SubAgentsMcp Spawn and orchestrate sub-agents

Using with Aether (mcp.json)

These servers use Aether's in-memory transport type -- they run inside your agent process, not as separate subprocesses. Wire them up in mcp.json:

{
  "servers": {
    "coding": {
      "type": "in-memory"
    },
    "skills": {
      "type": "in-memory",
      "args": ["--dir", "$HOME/.aether"]
    },
    "tasks": {
      "type": "in-memory"
    },
    "subagents": {
      "type": "in-memory",
      "args": ["--project-root", "."]
    }
  }
}

Each server key must match a factory registered with McpBuilder::register_in_memory_server(). The args array is parsed as CLI flags by each server:

Server Flag Default Description
coding --root-dir <path> cwd Workspace root for LSP and file operations
skills --dir <path> none Base directory containing commands/ and skills/ subdirectories
tasks --dir <path> . Base directory for task storage (creates .aether-tasks/ inside)
subagents --project-root <path> (alias: --dir) . Project root containing optional .aether/settings.json authored agents

To register factories and load the config:

use aether_core::mcp::mcp;
use futures::FutureExt;
use mcp_servers::{CodingMcp, SkillsMcp, SubAgentsMcp, TasksMcp};

let builder = mcp()
    .register_in_memory_server("coding", Box::new(|_args| {
        async move { CodingMcp::new().into_dyn() }.boxed()
    }))
    .register_in_memory_server("skills", Box::new(|args| {
        async move { SkillsMcp::from_args(args).unwrap().into_dyn() }.boxed()
    }))
    .register_in_memory_server("tasks", Box::new(|args| {
        async move { TasksMcp::from_args(args).unwrap().into_dyn() }.boxed()
    }))
    .register_in_memory_server("subagents", Box::new(|args| {
        async move { SubAgentsMcp::from_args(args).unwrap().into_dyn() }.boxed()
    }));

// Load mcp.json -- matches server keys to registered factories
let builder = builder.from_json_file("mcp.json").await?;

Programmatic Usage

Add to your Cargo.toml:

# Everything
mcp-servers = { path = "../mcp-servers" }

# Just coding tools
mcp-servers = { path = "../mcp-servers", default-features = false, features = ["coding"] }

Create and start servers directly:

use mcp_servers::{CodingMcp, SkillsMcp, TasksMcp};
use rmcp::ServiceExt;

// Create a coding server
let server = CodingMcp::new()
    .with_root_dir("/my/project".into())
    .into_dyn();

// Or with LSP support
use mcp_servers::{DefaultCodingTools, LspCodingTools};

let lsp_tools = LspCodingTools::new(DefaultCodingTools::new(), "/my/project".into());
let server = CodingMcp::with_tools(lsp_tools).into_dyn();

Server Documentation

Feature Flags

  • default -- all four servers
  • coding -- file ops, bash, LSP, web tools
  • skills -- slash commands and prompts
  • tasks -- task tracking (no dependency on coding)
  • subagents -- sub-agent spawning (implies coding, skills, tasks)
  • all -- same as default, explicit alias