AltOrbit

app.altorbitPublished by altorbit.appOfficial publisherv1.0.0Updated Oct 29, 2026

AltOrbit boards, tickets, time tracking, reports and client requests, with your rights in the app.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

AltOrbit's remote MCP server gives an assistant access to your AltOrbit boards, tickets, time tracking, reports and client requests, scoped to your app rights.

What you can do
  • Work with AltOrbit boards and tickets.
  • Track and review time entries.
  • Read reports.
  • Handle client requests.
  • All actions run under the permissions your AltOrbit account already has in the app.
When to use it
Useful when your team runs projects, tickets and client work in AltOrbit and you want an assistant to look things up or act on them without switching apps. It fits project tracking, time logging and client-request follow-up.
Requirements
A remote MCP endpoint at api.altorbit.app over streamable HTTP, with OAuth sign-in to an AltOrbit account required. No packages, environment variables or headers are declared.
Before you install
The server acts with your existing AltOrbit rights, so an assistant may be able to change boards, tickets, time entries and client requests depending on your role. Review what your account is permitted to modify before connecting, and note that your AltOrbit work data is shared with the assistant through the service.

Installation

In SourceWeft

  1. Open AltOrbit in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/app.altorbit%2Fmcp/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": {
    "altorbit": {
      "type": "http",
      "url": "https://api.altorbit.app/mcp"
    }
  }
}

Tools

0
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

1
  1. v1.0.0LatestOct 29, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.