Servidor MCP de Scheduling UI components and calendar connectivity

Qué servidores del registro oficial de MCP son de Scheduling UI components and calendar connectivity, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-14

← Volver a Scheduling UI components and calendar connectivity

De quién es el servidor

Nombre en el registrocom.mobiscroll/mcpverificado en el registro MCP

El nombre en el registro está bajo mobiscroll.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-14

Estadorespondecomprobado el 2026-10-14
Herramientas14
El servidor se llamamobiscroll-mcp-server
Versión del servidor2.0.0
Versión del protocolo2025-06-18

El 2026-10-14 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 538 ms.

Herramientas que ofrece14 herramientas · leído el 2026-10-14

resolveEnvironment
Resolves which Mobiscroll framework and major version a project uses, from the contents of its package.json. This server runs remotely and has no access to the local filesystem, so the file contents are passed in as packageJsonContent…
listComponents
Returns all available Mobiscroll UI components for a given framework and major version, with a short description and entity count for each.
getComponentSchema
Returns the API schema (options, events, methods, renderers) for a Mobiscroll component. Two-step, token-efficient flow: (1) call WITHOUT names to get a compact index - every entity as name + kind + tsType + a one-line summary. (2) Review…
searchExamples
Search for Mobiscroll examples by query, framework, major version, and component filters. Supports multi-keyword queries — all keywords must match (AND logic). Results are sorted by relevance (title matches rank highest).
getExampleById
Get a complete example by ID, including source files, description, and implementation instructions (when available).
validateCode
Validate a code snippet against the component schema, checking for unknown props/events/methods and deprecated usage. Static analysis only — no execution.
resolveConnectEnvironment
Resolves which Mobiscroll Connect SDK (language and version) a project depends on, from the contents of its dependency manifest, and returns the Connect API and SDK versions this server documents. This server runs remotely and has no…
listConnectEndpoints
Lists all Mobiscroll Connect REST API endpoints (method, path, summary, auth). Use getConnectEndpointSchema for full parameter/response detail of one endpoint.
getConnectEndpointSchema
Returns the full schema of a single Connect REST endpoint: method, path, parameters (query/body) with types, authentication, response statuses, and examples. Resolve by endpointId (from listConnectEndpoints) or by method + path. Describes…
listConnectSdkMethods
Lists the resources (auth, calendars, events) and methods exposed by one language's Connect SDK. Use getConnectSdkMethod for the full signature/doc of one method.
getConnectSdkMethod
Returns the full schema of one SDK method in one language: signature, parameters, return type, doc comment, and example. Identify the method by canonical id ("events.create"), by the language method name ("ListAsync"), or "resource.method".
searchConnect
Keyword search across Connect REST endpoints and SDK methods. Space-separated keywords, all must match (AND). Results sorted by relevance.
mapConnectEndpointToSdk
Given a Connect REST endpoint, returns the equivalent SDK call (method name, signature, example) in each language. Resolve by endpointId or by method + path. Optionally restrict to one language. Describes the endpoint and SDK call from…
getConnectErrorTaxonomy
Returns the shared Connect error taxonomy: each error category with its HTTP status and the language-idiomatic exception type. Optionally filter the exception column to one language.

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

{
  "mcpServers": {
    "mobiscroll": {
      "type": "http",
      "url": "https://mcp.mobiscroll.com"
    }
  }
}

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.