Basicops

io.github.BasicOpsPublished by GitHub account BasicOpsv1.0.2Updated Oct 24, 2026

BasicOps MCP server for project management, tasks, notes, and team collaboration.

VerifiedStreamable HTTPWeb executableProductivity & Workflow Communication & Collaboration

Server details

Identifier: io.github.BasicOps/basicops
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account BasicOps for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.BasicOps%2Fbasicops.svg)](https://sourceweft.com/mcp/io.github.BasicOps%2Fbasicops?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Official BasicOps MCP server that lets an assistant manage projects, tasks, notes, messages and team members in a BasicOps workspace.

What you can do: Create, update, list and archive projects, and organize their sections
Create, update, assign, prioritize and complete tasks and subtasks
Create and manage project notes
Post and reply to messages in projects and tasks
List and manage project templates, look up team members and current user info
Upload and attach files to tasks
When to use it: Useful when your team runs projects and tasks in BasicOps and you want an AI client to read and change that work in natural language instead of clicking through the app.
Requirements: A remote Streamable HTTP endpoint (legacy SSE also offered); no local install. A BasicOps account and workspace access. OAuth 2.1 sign-in for most clients, or a BasicOps API key sent as a Bearer token in the Authorization header for clients without OAuth token refresh.

Before you install

The API key is shown only once and grants access to your workspace; store it safely and revoke it in settings if exposed. Tools can create, update, archive and complete projects and tasks, post messages and upload files, so changes are written to shared team data. Access is granted to the whole workspace through the authorization flow.

Installation

In SourceWeft

Open Basicops 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.BasicOps%2Fbasicops/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "basicops": {
      "type": "http",
      "url": "https://app.basicops.com/mcp"
    }
  }
}

README

BasicOps MCP Server

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.

Endpoints

Authentication

The BasicOps MCP server supports two authentication methods:

OAuth 2.1 (recommended)

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.

API Key

For clients that do not support OAuth token refresh (such as Claude CLI / Claude Code), you can authenticate using a BasicOps API key instead.

In BasicOps, go to Settings → API Keys and generate a new key. Copy the key — it is only shown once.
Configure your MCP client to send the key as a 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.

Features

The BasicOps MCP server exposes tools for working with your entire BasicOps workspace:

Projects — create, update, list, and archive projects
Tasks & Subtasks — create, update, assign, prioritize, and complete tasks
Sections — organize tasks within projects using sections
Notes — create and manage project notes
Messages — post and reply to messages in projects and tasks
Templates — list and manage project templates
Users — look up team members and current user info
File Attachments — upload and attach files to tasks

Getting Started

1. Configure your MCP client

Claude Desktop

In Claude Desktop, add a new MCP connector using the custom connector option. Enter a name (e.g. BasicOps) and the Streamable HTTP endpoint:

On first use, you will be prompted to sign in to BasicOps via the OAuth 2.1 authorization flow.

Claude CLI / Claude Code

Claude CLI does not support OAuth token refresh, so use an API key instead. Generate one in BasicOps Settings → API Keys, then run:

bash

claude mcp add basicops \  --transport http \  https://app.basicops.com/mcp \  --header "Authorization: Bearer bo_YOUR_API_KEY"

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:

json

{  "mcpServers": {    "basicops": {      "type": "http",      "url": "https://app.basicops.com/mcp",      "headers": {        "Authorization": "Bearer bo_YOUR_API_KEY"      }    }  }}

{  "mcpServers": {    "basicops": {      "type": "http",      "url": "https://app.basicops.com/mcp",      "headers": {        "Authorization": "Bearer bo_YOUR_API_KEY"      }    }  }}

Other clients

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.

Resources

Support

For support, visit basicops.com or contact us at [email protected].

Source: README.md at commit 79e82b2

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.2LatestSep 16, 2026

Score

75% 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
License10 pts
Declare a license in the repository or the registry entry.

Transport	URL
Streamable HTTP	`https://app.basicops.com/mcp`
SSE (legacy)	`https://app.basicops.com/mcp/sse`