Messaging is built into every BasicOps task and project, so one authorisation reaches both the work items and the discussion around them. That is what lets a question like "what did we decide and what is still open" be answered without the assistant hopping to a separate chat product.
A connection between an MCP client and a BasicOps workspace. Because messaging is built into every task and project, the same connection reaches both the work items and the conversation around them.
- Tasks created, assigned and updated without opening the app
- Team conversations readable in the same query as the tasks they belong to
- Projects set up, and status reports pulled across all of them
- Messages sent to the right channel from the assistant
- Files shared and conversations searched
- Access that follows your own workspace permissions — a restricted project stays invisible to the assistant too
- Open-source SDKs in TypeScript and Python for building on top
A BasicOps account, authorised over OAuth in the browser. No key goes into the client configuration, and the server is included on every plan at no additional charge.
One command plus a key — claude mcp add basicops --transport http https://app.basicops.com/mcp --header "Authorization: Bearer bo_YOUR_API_KEY", then supply credentials