Mbta Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Boston transit from MBTA. No key required.

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

A local MCP server that gives an assistant access to Boston-area MBTA transit information, with no API key required.

What you can do
The registry entry describes it as providing Boston transit data from MBTA, with no key required. No tool list, instructions or README were supplied, so the exact operations an assistant can perform are not documented here. It runs as a local process over stdio rather than as a remote endpoint.
When to use it
Worth considering when you want an assistant to answer questions about Boston-area public transit using MBTA data, and you prefer a local server that needs no API key.
Requirements
Runs as a local process on the user's machine over stdio, installed from the npm package mbta-mcp, so a Node.js runtime is needed. No authentication, environment variables or headers are declared. Desktop-only; not available as a web executable.
Before you install
The available input does not document the tools, their behavior, or what data is sent where, so review the package before installing. No credentials, payments or write actions are indicated.

Installation

In SourceWeft

  1. Open Mbta Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.