mobiscroll.com valid

Mobiscroll

Mobiscroll provides scheduling, event calendar and resource management UI components, and Mobiscroll Connect, the calendar connectivity layer for scheduling products. Teams use them to build scheduling, booking, planning and resource management workflows.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T04:12:45.495Z. Cached copy · Source on mobiscroll.com

# Mobiscroll

> Mobiscroll provides scheduling, event calendar and resource management UI components, and Mobiscroll Connect, the calendar connectivity layer for scheduling products. Teams use them to build scheduling, booking, planning and resource management workflows.

Two products, used independently or together. Mobiscroll UI is the user-facing scheduling
interface. Mobiscroll Connect is the calendar connectivity layer: one integration for supported
calendar providers, with a unified Calendar API, normalized calendar data, and user-facing
connection and consent pages. Connect does not require Mobiscroll UI and works with your own
frontend.

## Products

- [Mobiscroll UI](https://mobiscroll.com/scheduling-ui): scheduler, event calendar, resource timeline and agenda views, plus calendar, date, time and range pickers. Ships as plain JavaScript and jQuery builds, and as native React, Angular and Vue components — not wrappers.
- [Mobiscroll Connect](https://mobiscroll.com/connect): the calendar connectivity layer for scheduling products. Unified Calendar API, normalized calendar data, OAuth and consent flows, calendar sync, webhooks.

## Mobiscroll UI — supported frameworks

- JavaScript, React, Angular, Vue, jQuery

## Mobiscroll Connect — SDKs and calendar providers

- SDKs: Node.js, Python, PHP, .NET, Java, Go, Ruby, plus direct REST
- Source: https://github.com/acidb/mobiscroll-connect-sdks
- Go module path: github.com/acidb/mobiscroll-connect-sdks/sdks/go
- Calendar providers: Google Calendar, Microsoft Outlook, Apple Calendar, CalDAV

## Documentation and demos

- [Documentation index](https://mobiscroll.com/docs/llms.txt): full map of the component and Connect API documentation
- [Documentation](https://mobiscroll.com/docs): component API reference and implementation guides
- [Demos](https://demo.mobiscroll.com/llms.txt): index of 400+ runnable examples with source, across all supported frameworks

## AI tooling

- [AI Tooling](https://mobiscroll.com/docs/javascript/guides/ai-integration): MCP server, agent skills for Claude Code and Codex, rule files for Cursor and GitHub Copilot
- MCP server: https://mcp.mobiscroll.com/ — version-stamped API knowledge over the Model Context Protocol

## Optional

- [Mobiscroll v5 documentation](https://mobiscroll.com/docs/5.35.0/): version 5.35.0, no longer actively maintained. Use v6 for anything new.

Machine-readable: GET /v1/resolve?q=mobiscroll.com · GET /v1/domain/mobiscroll.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for mobiscroll.com:
1. POST https://agentwebmap.com/v1/sites/mobiscroll.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://mobiscroll.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/mobiscroll.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/mobiscroll.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.