Skip to main content
Glama
deenesjakoruzh
harshil1712

Berlin Transport MCP Server

by harshil1712
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Servidor MCP de Transporte de Berlín

Un servidor MCP que proporciona acceso a los datos de transporte público de Berlín a través de la API VBB (Verkehrsverbund Berlin-Brandenburg). Este servidor encapsula la API v6.vbb.transport.rest .

Herramientas disponibles

1. paradas de búsqueda

Búsqueda de paradas de transporte público en Berlín-Brandeburgo.

Parámetros:

  • query (cadena): consulta de búsqueda de paradas

2. obtener_salidas

Obtenga las próximas salidas para una parada específica.

Parámetros:

  • stop_id (cadena): ID de parada para obtener las salidas

  • results (número, opcional): Número de resultados a devolver

3. obtener_viajes

Obtenga opciones de viaje de una parada a otra.

Parámetros:

  • from (cadena): ID de parada de origen

  • to (cadena): ID de parada de destino

  • departure (cadena, opcional): hora de salida (p. ej., "mañana a las 14 h")

  • results (número, opcional): Número de resultados a devolver

Related MCP server: BVG MCP Server

Conecte Claude Desktop a su servidor MCP

También puede conectarse a su servidor MCP remoto desde clientes MCP locales, utilizando el proxy mcp-remote .

Para conectarse a su servidor MCP desde Claude Desktop, siga el inicio rápido de Anthropic y dentro de Claude Desktop vaya a Configuración > Desarrollador > Editar configuración.

Actualizar con esta configuración:

{
  "mcpServers": {
    "calculator": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://berlin-transport.mcp-tools.app/sse"  // or if local http://localhost:8787/sse
      ]
    }
  }
}

Reinicia Claude y deberías ver que las herramientas están disponibles.

Documentación de la API

Para obtener más detalles sobre la API subyacente, visita v6.vbb.transport.rest/getting-started.html .

Empezar:

Implementar en trabajadores

Esto implementará su servidor MCP en una URL como: remote-mcp-server-authless.<your-account>.workers.dev/sse

Alternativamente, puede utilizar la línea de comando a continuación para crear el servidor MCP remoto en su máquina local:

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

Personalización de su servidor MCP

Para agregar sus propias herramientas al servidor MCP, defina cada herramienta dentro del método init() de src/index.ts usando this.server.tool(...) .

Conéctese a Cloudflare AI Playground

Puedes conectarte a tu servidor MCP desde Cloudflare AI Playground, que es un cliente MCP remoto:

  1. Vaya a https://playground.ai.cloudflare.com/

  2. Ingrese la URL de su servidor MCP implementado ( remote-mcp-server-authless.<your-account>.workers.dev/sse )

  3. ¡Ahora puedes usar tus herramientas MCP directamente desde el área de juegos!

Available Tools

3 tools
get_departuresD
ParametersJSON Schema
NameRequiredDescriptionDefault
stop_idYesStop ID to get departures for
resultsNoNumber 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
NameRequiredDescriptionDefault
fromYesOrigin stop ID
toYesDestination stop ID
departureNoDeparture time (e.g. tomorrow 2pm)
resultsNoNumber 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
NameRequiredDescriptionDefault
queryYesSearch 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.

  1. 3 tool updates
    • 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 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

Related MCP Connectors

Related MCP Servers