Skip to main content
Glama
fulcradynamics

Fulcra MCP Server

by fulcradynamics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Fulcra MCP Server

No user-submitted related servers found.

    Related Servers

    • Oura MCP Server

      koji117
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides access to Oura Ring health data, including sleep, activity, readiness, and stress metrics via the Model Context Protocol. It enables users to query their personal biometric information and daily health summaries through natural language in MCP-compatible clients.
      2,914 npm
      MIT

    • oura-mcp

      louis030195
      A
      license
      B
      quality
      D
      maintenance
      Enables users to query their Oura Ring data (sleep, readiness, activity, heart rate) via natural language through any MCP-compatible LLM.
      4
      10 npm
      1
      MIT

    • ultrahuman_mcp

      crixalis17
      A
      license
      A
      quality
      D
      maintenance
      Exposes real-time health data from the Ultrahuman Ring to AI agents via the Model Context Protocol, providing optimized summaries with trend analysis and actionable insights.
      7
      MIT

    • ContextFlow MCP Server

      Diwakarsrd
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible agents such as Claude and Cursor to retrieve permission-aware, structured context from local or hosted data stores. Exposes tools for semantic search, entity and relationship lookup, memory access, context pack compilation, source attribution, and retrieval explanation.
      1
      Apache 2.0
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 48 tools

    Disambiguation3/5

    Core data, file, share, and group tools are mostly distinct, but the agent-contact cluster overlaps heavily across invitations, contact status/identifier, preferences/settings, and panel-opening tools. Several tools sound like they target the same contact workflow, so an agent could easily pick the wrong one.

    Naming Consistency4/5

    Tool names are overwhelmingly snake_case verb_noun and readable. Minor deviations appear with open_/get_/prepare_/create_/match_ prefixes, but the convention remains predictable overall.

    Tool Count2/5

    At 48 tools, the surface is heavy even for a broad personal-data platform. Several UI-oriented or auxiliary tools inflate the set and increase selection burden.

    Completeness4/5

    Coverage is broad: data types, records, files, shares, groups, agent communication, and preferences all have lifecycle operations. Some gaps remain, such as record updates and calendar/message mutations, but they are mostly minor.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources