AgentOS MCP Server

by devvcore Your server? Claim it

answering

AgentOS is answering right now. Last checked moments ago.

Shared business knowledge, tools and skills for AI agents, with citations and approval controls.

Uptime history 9 days of history

9 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

446 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check AgentOS every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add agentos --transport http https://tryagentos.net/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://tryagentos.net/api/mcp

~/.codex/config.toml

[mcp_servers.agentos]
url = "https://tryagentos.net/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "agentos": {
      "url": "https://tryagentos.net/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "agentos": {
      "type": "http",
      "url": "https://tryagentos.net/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://tryagentos.net/api/mcp	streamable-http	sign-in	439 ms	0 min ago

Alternatives to AgentOS

same job, measured the same way

Alloy

by alloy

AI workspace — shared knowledge, skills, and tools for AI agents

answering

Bhived MCP

by artkeyai

Shared knowledge graph, skills, and tool discovery for AI agents through the Model Context Protocol.

42 installs/wk local only

Connapse

by destrayon

Self-hosted knowledge backend for AI agents with hybrid search and MCP tools

local only

Re-Agents MCP

by re-agents

Re-Agents.ai tools for AI agents: website audits and your approved company knowledge.

18 installs/wk local only

Levirge Brain

by levirge

Shared MCP memory for AI agents: knowledge base, skills, todos and agent-to-agent handoffs.

answering

mFlow

by m-flow

Shared task board and knowledge base for AI coding agents

answering

BailingHub for Business Operations

by bailinghub

Let AI agents query and operate business systems with authorization, approval and audit trails.

269 installs/wk local only

Okfshare MCP

by megapanchamz

Shared, versioned knowledge for AI coding agents: cited retrieval and publishing of OKF bundles.

15 installs/wk local only

AgentOS — questions

Answers built from our own checks of this server.

Why is there no tool list for AgentOS?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is AgentOS working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 446 ms. The bar chart above shows every period we have measured.

How do I connect AgentOS?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to AgentOS?

No API key is involved. AgentOS answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is AgentOS?

It answers our handshake in 446 ms on average, which is faster than 30% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.