Connects your AI client directly to your BasicOps workspace for managing projects, tasks, and team collaboration through natural language. Exposes tools for creating and updating projects, managing tasks and subtasks with assignments and priorities, organizing work with sections, handling notes and file attachments, and posting messages. Supports both OAuth 2.1 and API key authentication depending on your client. Useful when you want to triage your backlog, create tasks from meeting notes, or update project status without switching contexts. Works over streamable HTTP or SSE with Claude Desktop, Cursor, Windsurf, and other MCP clients.
The official Model Context Protocol (MCP) server for BasicOps — a project management platform for tasks, notes, and team collaboration.
Connect any MCP-compatible AI client (Claude, Cursor, Windsurf, etc.) to your BasicOps workspace and manage your work using natural language.
| Transport | URL |
|---|---|
| Streamable HTTP | https://app.basicops.com/mcp |
| SSE (legacy) | https://app.basicops.com/mcp/sse |
The BasicOps MCP server supports two authentication methods:
Most MCP clients (Claude Desktop, Cursor, Windsurf, etc.) support OAuth 2.1. When you connect, you will be redirected through the OAuth 2.1 authorization flow to grant access to your BasicOps workspace. No manual token management is required.
For clients that do not support OAuth token refresh (such as Claude CLI / Claude Code), you can authenticate using a BasicOps API key instead.
Bearer token in the Authorization header (see client-specific instructions below).API keys do not expire by default but can be revoked at any time from Settings → API Keys.
The BasicOps MCP server exposes tools for working with your entire BasicOps workspace:
In Claude Desktop, add a new MCP connector using the custom connector option. Enter a name (e.g. BasicOps) and the Streamable HTTP endpoint:
https://app.basicops.com/mcp
On first use, you will be prompted to sign in to BasicOps via the OAuth 2.1 authorization flow.
Claude CLI does not support OAuth token refresh, so use an API key instead. Generate one in BasicOps Settings → API Keys, then run:
claude mcp add basicops \
--transport http \
https://app.basicops.com/mcp \
--header "Authorization: Bearer bo_YOUR_API_KEY"
Or add it manually to your ~/.claude.json:
{
"mcpServers": {
"basicops": {
"type": "http",
"url": "https://app.basicops.com/mcp",
"headers": {
"Authorization": "Bearer bo_YOUR_API_KEY"
}
}
}
}
Use the Streamable HTTP endpoint https://app.basicops.com/mcp. For clients that only support SSE, use https://app.basicops.com/mcp/sse instead.
Clients that support OAuth 2.1 will be redirected through the authorization flow automatically. Clients that do not support OAuth can pass an API key as Authorization: Bearer bo_YOUR_API_KEY.
For support, visit basicops.com or contact us at support@basicops.com.