Compass OS

io.github.tsinovoiPublished by GitHub account tsinovoiv1.0.0Updated Nov 4, 2026

Your career in your AI app: tracked roles, profile, resumes, wins and interview stories.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Compass OS connects an AI assistant to a personal career workspace: tracked job roles, profile, resumes, wins and interview stories.

What you can do
  • Track job roles and applications in a career workspace
  • Maintain a career profile, resumes, achievements and interview stories
  • Bring that career data into an AI app so the assistant can work with it
  • No tool list is published, so exact actions are not documented
When to use it
Worth considering if you manage a job search or career history in Compass OS and want an assistant to work with those roles, resumes and interview stories directly.
Requirements
Remote MCP endpoint at compass-os.dev over streamable HTTP; OAuth sign-in is required, so a Compass OS account is needed. No environment variables or headers are declared.
Before you install
The server holds personal career data such as resumes, profile details and interview stories, and OAuth grants the assistant access to that account. No tool list is published, so what the assistant can read or change is unclear; review the granted scopes before connecting.

Installation

In SourceWeft

  1. Open Compass OS 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/io.github.tsinovoi%2Fcompass-os/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": {
    "compass-os": {
      "type": "http",
      "url": "https://compass-os.dev/api/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.0LatestNov 4, 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.