AgentOS
io.github.devvcorePublished by GitHub account devvcorev0.2.0Updated Oct 27, 2026
Shared business knowledge, tools and skills for AI agents, with citations and approval controls.
Overview
AgentOS is a remote MCP endpoint that gives AI agents shared business knowledge, tools and skills, with citations and approval controls.
- What you can do
- Connect an assistant to a shared business knowledge base and tool set hosted by AgentOS.
- Retrieve business knowledge and skills for agents, with citations attached to answers.
- Rely on approval controls around actions the agent takes.
- Authenticate per user with a personal access token rather than a shared key.
- When to use it
- Useful when you want an assistant to work from a shared, organization-level body of business knowledge and skills instead of ad hoc context, and when you need citations and approval steps around what the agent does.
- Requirements
- A remote streamable HTTP endpoint at tryagentos.net; no local package to install. An AgentOS account is required, plus a personal access token sent in the Authorization header as a Bearer token. Network access to the endpoint.
Installation
In SourceWeft
- Open AgentOS in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.devvcore%2Fagentos/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"agentos": {
"type": "http",
"url": "https://tryagentos.net/api/mcp"
}
}
}Tools
0Version history
1- v0.2.0LatestOct 17, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.