Name: BasicOps
Author: BasicOps

LABSCO SUMMARY

Tasks and the conversation about them, in one connection.

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.

What it is

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.

What you get

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

Requirements

A BasicOps account. Claude Desktop, Cursor and Windsurf sign you in over OAuth in the browser, with no key to paste. Claude Code cannot refresh OAuth tokens, so it takes an API key from Settings → API Keys, sent as a Bearer header. The server is included on every plan at no additional charge.

Setup effort

One command plus a key — claude mcp add basicops --transport http https://app.basicops.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"

See installation options

USE CASES

01

Catching up before a standup

Ask what is active, blocked or unassigned and get the answer together with the messages that explain why.

02

Turning a discussion into work

Create and assign the tasks that came out of a thread without retyping them into the app.

03

Answering where something landed

Search the conversations attached to a project instead of scrolling a channel looking for the decision.

04

Sending an update to the right place

Post the message to the channel it belongs in, from the assistant you were already working in.

05

Reporting across projects

Pull a status readout spanning every project you can see, bounded by the permissions your account already has.

BEFORE YOU INSTALL

What to know first

Requires

A client that can reach a remote MCP server over HTTP

Where it runs

Both documented clients connect to a hosted endpoint.

INSTALLATION

Connect your client

Server setup

claude mcp add

TERMINAL

claude mcp add basicops --transport http https://app.basicops.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"

Hosted endpoint

ENDPOINT URL

https://app.basicops.com/mcp

Add this hosted endpoint to your MCP client using the credentials listed under Requirements.

MCP Clients

Claude Code

CLAUDE CODE · JSON

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

Any MCP client — SSE

ANY MCP CLIENT — SSE · JSON

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://app.basicops.com/mcp/sse"
    }
  }
}

BasicOps