is an open standard for connecting AI agents to external systems — databases, APIs, filesystems, and services. Friday manages MCP server processes: declare a server in your workspace and everyDocumentation Index
Fetch the complete documentation index at: https://docs.hellofriday.ai/llms.txt
Use this file to discover all available pages before exploring further.
llm or user agent in that workspace can call its tools.
Declaring a server
workspace.yml
servers is the server ID you’ll use to prefix tool names. The transport block tells Friday how to start the server. Use from_environment for credentials — the daemon injects them at process start.
Tool naming
Tools must be referenced asserverId/toolName in an agent’s tools array:
friday agent list -w <workspace> to see the exact tool names available from each configured server.
Built-in platform tools (memory_save, memory_read) have no prefix and require no MCP server declaration — they’re always available:
Using tools in an llm agent
workspace.yml
Using tools in a custom Python agent
Python agents call tools viactx.tools — tool names are bare (no prefix) when calling from code:
atlas agents and MCP
type: atlas bundled agents are self-contained — they have their own built-in tool surfaces and ignore the tools array entirely. If you need a specific MCP tool called, use type: llm instead.
Common servers
| Server | Install | What it provides |
|---|---|---|
| GitHub | npx -y @modelcontextprotocol/server-github | Repos, PRs, issues, commits |
| Postgres | npx -y @modelcontextprotocol/server-postgres | SQL queries on Postgres |
| Filesystem | npx -y @modelcontextprotocol/server-filesystem | Read/write local files |
| Time | uvx mcp-server-time | Current time, timezone conversion |
| Fetch | uvx mcp-server-fetch | HTTP fetch as a tool |
Transport
Onlystdio transport is supported — Friday spawns the server as a child process and communicates over stdin/stdout. SSE transport is planned.
