MTA API

io.github.HumanInterfaceDesignPublished by GitHub account HumanInterfaceDesignv1.1.0Updated Oct 31, 2026

Live NYC-area transit: subway, bus, PATH, NJ Transit, LIRR, Metro-North, NYC Ferry, Citi Bike.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote MCP endpoint giving an assistant live NYC-area transit data across subway, bus, PATH, NJ Transit, LIRR, Metro-North, NYC Ferry and Citi Bike.

What you can do
  • Retrieve live NYC-area transit information covering subway, bus, PATH, NJ Transit, LIRR, Metro-North, NYC Ferry and Citi Bike.
  • No individual tools are listed in the manifest, so the exact operations are not documented here; the server is described only as a live transit data source.
When to use it
Useful when someone wants an assistant to answer questions about current NYC-area transit conditions across several modes and operators, rather than static schedules.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's site. Authentication is required: either an MTA API key sent as a Bearer token in the Authorization header, or an OAuth sign-in.
Before you install
An API key is passed in the Authorization header, so keep it out of shared logs and transcripts. The server is hosted by a third party, so queries go to that provider; check its terms and any usage limits before relying on it.

Installation

In SourceWeft

  1. Open MTA API 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.HumanInterfaceDesign%2Fmta-api/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": {
    "mta-api": {
      "type": "http",
      "url": "https://www.mtaapi.dev/mcp"
    }
  }
}

README

This repository has no README.

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

2
  1. v1.1.0LatestOct 31, 2026
  2. v1.0.0Oct 30, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.