Scheduling UI components and calendar connectivity MCP server

Which servers in the official MCP registry are Scheduling UI components and calendar connectivity's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to Scheduling UI components and calendar connectivity

Whose server it is

Registry namecom.mobiscroll/mcpverified in the MCP registry

The registry name sits under mobiscroll.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14

Stateanswerschecked 2026-10-14
Tools14
Server calls itselfmobiscroll-mcp-server
Server version2.0.0
Protocol version2025-06-18

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 538 ms.

Tools it offers14 tools · read 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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.