For the complete documentation index, see llms.txt. This page is also available as Markdown.

Getting started

This guide takes you from zero to calling your first MCP tool. It should take about 5 minutes.

Installing mcp

Homebrew (macOS and Linux):

brew install avelino/mcp/mcp

Pre-built binary:

Download the latest binary for your platform from GitHub Releases, make it executable, and move it to your $PATH:

chmod +x mcp-*
sudo mv mcp-* /usr/local/bin/mcp

Docker:

docker pull ghcr.io/avelino/mcp

To use it like a native command, create an alias:

alias mcp='docker run --rm -v ~/.config/mcp:/root/.config/mcp ghcr.io/avelino/mcp'

Add the alias to your shell profile (~/.bashrc, ~/.zshrc, or ~/.config/fish/config.fish) to make it permanent. If your servers need environment variables (API tokens, etc.), pass them with -e:

alias mcp='docker run --rm -v ~/.config/mcp:/root/.config/mcp -e GITHUB_TOKEN ghcr.io/avelino/mcp'

From source (requires Rust):

# Install Rust if needed: curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
cargo install --path .

Verify it works:

You should see:

Adding your first server

The fastest way to get started is adding a server from the MCP registry. Let's add the filesystem server — it lets you read, write, and search files through MCP.

You'll see something like:

Listing available tools

Now see what tools the server provides:

Output:

Calling a tool

Call a tool by passing its name and a JSON object with the arguments:

Output:

That's it. You just called an MCP tool from your terminal.

What's next?

  • Tutorial — Walk through more realistic examples: HTTP servers, authentication, piping, and scripting.

  • Configuration — Learn the full config file format.

  • Supported services — Setup guides for Sentry, Slack, Grafana, and more.

Last updated

Was this helpful?