Skip to main content
Glama
crisphive

Crisphive

Official
by crisphive
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Crisphive

  • Chronary by Chronary

    Chronaryofficial

    Chronary
    A
    license
    A
    quality
    B
    maintenance
    Calendar API purpose-built for AI agents. Exposes tools to manage agents, calendars, and events, find meeting times, run scheduling proposals, set availability rules, manage webhooks, and subscribe to iCal feeds.
    54
    252 npm
    Apache 2.0

Related Servers

  • Floyd

    floyd-run
    A
    license
    Not graded
    quality
    C
    maintenance
    Scheduling and booking engine for AI agents. Check availability, hold slots, and confirm appointments with two-phase booking and conflict-free resource management.
    2
    Apache 2.0

  • Artel

    NicolasPrimeau
    A
    license
    A
    quality
    A
    maintenance
    The infrastructure for AI teams: a self-hosted server that gives a fleet of agents shared semantic memory, tasks, direct messages, and session handoff. Any agent that speaks HTTP participates: Claude Code, AutoGen, raw API scripts, anything.
    47
    9
    MIT

  • EnergyAtIt MCP Server

    kasathur
    A
    license
    B
    quality
    D
    maintenance
    Connects AI agents to energy infrastructure with 30+ tools for managing sites, assets, dispatch, settlements, compliance, and carbon tracking.
    34
    31 npm
    1
    MIT
  • Fieldproxy MCP server by Fieldproxy

    Fieldproxy MCP serverofficial

    Fieldproxy
    F
    license
    Not graded
    quality
    C
    maintenance
    Connects AI assistants such as Claude, ChatGPT, Microsoft 365 Copilot, Cursor and Codex to a field service management workspace so they can read and change data on customers, jobs, technicians, invoices, dispatch, comms and reports. It also lets users build and modify the software itself — new fields, screens, tables, automations and agents — with changes staged as drafts in a sandbox workspace and going live only after administrator approval and rollback protection.
    -
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

B3.4/5.0

Scored across 53 tools

Disambiguation3/5

Most tools pair a unique action with a unique resource, but the scheduling/candidate cluster—listJobRequestBookingWindows, listMatchingSlots, listNearbyTechnicians, listCrewCandidates, and listEmergencyCandidates—has overlapping concepts that could cause misselection. The preview/commit and quote/confirm pairs are distinguishable but demand close reading.

Naming Consistency5/5

All 53 tools use the same verb-first camelCase pattern (create/get/list/update/delete plus preview/commit/replace/quote), with no snake_case or inconsistent verb styles. Minor semantic quirks like listTechnicianSkills versus listSkillsByCategory do not break the predictable pattern.

Tool Count1/5

With 53 tools, the surface is in the extreme range and creates a heavy tool-selection and context burden for agents. Even though the domain is broad, this set should be split into focused servers (customers, scheduling, technicians, fleet, catalog) rather than exposed as one monolithic tool set.

Completeness2/5

Scheduling and emergency-rescheduling flows are richly covered, but several resources are missing standard updates (no updateVehicle, updateJobType, updateServiceArea, updateSkill, or updateSkillCategory), and job requests lack explicit cancel/archive/advance-status endpoints despite a lifecycle-driven design. These are significant gaps an agent will hit when trying to manage work orders end to end.

Maintenance

ActivityActive
ResponsivenessUnresponsive

Resources