Pilotless roadmap

io.github.pilotless-studioPublished by GitHub account pilotless-studiov0.1.0Updated Oct 26, 2026

Reads a Pilotless roadmap after OAuth sign-in. Scope is roadmap:read only.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant read a Pilotless roadmap after OAuth sign-in, with read-only roadmap scope.

What you can do
  • Read roadmap content from Pilotless after the user signs in with OAuth.
  • Access is limited to the roadmap:read scope, so the assistant can only view roadmap information, not change it.
  • No individual tools are documented in the listing, so the exact operations available are not specified.
When to use it
Useful when you want an assistant to look at your Pilotless roadmap while answering questions or drafting plans, without giving it write access.
Requirements
A remote MCP connection to the Pilotless endpoint over streamable HTTP, plus an OAuth sign-in with a Pilotless account. No environment variables, headers or local packages are declared.
Before you install
Signing in grants the assistant read access to your Pilotless roadmap data, which is held by a third-party service. The granted scope is roadmap:read only, so no write actions are expected.

Installation

In SourceWeft

  1. Open Pilotless roadmap 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.pilotless-studio%2Froadmap/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": {
    "pilotless-roadmap": {
      "type": "http",
      "url": "https://pilotless.nl/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. v0.1.0LatestOct 25, 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.