de en es ja ko ru zh

Berlin Transport MCP Server

Name: Berlin Transport MCP Server
Author: harshil1712

by harshil1712

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

베를린 교통 MCP 서버

VBB(Verkehrsverbund Berlin-Brandenburg) API를 통해 베를린 대중교통 데이터에 접근할 수 있는 MCP 서버입니다. 이 서버는 v6.vbb.transport.rest API를 래핑합니다.

사용 가능한 도구

1. 검색_중지

베를린-브란덴부르크의 대중교통 정류장을 검색하세요.

매개변수:

query (문자열): 정류장에 대한 검색 쿼리

2. 출발 정보 가져오기

특정 정류장의 예정된 출발편을 받아보세요.

매개변수:

stop_id (문자열): 출발지를 가져올 정류장 ID
results (숫자, 선택 사항): 반환할 결과 수

3. get_journeys

한 정류장에서 다른 정류장까지의 여행 옵션을 알아보세요.

매개변수:

from (문자열): 출발지 정류장 ID
to (문자열): 목적지 정류장 ID
departure (문자열, 선택 사항): 출발 시간(예: "내일 오후 2시")
results (숫자, 선택 사항): 반환할 결과 수

Related MCP server: BVG MCP Server

Claude Desktop을 MCP 서버에 연결하세요

mcp-remote proxy를 사용하여 로컬 MCP 클라이언트에서 원격 MCP 서버에 연결할 수도 있습니다.

Claude Desktop에서 MCP 서버에 연결하려면 Anthropic의 빠른 시작을 따르고 Claude Desktop에서 설정 > 개발자 > 구성 편집으로 이동하세요.

다음 구성으로 업데이트:

지엑스피1

클로드를 다시 시작하면 도구를 사용할 수 있게 됩니다.

API 문서

기본 API에 대한 자세한 내용은 v6.vbb.transport.rest/getting-started.html을 방문하세요.

시작하기:

근로자에게 배포

이렇게 하면 MCP 서버가 remote-mcp-server-authless.<your-account>.workers.dev/sse 와 같은 URL에 배포됩니다.

또는 아래 명령줄을 사용하여 로컬 컴퓨터에 원격 MCP 서버를 생성할 수 있습니다.

npm create cloudflare@latest -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authless

MCP 서버 사용자 지정

MCP 서버에 자체 도구를 추가하려면 src/index.ts 의 init() 메서드 내에서 this.server.tool(...) 사용하여 각 도구를 정의합니다.

Cloudflare AI Playground에 연결

원격 MCP 클라이언트인 Cloudflare AI Playground에서 MCP 서버에 연결할 수 있습니다.

https://playground.ai.cloudflare.com/ 으로 이동하세요
배포된 MCP 서버 URL을 입력하세요( remote-mcp-server-authless.<your-account>.workers.dev/sse )
이제 놀이터에서 바로 MCP 도구를 사용할 수 있습니다!

Available Tools

3 tools

get_departuresD

ParametersJSON Schema

Name	Required	Description	Default
`stop_id`	Yes	Stop ID to get departures for
`results`	No	Number of results to return

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_journeysD

ParametersJSON Schema

Name	Required	Description
`from`	Yes	Origin stop ID
`to`	Yes	Destination stop ID
`departure`	No	Departure time (e.g. tomorrow 2pm)
`results`	No	Number of results to return

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_stopsD

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	Search query for stops

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

3 tool updatesAug 15, 2025
- First observedget_departures
- First observedget_journeys
- First observedsearch_stops

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.8/5.0

Scored 2026-04-18 10:10 across 3 tools

Disambiguation4/5

The three tools have distinct purposes: get_departures likely retrieves departure times, get_journeys handles route planning, and search_stops finds stops or stations. While there is some potential overlap between get_departures and get_journeys (both involve travel information), the names suggest clear enough separation for an agent to differentiate them effectively.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case: get_departures, get_journeys, and search_stops. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming style.

Tool Count3/5

With only 3 tools, the server feels thin for a transport domain that typically requires more operations like route details, fare information, or service alerts. While it covers basic functions, the count is borderline low for comprehensive transport-related tasks.

Completeness2/5

The tool set has significant gaps for a transport server. It lacks essential operations such as getting route details, checking fares, accessing service status or alerts, and managing user preferences. This incomplete coverage will likely cause agent failures when handling common transport queries beyond basic departure and journey lookups.

Maintenance

ActivityStale

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

MobilityMCP A
eu.projektionisten
Journeys, departures, line courses, disruptions in Germany; nearby sharing as currently reported.
Government Data Location Services Travel & Transportation
131
Live Times Transit
io.github.travelwhiz-ltd
Read-only public transit departures, stop search, and city coverage for bus and train users.
Travel & Transportation Location Services
1
onebusaway-mcp-server A
io.github.cyanheads
Real-time transit stops, routes, arrivals, vehicle positions, and schedules via OneBusAway APIs.
Travel & Transportation Location Services
1621
Swisstransport A
io.github.pipeworx-io
Swiss Transport MCP — wraps Transport Open Data API (free, no auth)
Travel & Transportation Open Data Government Data
432

Related MCP Servers

Île-de-France Mobilités MCP
Travel & Transportation Location Services Search
HeshamWM
A
license
Not graded
quality
D
maintenance
Provides real-time access to Paris public transport data (métro, RER, bus, tram, Transilien) including live departure times and traffic disruptions through the IDFM PRIM API.
Updated a year ago (2025-11-19 01:38 UTC)
2
MIT
BVG MCP Server
Travel & Transportation Location Services Search
uniquename
A
license
Not graded
quality
D
maintenance
An MCP server for interacting with the Berlin Public Transport (BVG) API to search for locations and plan journeys. It provides real-time access to departures, arrivals, trip details, and vehicle tracking within Berlin's transit network.
Updated 8 months ago (2026-02-05 14:11 UTC)
MIT
NS Travel MCP Server
Travel & Transportation Location Services
lauragift21
F
license
Not graded
quality
D
maintenance
Provides real-time Dutch Railways (NS) data for journey planning, live departures, disruptions, and station search.
Updated a year ago (2025-06-09 21:52 UTC)
3
-
Deutsche Bahn MCP Server
Travel & Transportation Location Services
PaulvonBerg
F
license
Not graded
quality
C
maintenance
Provides unified access to Deutsche Bahn APIs for real-time railway data, station information, timetables, disruptions, parking, and accessibility services.
Updated 9 months ago (2026-01-06 15:44 UTC)
21
-