MCP Servers
AgentOS can use tools from any Model Context Protocol (MCP) server, local or remote. It can also act as an MCP server itself.
Adding an MCP server
| Scope | Where to add it | Stored in |
|---|---|---|
| All workspaces | Global Settings → MCP Servers | ~/.agentos/mcp-servers.json |
| One workspace | Workspace Settings → MCP Servers | .agentos/mcp-servers.json |
AgentOS supports both stdio servers (a command such as npx or uvx) and HTTP/SSE servers (a URL). When you add a
server, AgentOS connects to it and discovers its tools, resources and prompts. Enabled servers are offered to the agent automatically.
API keys and environment variables
Many servers need an API key. Add it to the server's environment (env) settings, and AgentOS passes it
to the server when it starts.
Installing an MCP server from GitHub
/install https://github.com/github/github-mcp-server
/install config github-mcp-server GITHUB_PERSONAL_ACCESS_TOKEN=ghp_…
A server that needs a key is registered disabled until you set the key with /install config. See
Skills, Tools & Plugins for more about /install.
Using MCP servers in chat
Connect to my MCP server at http://localhost:7000/sse and list all available tools.
Use the order-lookup tool on my MCP server to check the status of order #12345.AgentOS as an MCP server
Make your AgentOS agents available as tools in Claude Code, Claude Desktop, Cursor, Codex, Gemini CLI and other MCP clients:
agentos mcp install