Orbit

What Orbit MCP server does

The Orbit MCP server gives AI agents access to selected information and actions in an Orbit workspace. Orbit is a task manager built around issues, boards, sprints, projects, milestones, and docs. Through MCP, agents can read the board and file work rather than operating with unrestricted workspace access.

Access is scoped through OAuth. The agent therefore works with the permissions assigned to its connection, which is relevant for teams that need to limit what an automated or assistant-driven workflow can see and change.

Orbit belongs in the Workplace & Productivity category for use cases involving task tracking, planning, and project documentation.

How it works

An agent connects to Orbit over MCP and authenticates with OAuth. Orbit applies the connected user’s permissions when the agent reads board data or files work.

The underlying application supports issues with properties such as priorities, labels, states, estimates, assignees, reviewers, and relations. It also includes sprints, projects, docs, search, saved views, and realtime updates. The MCP listing specifically confirms agent access to the board and the ability to file work, not automatic access to every application feature.

Setup and configuration

The repository provides a local setup path for evaluating Orbit. It requires Bun 1.3 or newer and Docker. The documented sequence clones the repository, installs dependencies, copies .env.example to .env, starts the Postgres, Redis, and MinIO services, pushes the database schema, creates test databases, seeds demo data, and starts the development application.

The local web application runs at http://localhost:3000. Development realtime services use port 3100; the local Postgres, Redis, and MinIO services use ports 5434, 6380, and 9010 respectively. The repository labels self-hosting as Preview, so this setup should be treated as local evaluation rather than a supported production deployment.

Tools and capabilities

The confirmed MCP capabilities are:

• Read the Orbit board through an AI agent.
• File work in Orbit.
• Apply the connected user’s scoped OAuth permissions to agent access.

These capabilities can support workflows where an agent reviews existing tasks before recording new work.

Limitations and notes

The Orbit MCP server is tied to an Orbit workspace and its authorization model. OAuth permissions determine what the agent can access, so the resulting capabilities depend on the account and scope used for the connection.

The repository describes self-hosting as Preview and notes that the deployment profile is not a provider-neutral production commitment.

The Orbit MCP server should be selected for scoped board access and work filing, not on the assumption that it exposes every Orbit feature or a documented set of specialized agent tools.