OIO
app.oiov1.8.0Updated Oct 5, 2026
Projects, tickets, notes and to-dos in OIO, the freelance workspace. OAuth sign-in, Pro plan.
Overview
AI-generated overview
Connects an assistant to OIO, a freelance workspace, so it can work with projects, tickets, notes and to-dos.
- What it does
- OIO is a remote MCP server for the OIO freelance workspace. According to the registry description, it covers projects, tickets, notes and to-dos, letting an assistant read and act on that workspace content. No individual tools are listed in the supplied material, so the exact operations are not documented here.
- When to use it
- Worth considering if you already run freelance work in OIO and want an assistant to reach your projects, tickets, notes and to-dos without leaving the chat. It is not useful if your work is not tracked in OIO.
- Requirements
- A remote streamable HTTP endpoint at oio.app; nothing to install locally. Sign-in is by OAuth, and the description mentions a Pro plan, so an OIO account with that plan is likely needed. No environment variables or headers are declared.
Before you install
The description states OAuth sign-in and a Pro plan, so access is tied to your OIO account and may require a paid subscription. Because the server covers tickets, notes and to-dos, an assistant may be able to change or delete that content; the supplied material does not say which operations are read-only. No tool list is published, so review permissions before connecting.
Installation
In SourceWeft
- Open OIO in the dashboard and add it to a workspace.
- 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.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"oio": {
"type": "http",
"url": "https://oio.app/api/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.8.0LatestOct 5, 2026

