What it does
The BasicOps MCP server lets MCP-compatible AI clients such as Claude, Cursor and Windsurf work with a BasicOps workspace using natural language. It exposes tools for projects, tasks and subtasks, sections, notes, messages, templates, team member lookup and file attachments.
It suits someone who wants to handle BasicOps work from an AI client rather than the web app, for example creating, assigning, prioritising or completing tasks, posting replies in project or task threads, or attaching files to tasks. Clients that support OAuth 2.1 sign in through an authorization flow. Clients without OAuth token refresh, such as Claude CLI and Claude Code, use an API key instead.
The client is pointed at the Streamable HTTP endpoint, or at the SSE endpoint for clients that only support SSE, which the publisher lists as legacy. Access is granted either by signing in through OAuth 2.1 or by generating an API key under Settings, then sending it as a Bearer token in the Authorization header. API keys do not expire by default and can be revoked at any time.
Limitations and requirements
Requires a BasicOps workspace and either OAuth 2.1 sign-in or a BasicOps API key. API keys are shown only once when generated. Clients that do not support OAuth token refresh, such as Claude CLI and Claude Code, must use an API key. The SSE transport is listed as legacy.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 16 Nov 2026 · its page on the source
BasicOps MCP Server
Projects, tasks, messages and files in BasicOps, where humans and AI agents work as one team
v1.0.3As shown on registry.modelcontextprotocol.io when we last read it